Skill Publisher Claw Skill

What This Skill Does

The Skill Publisher Claw Skill is a comprehensive framework designed for AI agents and developers to audit, package, and prepare OpenClaw skills for public distribution. It acts as an automated quality assurance layer that enforces standardized documentation, security compliance, and organizational rigor. By using this skill, you ensure that any component you publish to GitHub or ClawdHub adheres to a strict eight-point checklist, covering structural integrity, sensitive data sanitization, portability across different host environments, and clean commit history. It is the essential final step before any code or documentation reaches the public domain.

Installation

You can install this tool directly using the OpenClaw CLI by executing the following command in your terminal: clawhub install openclaw/skills/skills/acastellana/skill-publisher-claw-skill Once installed, you can invoke the auditor by referencing the skill name or using any of the recognized triggers such as 'publish skill' or 'audit skill'.

Use Cases

• Pre-Release Audits: Automatically scanning a new skill for hardcoded API keys, environment variables, or private configuration files before a public push.
• Collaborative Review: Using the standardized checklist to review third-party contributions, ensuring they meet the repository's structural requirements for SKILL.md and README.md files.
• Repository Health: Performing periodic maintenance on older skills to ensure they remain compatible with updated AI agent specifications and security best practices.
• Standardization: Enforcing naming conventions and file organization to prevent the 'single-massive-file' anti-pattern.

Example Prompts

1. "I am ready to release my new research skill. Please run the full security and quality audit on my current directory."
2. "Check my skill structure against the publisher checklist and let me know if my SKILL.md file is missing any required headers."
3. "Scan my repository for potential security leaks, like hardcoded tokens or email addresses, before I submit this to ClawdHub."

Tips & Limitations

To maximize the effectiveness of this skill, ensure that you run the audit within the root directory of your skill project. Note that while the tool is excellent at identifying common patterns for PII and secrets, it does not replace a manual code review for logical vulnerabilities. Always prioritize the manual verification step in the checklist, especially if your skill handles user-provided authentication data. Keep your repository clean by using standard .gitignore templates provided by the OpenClaw documentation.