skill-review

# Skill Review Review a skill as an execution contract, not as prose. Trace how an agent would enter, load, delegate, produce artifacts, and verify results; then report the smallest changes that would improve that chain. ## Review Workflow 1. Resolve the target skill or prompt chain. If the user names a path, stay on that path and its directly linked resources. 2. Read repo instructions first: nearest `AGENTS.md`, plugin manifests, and the target `SKILL.md` frontmatter/body. 3. Trace the chain from entrypoint to references, templates, scripts, detectors, tests, generated artifacts, and validation commands. Build an ownership map: what file owns workflow, output structure, runtime rules, style, and tests. 4. Audit the contract before editing. Use [Audit Checklist](references/audit-checklist.md) and [Reference Patterns](references/reference-patterns.md) as lenses. 5. If the user asked for changes, patch only the smallest owning files. Keep generated helpers, smoke scripts, and local experiments outside `SKILL.md` unless they are durable resources the skill must use. 6. Validate with the lightest real gate available: skill validator, repo tests, plugin validation, or a bounded agent smoke. State any gate that could not be run. Use subagents only as an evaluation surface or for independent broad research. The lead agent owns the review, final calibration, and file edits. Pass raw artifacts and task-local scope to subagents; do not pass the intended ...