How to Install and Use Gog in OpenClaw

Open your terminal and run the clawhub install command to add the GOG skill to your OpenClaw instance. ClawHub downloads the skill package, verifies its integrity, and registers it with your local OpenClaw configuration. Installation takes 10-30 seconds. When complete, you will see a success message showing the installed version number and the configuration keys the skill requires. The skill will not activate until credentials are configured — attempting to use it before setup will return a clear error message listing the missing configuration. If the install fails with a 'command not found' error, verify that your OpenClaw installation is complete and that the ClawHub binary is on your PATH. Running `clawhub --version` is a quick way to confirm ClawHub is accessible before attempting skill installations.

1clawhub install gog

GOG provides API access for developers and integration use cases. To get your credentials, navigate to your GOG account settings at gog.com. Look for 'Developer' or 'API Access' sections in the account settings page — GOG's API credential process may vary depending on account type and the current state of their developer program. For personal use integrations through OpenClaw, GOG may issue credentials directly through account settings, or you may need to use the GOG Galaxy authentication flow to obtain an access token. Check the GOG developer documentation or the OpenClaw community forums for the most current credential acquisition process, as GOG periodically updates how API access is managed. Once you have your GOG API key or OAuth credentials, note the exact variable names that the feishu-bridge skill expects — run `clawhub info gog` to see the precise configuration key names. These must match exactly what you set in OpenClaw's configuration. If GOG direct API credentials are not available for your account type, the gog skill may support an alternative authentication method using your GOG username and password combined with session token extraction — refer to the skill's documentation via `clawhub info gog` for the currently supported authentication approaches.

Add your GOG credentials to OpenClaw's configuration using the `clawhub config set` command or by editing the `~/.openclaw/.env` file directly. Use the exact variable names shown in `clawhub info gog` output — these must match precisely for the skill to authenticate correctly with GOG's API. After adding your credentials, run `clawhub reload` to apply the changes. OpenClaw will pick up the new configuration without a full restart. Verify the credentials are set by running `clawhub config get` for each credential variable — you should see a masked value confirming the key is present. If the skill uses OAuth-style access tokens that expire, you will need to refresh them periodically. Some versions of the gog skill handle token refresh automatically; check the skill documentation to understand the token lifecycle for your installed version.

1# Add to ~/.openclaw/.env (use the exact variable name from `clawhub info gog`)
2GOG_API_KEY=your_gog_api_key_here
3
4# Or set via clawhub config command
5clawhub config set GOG_API_KEY your_gog_api_key_here
6
7# Verify the key is saved
8clawhub config get GOG_API_KEY
9
10# Apply changes
11clawhub reload

Open OpenClaw chat and run a test prompt to confirm the GOG skill is working. Start with a simple catalog search — asking for games in a specific genre or by a specific developer. The gog skill activates automatically when OpenClaw recognizes game catalog intent in your prompts, or you can explicitly invoke it by mentioning 'on GOG' or 'using GOG' in your query. A successful response will include game titles, current prices, and brief descriptions from the GOG catalog. The response typically takes 2-5 seconds as OpenClaw queries the GOG API and formats the results. If you see an authentication error in the response, double-check your credential configuration from the previous step. If the skill does not activate on your first test, try rephrasing to explicitly mention GOG: 'Search GOG for...' or 'Use the GOG skill to find...' This signals to OpenClaw that the GOG skill specifically should handle the request rather than routing to a general search skill.

Beyond catalog search, the GOG skill supports wishlist operations when properly authenticated with your personal GOG account. You can add games to your wishlist, view current wishlist contents, check which items are on sale, and remove games you have already acquired. Wishlist functionality requires that your GOG credentials grant access to your personal account data — not just public catalog data. If your API key is scoped to public catalog access only, wishlist prompts will return a permissions error. In that case, check `clawhub info gog` for instructions on upgrading your credential scope to include account data access. For sale monitoring, you can create a recurring OpenClaw prompt that checks your wishlist against current GOG sale prices. Combined with a notification skill (Telegram, Discord, or Feishu), this creates an automated deal alert system: OpenClaw checks GOG daily and notifies you the moment a wishlist game hits your target price. RapidDev can help set up automated GOG sale monitoring workflows that combine the GOG skill with notification and scheduling integrations in OpenClaw — useful for building personal deal-tracking systems without manual daily checks.

1# Configure GOG skill options in ~/.openclaw/skills/gog.yaml
2gog:
3  include_dlc: false              # include DLC in search results (default: false)
4  currency: "USD"                 # preferred currency for prices (default: USD)
5  language: "en"                  # catalog language (default: en)
6  max_results: 10                 # max results per search query (default: 5)
7  include_coming_soon: false      # include unreleased games in results