remix-api-key-auth
Configure and verify bearer API key authentication for Remix agent publishing workflows.
Setup & Installation
Install command
clawhub install chuckstock/remix-api-key-authIf the CLI is not installed:
Install command
npx clawhub@latest install chuckstock/remix-api-key-authOr install with OpenClaw CLI:
Install command
openclaw skills install chuckstock/remix-api-key-author paste the repo link into your assistant's chat
Install command
https://github.com/openclaw/skills/tree/main/skills/chuckstock/remix-api-key-authWhat This Skill Does
Covers API key creation and bearer token setup for authenticating external services against Remix's server APIs. Includes a verification step and troubleshooting guidance for common auth failures.
The built-in verification call catches misconfigured keys before they cause silent failures in production.
When to Use It
- Connecting an agent service to a Remix project for the first time
- Rotating a compromised or expired Remix API key
- Debugging 401 errors when calling remix.gg endpoints
- Storing Remix credentials in a cloud runtime environment
- Verifying a new key works before deploying to production
View original SKILL.md file
# Remix API Key Setup Use this skill when a user needs to authenticate an external service/agent for Remix server APIs. ## Steps 1. Log in to your Remix account. 2. Go to `https://remix.gg/api-keys`. 3. Create a new API key. 4. Store it as a secret in your service runtime. 5. Send: - `Authorization: Bearer <api_key>` 6. Use base URL `https://api.remix.gg`. ## Verification Run a cheap authenticated call first (for example, `POST /v1/agents/games` in a test project) to verify the key works. ## Troubleshooting Invalid API Key - Check `Authorization` is formatted as `Bearer <api_key>`. - Re-copy the key from `https://remix.gg/api-keys` and rotate if needed. - Verify your service is reading the expected secret/env var in the current runtime. - Confirm the request is server-side and not exposed through browser code. - If behavior seems inconsistent with local docs, use `https://api.remix.gg/docs` as source of truth.
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: Connecting an agent service to a Remix project for the first time
- 1Connecting an agent service to a Remix project for the first time
- 2Rotating a compromised or expired Remix API key
- 3Debugging 401 errors when calling remix.gg endpoints
- 4Storing Remix credentials in a cloud runtime environment
- 5Verifying a new key works before deploying to production
Configure and verify bearer API key authentication for Remix agent publishing workflows.
Security Audits
These signals reflect official OpenClaw status values. A Suspicious status means the skill should be used with extra caution.