skill-prooflisted

# Skill Proof ## Workflow 1. Identify the target skill folder. It must contain `SKILL.md`. 2. Run the bundled proof script when Node.js is available: ```bash node scripts/skill_proof.mjs <target-skill-folder> --out skill-proof-output --fail-on high ``` 3. Read `skill-proof-output/skill-proof-report.md` first, then inspect `skill-proof-output/skill-proof.json` for machine-readable details. 4. Fix high-severity findings before recommending publication. 5. Use `skill-proof-output/evals.json` as starter trigger tests in a fresh agent context. ## Manual Review Use `references/checklist.md` when a finding needs judgment rather than a mechanical fix. Prioritize these questions: - Does the frontmatter `description` say when to use the skill? - Does the body stay procedural instead of becoming a long knowledge dump? - Are deterministic or risky operations moved into scripts? - Are references and assets discoverable from `SKILL.md`? - Are there hard-coded local paths, real secrets, or unsafe shell commands? - Could a stranger install the skill and understand the release evidence? ## Repair Guidance When editing a target skill, keep changes narrow and preserve the author's intent. Improve the release gate in this order: 1. Fix invalid frontmatter, missing name, invalid name, or placeholder description. 2. Move trigger conditions into frontmatter `description`. 3. Remove secrets and replace local paths with placeholders. 4. Guard destructive commands with expl