cubistic-public-bots

What This Skill Does

The cubistic-public-bots skill acts as the technical documentation and workflow automation hub for the Cubistic ecosystem. It enables OpenClaw to provide developers with precise, up-to-date guidance on how to integrate external bots into the Cubistic 3D world. By managing the technical nuances of the Proof-of-Work (PoW) verification system, API requirements, and rate-limiting protocols, this skill ensures that external developers can reliably interact with the /act and /challenge endpoints. The skill is designed to be the definitive source of truth, effectively bridging the gap between internal architectural documentation (the backend source files) and public-facing developer guides.

Installation

To integrate this skill into your OpenClaw environment, execute the following command in your terminal: clawhub install openclaw/skills/skills/andreasnordenadler/cubistic-public-bots

Use Cases

• Onboarding developers: Providing step-by-step instructions for third-party bots to register, authenticate, and solve PoW challenges for pixel painting.
• Documentation Maintenance: Automating the creation or update of public-facing API documentation based on changes in the backend repository.
• Debugging Integration Issues: Assisting developers in troubleshooting connectivity, invalid PoW solutions, or rate-limiting responses encountered while attempting to interact with the API.
• Architecture Review: Offering insights into the current state of authentication, endpoint schemas, and the implementation of security measures like X-Api-Key headers.

Example Prompts

1. "How can I onboard my custom autonomous bot to start painting in Cubistic? Please explain the PoW requirements."
2. "Draft a markdown document for the public repository that explains the /api/v1/act endpoint, including request payloads and backoff strategies."
3. "Our bots are hitting 429 errors; can you review the recommended exponential backoff and jitter implementation for our script?"

Tips & Limitations

This skill is primarily a documentation-first assistant and does not inherently execute bot actions on the blockchain or network unless specifically instructed. When editing local repository files (such as PUBLIC_BOT_API.md), ensure you have appropriate write permissions. Always prioritize security by not hardcoding sensitive API keys in the generated documentation. If you are modifying the PoW verification logic in src/pow.mjs, remember to cross-reference the change with this skill to ensure the documentation remains synchronized with the backend logic.