OpenClaw GOG Skill: The Gaming Integration Your Agent Can Use

Most gamers have a backlog problem. 200 games owned, 12 actually played, and no idea what to start next. Your OpenClaw agent fixes this — permanently. The GOG Skill gives your agent direct read access to your library, your playtime, and your achievements so it can answer questions like "what's the shortest game in my backlog I haven't touched?" in under two seconds.

What the GOG Skill Does

The GOG Skill is one of OpenClaw's built-in integrations, meaning it ships with the core installation and requires no separate download. It authenticates with GOG's Connect API using OAuth2, then exposes your library data as structured context your agent can reason over.

Here's what the skill surfaces to your agent:

• Library inventory — every game you own, with title, GOG ID, genre tags, and release year
• Playtime data — total hours played per title (synced from GOG Galaxy cloud saves if enabled)
• Achievement progress — completion percentage and unlocked achievements per game
• Wishlist — games you've flagged for future purchase, with current price data
• Metadata queries — rating, description, system requirements on demand

The skill does not modify your account, make purchases, or launch games. It is read-only at the API level. This is a deliberate design choice — your agent stays in an advisory role.

Prerequisites

Before configuring the GOG Skill, confirm you have the following:

• OpenClaw v1.6.0 or later (GOG Skill was added in 1.6)
• A GOG account with at least one owned game
• GOG Galaxy installed and synced at least once (for playtime data to appear in the API)
• An internet connection from your OpenClaw host — the skill makes outbound HTTPS calls to api.gog.com

You do not need GOG Galaxy running on the same machine as OpenClaw. The OAuth token is account-level and works from any network.

Installation & Auth

The skill is bundled — you just need to activate and authorise it. Run the following command to start the OAuth flow:

# Initiate GOG OAuth authorisation
openclaw skill auth gog

# Output:
# → Open this URL in your browser to authorise OpenClaw:
# → https://auth.gog.com/auth?client_id=...&redirect_uri=...&scope=library
# → Waiting for callback on http://localhost:7842/callback ...
# → ✓ Authorised. Token stored in ~/.openclaw/secrets/gog_token.enc

The CLI opens a local callback server, you log into GOG in your browser, and the token is stored encrypted on disk. You won't need to repeat this unless you revoke access from GOG's account settings.

Configuration Reference

After authorisation, add the GOG Skill config block to your ~/.openclaw/config.yaml:

# ~/.openclaw/config.yaml
skills:
  gog:
    enabled: true
    cache_responses: true       # cache API responses to avoid rate limits
    cache_ttl_seconds: 300      # how long to cache library data (5 min default)
    include_wishlist: true       # expose wishlist data to agent
    include_achievements: true  # expose achievement data to agent
    max_library_results: 200    # cap results returned in library queries
    default_sort: "playtime_desc" # playtime_desc | title_asc | last_played

After saving, restart OpenClaw to load the new config:

openclaw restart
# Verify skill loaded:
openclaw skill list
# → gog    ✓ active    library: 247 games

What You Can Ask Your Agent

Once active, your agent understands natural language queries about your GOG library. Here's what works well in practice:

• "What are my top 5 most-played games on GOG?"
• "Which games in my library have I never started?"
• "Find me a short RPG I own that I haven't finished."
• "How close am I to 100% achievements in The Witcher 3?"
• "What's the cheapest game on my wishlist right now?"
• "Recommend a game for a 2-hour session based on what I've enjoyed."

The agent combines library metadata with your conversation context. If you've told it you prefer strategy games or have limited time, it factors that in automatically.

We'll get to advanced combinations in a moment — but first, understand why single-skill queries are just the beginning.

Advanced: Combining Skills

The GOG Skill gets significantly more powerful when combined with other OpenClaw skills. Here's what we've seen work consistently:

GOG + Summarize Skill: Ask your agent to pull a game from your library and generate a personalised summary — not just a generic description, but one that highlights aspects matching your stated preferences. Saves 20 minutes of reading reviews.

GOG + Google Calendar Skill: "Schedule 2-hour gaming sessions on weekday evenings this week and suggest what to play." The agent checks your calendar for free slots and cross-references your library for session-appropriate games.

GOG + Web Search Skill: Ask your agent to find current sale prices on your wishlist titles across CDKeys, Humble Bundle, and GOG itself. It queries your wishlist, then searches for current deals.

Each skill operates independently but they share the same agent context. Combining them is a matter of asking multi-part questions — no additional configuration needed.

Common Mistakes

Three mistakes break 80% of GOG Skill setups. Avoid them all:

1. Forgetting to sync Galaxy before authorising. If you've never opened GOG Galaxy and synced your library, the Connect API returns empty playtime data. Open Galaxy, let it sync fully, then run openclaw skill auth gog. The skill reads what Galaxy has uploaded — not your local install state.

2. Setting cache_ttl_seconds too low. A TTL under 60 seconds means heavy agent usage (multiple queries in quick succession) hits GOG's rate limit. The 403 response from GOG looks like an auth failure, which throws people off. Stick with the 300-second default unless you have a specific reason to go lower.

3. Running the auth command as root. The token file stores to ~/.openclaw/secrets/ relative to the user running the command. If you auth as root but run OpenClaw as a service user, the token file is in the wrong home directory. Always auth as the same user that runs OpenClaw.

Sound familiar? These are the exact issues we see reported in the OpenClaw community Discord weekly. Fix them upfront and your setup will be clean from day one.

Frequently Asked Questions

What is the OpenClaw GOG Skill?

The GOG Skill is a built-in integration connecting your OpenClaw agent to your GOG.com library via OAuth2. It lets your agent read your game collection, playtime stats, achievements, and wishlist — all through natural language queries with no manual API calls required.

Does the GOG Skill require GOG Galaxy installed on the server?

No. It communicates with GOG's Connect API over HTTPS. Galaxy doesn't need to run on the OpenClaw host. You do need Galaxy installed on at least one machine to sync playtime data to GOG's servers, but that machine doesn't have to be the OpenClaw host.

Can my agent launch games through the GOG Skill?

Not through this skill — GOG's Connect API is read-only. Game launches require interfacing with GOG Galaxy's local IPC socket, which is a separate integration. The built-in GOG Skill focuses on data retrieval, recommendations, and library management queries.

How does the recommendation engine work?

The skill passes structured library and playtime data to your configured LLM. The model reasons over genre tags, playtime patterns, and wishlist items against your stated preferences. Recommendation quality improves with more playtime data synced to GOG's servers.

What happens when GOG rate-limits my agent?

GOG enforces 60 requests per minute per OAuth token. OpenClaw's GOG Skill includes response caching with a configurable TTL — default is 300 seconds. Enable cache_responses: true in your config. A rate-limit hit returns a 403, which OpenClaw logs clearly so you know exactly what happened.

Is my GOG password stored anywhere by OpenClaw?

Never. The skill uses OAuth2 token exchange — your password touches only GOG's servers. OpenClaw stores only the encrypted refresh token. You can revoke access any time from GOG's connected apps settings, instantly invalidating the stored token.

Can I run the GOG Skill alongside Steam or Epic integrations?

Yes. OpenClaw skills run independently with separate config blocks and credentials. Many users run GOG, Steam, and Epic skills together to give their agent a unified cross-platform library view. Each skill has its own cache and rate-limit handling.