remix-api-key-auth
Configure and verify bearer API key authentication for Remix agent publishing workflows.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/chuckstock/remix-api-key-authWhat This Skill Does
The remix-api-key-auth skill provides a robust framework for managing and verifying bearer API key authentication specifically tailored for Remix agent publishing workflows. It streamlines the connection between your local environment or service runtime and the Remix server APIs. By centralizing the authentication logic, this skill ensures that requests to https://api.remix.gg are correctly formatted with the required Authorization: Bearer <api_key> header, reducing common handshake errors and configuration drift.
Installation
To integrate this capability into your OpenClaw agent, execute the following command in your terminal within your OpenClaw project directory:
clawhub install openclaw/skills/skills/chuckstock/remix-api-key-auth
Ensure that your OpenClaw version supports the skills marketplace, and check your skills.json configuration file to confirm the package has been added correctly after execution.
Use Cases
This skill is essential for developers building automated CI/CD pipelines for Remix agent deployment. It is primarily used when:
- You need to automate the pushing of agent configurations to the Remix platform.
- You are initializing a new project that requires authenticated API access for game-world management.
- You are debugging authentication failures during the deployment process of your AI agents.
- You want to standardize how secrets are handled across multiple environment configurations.
Example Prompts
- "OpenClaw, please verify my Remix API key by running a test request to the game agent endpoint."
- "Help me configure the authentication headers for my new Remix service connection to ensure all requests use the correct bearer token."
- "My Remix deployment is failing with a 401 error; can you help me troubleshoot my API key setup?"
Tips & Limitations
To maintain security, never hardcode your API key directly in your script files; always load it from an encrypted secrets manager or an .env file that is excluded from version control. Note that this skill only handles the authentication handshake. If you encounter errors after successful authentication, verify your request payload against the documentation at https://api.remix.gg/docs. Ensure your API key has the necessary scope permissions for the specific endpoints you are targeting, as rotating a key is the best practice if you suspect it has been compromised.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-chuckstock-remix-api-key-auth": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: external-api