ClawHub Publisher

Automate ClawHub skill package publishing, versioning, and release management.

1|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/bobvarkey/openclaw-workspace --skill clawhub-publisher
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ClawHub Publisher
Source: https://github.com/bobvarkey/openclaw-workspace/tree/main/skills/clawhub-publisher
Command: npx skills add https://github.com/bobvarkey/openclaw-workspace --skill clawhub-publisher

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

ClawHub Publisher removes the manual work from packaging, versioning, and deploying skills. It helps teams avoid repetitive release steps, inconsistent metadata, and slow publication workflows.

Core Features & Use Cases

  • One-command publishing: Push a skill to ClawHub with version and changelog details in a single workflow.
  • Release automation: Automatically bump versions, generate changelogs from git history, and validate required metadata before deployment.
  • Operational workflows: Bundle assets, inject Gumroad upsell links, track publishing history, roll back bad releases, and support team-based publishing.
  • Use case: A skill maintainer can prepare a release, validate the package, publish multiple skills in batch, and recover quickly if a deployment needs to be reverted.

Quick Start

Ask the skill to publish a skill directory to ClawHub with the desired version, changelog, and optional Gumroad link.

Frequently Asked Questions about ClawHub Publisher

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automate skill package publishing and versioning for ClawHub?

Automate skill package publishing and versioning for ClawHub by using a workflow that bumps versions, validates metadata, bundles assets, and pushes releases in a single command. This removes manual release steps and ensures consistent deployment.

Can I generate changelogs from git history automatically during skill deployment?

Yes, you can generate changelogs from git history automatically during skill deployment. The release automation workflow extracts commit history to create changelog details, validates required metadata, and bundles assets before publishing to ClawHub.

What is the best way to roll back a bad skill release after batch deployment?

The best way to roll back a bad skill release after batch deployment is to use operational rollback workflows that track publishing history. This allows maintainers to quickly revert bad deployments and recover failed publishing states across multiple skills.

Does ClawHub skill publishing support CI/CD pipelines and team-based operations?

Yes, ClawHub skill publishing supports CI/CD pipelines and team-based operations. The deployment behavior is designed for CI/CD-friendly automation, allowing teams to prepare releases, validate packages, and publish multiple skills in batch workflows.

How do I validate required metadata before publishing a skill package?

Validate required metadata before publishing a skill package by running the release automation workflow. It checks metadata consistency, bundles necessary assets, and injects optional Gumroad upsell links prior to executing the deployment command.