Menu
Check this repo's skill invariants (name==folder==kebab-case, unique leaf names, every skill in its area README) and fix violations.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Use before any creative/build work — adding features, building components, new functionality, or changing behavior. Turns a brief or vague idea into an approved design doc through one-question-at-a-time dialogue. Does NOT write code until the design is approved. Output is the design doc; the next step is owned by the caller.
Craft a clear /goal condition for Claude Code's autonomous mode from a rough task description.
Convene an independent cross-model judge — a model of a different family (e.g. Codex/GPT, Gemini, or a Cursor agent pinned to a non-Claude model), whichever CLI is installed — to cross-examine an artifact (a decision, a diff, a document, or a research answer) and adjudicate its findings disbelieve-it-back. This is the cross-model *mechanism*; the caller brings the artifact and its own in-family review. Use via `vet` (code), `research-council` (research), `plan` (a design decision), or directly when you want a second opinion from a model that doesn't share your blind spots. It reviews; it never edits.
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
Reference for writing and editing skills well — the vocabulary and principles that make a skill predictable.
Build and sharpen a project's domain model. Use when the user wants to pin down domain terminology or a ubiquitous language, record an architectural decision, or when another skill needs to maintain the domain model.
| name | validate-skills |
| description | Check this repo's skill invariants (name==folder==kebab-case, unique leaf names, every skill in its area README) and fix violations. |
| disable-model-invocation | true |
The fast gate that proves skill changes are sound before install.sh would catch them.
./scripts/validate-skills.sh
install.sh:
name != folder → make the name: frontmatter match the leaf folder name exactly.not kebab-case → rename to lowercase words joined by single hyphens.duplicate leaf name → rename one; leaf names are unique across the whole repo.no 'name:' → add the frontmatter name: line.README.md — add the one-line row
(unless the skill was just removed, in which case delete its stale row).0 error(s). Treat that as the done-condition for skill changes.install.sh's discovery (same domains, same pruned dirs), so passing here
means ./install.sh --dry-run will link cleanly.