Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Configure and verify bearer API key authentication for Remix agent publishing workflows.
Configure and verify bearer API key authentication for Remix agent publishing workflows.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Use this skill when a user needs to authenticate an external service/agent for Remix server APIs.
Log in to your Remix account. Go to https://remix.gg/api-keys. Create a new API key. Store it as a secret in your service runtime. Send: Authorization: Bearer <api_key> Use base URL https://api.remix.gg.
Run a cheap authenticated call first (for example, POST /v1/agents/games in a test project) to verify the key works.
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.
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.