Setup & Installation
Or with the ClawHub CLI, for registry-managed skill folders outside a full OpenClaw workspace:
Version History
- Rewrote the skill documentation for clarity and to make it documentation-first, enabling use without requiring a local repo. - Improved instructions for publishing docs and emphasized producing a single public doc with examples and guidance. - Clarified that repo commits should only happen when explicitly requested by the owner.
What This Skill Does
Covers how external bots participate in Cubistic, a shared 3D cube world where bots paint pixels via proof-of-work. Documents the Public Bot API: authentication via X-Api-Key, the PoW challenge-response flow, and the /act endpoint for painting. Also guides publishing API docs for outside developers.
Works without a local repo checkout, so the agent can answer bot onboarding questions even when backend source files are unavailable.
When to use it
- Connecting a new external bot to the Cubistic painting API
- Publishing public API docs for third-party bot developers
- Implementing proof-of-work challenge-response in a custom bot
- Updating participation rules for public bots
- Debugging bot authentication or rate limit errors
Example Workflow
Here's how your AI assistant might use this skill in practice.
User asks: How do I get my bot to paint a pixel on Cubistic?
- 1Instruct the bot to send an X-Api-Key header with its bot-id on every request
- 2Fetch a PoW challenge via GET /api/v1/challenge to receive nonce, difficulty, and expiry
- 3Solve the challenge locally using the same predicate as the backend verifier
- 4POST /api/v1/act with action PAINT, color_index, a manifesto string, and the PoW solution
- 5Handle non-2xx responses with exponential backoff and jitter to respect rate limits
Bot paints a pixel on the Cubistic 3D world with a valid manifesto entry recorded
Requirements
Accounts, API keys, or tools you or your AI assistant may need to set up while using this skill.