clawhub-publish

What This Skill Does

The clawhub-publish skill serves as the backbone for managing the lifecycle of OpenClaw agent skills. It provides a comprehensive command-line interface that bridges the gap between local development, version control, and the public ClawHub registry. By automating the repetitive aspects of software distribution—such as semver validation, git tagging, and registry synchronization—this skill ensures that your updates are deployed reliably and consistently. It integrates seamlessly with Notion for task tracking, ensuring that every deployment is correctly documented and mapped to internal project management workflows.

Installation

To begin using the utility, ensure you have the ClawHub CLI installed globally: npm install -g clawhub. Once installed, authenticate using clawhub login. You can then integrate the skill directly into your development environment by running: clawhub install openclaw/skills/skills/briansmith80/clawhub-publish. Ensure that your local machine has a configured Git remote origin and that your GitHub Personal Access Token is accessible via your secure credentials manager as documented in your project workspace.

Use Cases

This skill is ideal for teams and individual developers maintaining agent repositories. Use it to perform rapid hotfixes where a security patch must be pushed instantly across the registry, or for standard CI/CD pipelines where feature releases require automated changelog generation and version bumping. It is also highly effective for synchronizing technical task completion with project management tools, ensuring that when code hits the registry, the corresponding Notion card is automatically moved to the 'Done' status.

Example Prompts

1. "Publish a patch update for my utility skill located at ~/projects/web-scraper with the message: Fixed login race condition during OAuth handshake."
2. "Perform a dry run of the next minor release for the data-parser skill to verify versioning and changelog formatting before actual deployment."
3. "Push a major update for the research-agent skill, bump the version automatically, and link it to the Notion task with ID 26c29e15."

Tips & Limitations

Always perform a --dry-run before executing public pushes to verify that your changelog and version tags are formatted correctly. Keep in mind that this skill requires access to your local file system and GitHub credentials; ensure these are protected in a secure environment. If you are working on a team, confirm that your branch protections allow for the automatic commits and pushes generated by the script to avoid friction during the deployment phase. Finally, note that while the script automates the registry process, you are responsible for testing the underlying skill functionality before publication.