Clawhub Publish Best Practicesv1.0.1

A development team needs to publish a batch of new skills to the ClawHub marketplace. By following the best practices outlined, they can avoid common pitfalls like exceeding rate limits or publishing duplicates, ensuring a smooth and efficient publication process.

A developer working on internal agent skills (e.g., self-improving-agent) uses this guide to avoid mistakenly publishing them to the public marketplace. The guide's rule to only publish listed skills prevents data exposure and unnecessary conflicts.

When attempting to publish a skill with a slug that is already taken (e.g., 'mcdonalds'), the developer refers to this guide to skip it, record the conflict, and move on without wasting time on invalid workarounds. This preserves the integrity of the skills list.

A team managing a portfolio of skills uses the documented rate limits (5 new skills/hour, 20/24 hours) to plan their publishing schedule. They batch updates separately to avoid hitting quotas, ensuring continuous deployment without interruptions.

After publishing skills, a project lead promptly updates the maintenance files (e.g., PUBLISHED_SKILLS_MAINTENANCE.md) with skill IDs and timestamps, then verifies each skill's availability. This ensures accurate tracking and accountability across the team.

Third-party developers curate and publish high-value skills (e.g., brand-specific integrations) on ClawHub, monetizing through subscription fees or pay-per-use. The best practices ensure efficient publication and conflict avoidance.

Enterprises maintain a private catalog of agent skills for internal automation. This guide helps them manage the publication pipeline, preventing accidental public exposure and ensuring smooth updates across departments.

Consultants offer services to help teams adopt these best practices, including audit of existing skills lists, rate-limit planning, and workflow automation. Revenue comes from one-time engagements or ongoing support.