8.9
/ 10
1 evaluations
1.7k Downloads
Overview
Provide a structured checklist and lightweight audit tooling to prepare a Claw skill for safe, portable, high-quality public release (e.g., to GitHub or Clawhub).
Key Advantages
1.End-to-end publication checklist covering structure, security, portability, quality, docs, testing, git hygiene, and metadata.
2.Concrete, copy-pasteable shell commands for scanning for secrets, PII, hardcoded paths, debug artifacts, and TODOs.
3.Standardized expectations for SKILL.md and README.md, improving discoverability and reuse across skills.
4.Encourages good open-source practices, including licensing, tags, commit hygiene, and pre-push checks.
5.Provides an optional automated audit script that can be run before every publish for repeatable checks.
Use Cases
- Auditing a Claw skill before open-sourcing it on GitHub or publishing to Clawhub.
- Running periodic quality and security reviews on an existing portfolio of published skills.
- Setting up a team-wide standard for how Claw skills should be structured, documented, and licensed.
- Using the audit script in CI or as a local pre-publish step to catch secrets, hardcoded paths, and missing key files.
- Reviewing someone else’s Claw skill repo for structure, safety, and documentation gaps before adoption.
Evaluation Scores
8.9
/ 10
Reliability
8.3
Functionality
9.0
Usability
8.8
Safety
9.4
Performance
9.0
Compatibility
9.2
Based on 1 evaluation · Latest: 3/19/2026
Download Trend
Loading...
Evaluation History (1)
8.9/103/19/2026▼
OS: linux-arm64LLM: anthropic/claude-opus-4.6
**Judgement**
A mature, high-value meta-skill that significantly improves the quality and safety of Claw skills before public release. It is especially strong on security hygiene, documentation standards, and reproducible auditing.
**Strengths**
- Very comprehensive checklist across structure, security, portability, code quality, docs, testing, git, and metadata.
- Practical, command-level guidance (grep patterns, example scripts, directory structure) rather than abstract advice.
- Strong emphasis on secret/PII removal and safe example data, which directly reduces security leakage risk in published skills.
- Clear SKILL.md and README.md templates that promote consistent, reusable skill documentation.
**Key Risks / Limitations**
- Automated checks are grep-based and limited to markdown files; sensitive data in other file types or less obvious formats may be missed.
- Heavy reliance on Unix-like tooling (bash, grep) may reduce out-of-the-box usability on pure Windows environments without a POSIX shell.
- The checklist is only as effective as the diligence of the human following it; it does not enforce compliance.
**Recommended Scenarios**
- Default publication gate for any Claw skill being made public (GitHub, Clawhub, or internal catalog).
- Team standards document for how to structure, document, and secure skills in a multi-contributor repository.
- CI or pre-publish step where the included audit script is run and failures block release until remediated.
Overall, this skill is well-suited as a foundational quality and security layer in any serious Claw-skill development workflow.
Comments (0)
No comments yet. Be the first!