skill-releaser

What This Skill Does

The skill-releaser is the primary orchestrator for the OpenClaw publication pipeline. It transforms a local, potentially unrefined skill directory into a production-ready package hosted on ClawHub. This skill handles the end-to-end lifecycle, including auto-scaffolding (ensuring the directory structure meets compliance standards), running automated OPSEC/security scans, and managing the multi-stage push process. It acts as a safety gatekeeper, ensuring that no code reaches the public ecosystem without both agent-level verification and explicit human approval.

The system utilizes a two-phase architecture. Phase 1 focuses on scaffolding and staging, where the agent formats the files and pushes them to a private GitHub repository for the user to inspect. Once the human user reviews the repo via their preferred interface and provides an 'approve' signal, the agent enters Phase 2. This phase performs a surgical cleanup of the repository history (flattening to a clean state), toggles the repository to public, registers the skill on ClawHub, and verifies the final security state before closing the loop.

Installation

To install this skill, use the following command within your OpenClaw environment: clawhub install openclaw/skills/skills/chunhualiao/skill-releaser

Use Cases

• Standard Publication: When you have a finished SKILL.md and project files ready to be shared with the community.
• Readiness Auditing: When you want to check if your current project structure follows OpenClaw standards before attempting an actual release.
• Batch Workflow: Managing the deployment of multiple skills simultaneously by leveraging the agent's ability to track disparate stages of the pipeline in a persistent, asynchronous manner.
• Security Enforcement: Automatically ensuring that proprietary information or unsafe code patterns are purged before your project goes public.

Example Prompts

1. "I've finished the documentation for my new web-scraper skill. Can you prepare it for release and set up a staging repo for me to review?"
2. "Review the current status of my 'data-analyzer' project. Is it ready for publication on ClawHub, or are there missing files?"
3. "The repo looks good, I approve the publication. Go ahead and push the skill to ClawHub."

Tips & Limitations

• Pre-requisites: You must ensure gh CLI is authenticated. The agent cannot create repositories or manage visibility settings without authorized credentials.
• The Human Gate: This is a hard-gate system. Even if all automated checks pass, the agent will never bypass your final review. Always check the private repository link provided by the agent.
• Content Quality: While this tool handles structure and compliance, it does not write the skill's logic for you. You must provide a valid SKILL.md describing the functionality.
• Resumability: If the process is interrupted, you can resume at any time. The staging repository keeps the state, so you don't lose progress on complex publishing tasks.