skill-workshop

Topics in the source

• skill-workshop
• When to load
• At work-done — the gate
• The two passes
• Model-upgrade mode
• Commands
• References
• Gotchas

Authoring rules, validator and auditor for Claude Code skills. The rules are distilled from docs/research/claude-skill-systemv1.17.md; open that only when extending the rule set. CANARY: skill-workshop-loaded-2026-08-22-ceb6dc3efb38428d Load it before any file under a skills/ / folder changes (SKILL.md, references/, scripts/, assets/, evals/), including through Bash; when reviewing a skill diff; when a skill fails to load or trigger; and when running the validator or auditor by hand. Before reporting skill work as finished, run both passes on every skill folder changed this session, because load and routing failures are silent at runtime and only these checks surface them. 1. Mechanical. validate.py for each changed skill (exit 0 clean, 1 failure, 2 internal error), then one auditlibrary.py per changed library for the listing budget and cross-skill checks. It takes under a second per skill, so it always runs. 2. Semantic. Once the mechanical pass is clean, walk references/skill-rules.md, then references/content-quality-rules.md, against the current state of the files changed this session. A must finding stops the gate until the user fixes, dismisses or defers it; a should finding i

This is an excerpt. Refer to the complete source and its current requirements.