clawhub-publisher

What This Skill Does

The clawhub-publisher skill is an essential developer tool designed to streamline the lifecycle of publishing AI agents and skills to the ClawHub ecosystem. It provides a robust, professional-grade interface for handling the distribution of OpenClaw assets. By encapsulating complex authentication, versioning, and distribution logic, it eliminates the manual overhead typically associated with packaging and deploying code modules. It automatically manages API token validation, ensuring that security credentials are handled correctly before attempting any remote operations.

Installation

To install this skill, run the following command in your terminal: clawhub install openclaw/skills/skills/charpup/openclaw-clawhub-publisher

Ensure you have configured your environment by creating a .env file containing your CLAWHUB_TOKEN or by exporting it as a system-wide environment variable. You can verify your installation by executing node lib/clawhub-publisher.js login to confirm the handshake between your local workspace and the ClawHub servers.

Use Cases

• Automated CI/CD Pipelines: Integrate the publisher into existing GitHub Actions or local build scripts to automatically publish verified skills upon successful merge.
• Batch Deployments: Developers managing a portfolio of agents can use the batch publish feature to roll out updates to multiple skills simultaneously, ensuring version parity across their entire catalog.
• Error Resilient Distribution: In environments where network instability is a concern, the skill provides a critical fallback mechanism, automatically switching between CLI execution and direct API interactions to maximize the chances of a successful deployment.

Example Prompts

1. "Publish the skill located at ./my-agent with version 1.2.0 and include the changelog: 'Fixed memory leak issue'."
2. "Run a batch publish for all skills in my ./projects directory using the latest tag and version 2.0.1."
3. "Verify my current ClawHub connection status and retry the last failed deployment for the 'data-parser' skill."

Tips & Limitations

• Token Security: Never commit your .env file to version control. Always use environment variables in CI environments.
• Project Structure: Ensure that your skill directory contains the required SKILL.md file, as the publisher strictly validates the project structure before proceeding.
• CLI vs API: The skill prioritizes CLI performance, but if your local environment lacks the necessary dependencies for the CLI tool, the API fallback will consume significantly more bandwidth and potentially be slower for large asset uploads.