Content
100%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
An exemplary skill body: a tightly sequenced git workflow with executable commands, explicit safety constraints, validation checkpoints, and error-recovery loops, all delivered with zero padding. Nothing material is missing or misplaced.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's git competence: no concept explanations, just operational constraints ("Do not rebase, reset, or force-push", "Never pop or drop a pre-existing stash") and commands. Every token earns its place. | 5 / 5 |
Actionability | Every step carries a copy-paste-ready command (git merge --ff-only, git stash push --include-untracked, rg conflict-marker grep, bun run build), and placeholders like <canonical-remote> and <recorded-stash-commit> are resolved by earlier steps, so the guidance is fully executable. | 5 / 5 |
Workflow Clarity | A clear 9-step sequence with explicit validation checkpoints (step 7: git diff --check, --cached --check, tests, build/stylecheck) and genuine feedback loops (conflict resolution: resolve -> grep markers -> stage -> commit; stash conflicts: resolve without re-applying). The destructive-operation cap does not apply because validation is present. | 5 / 5 |
Progressive Disclosure | A self-contained, short, single-workflow skill with no bundle files and no content that belongs in external references; the single well-organized Workflow section is the appropriate structure, which the rubric's simple-skill note treats as full marks. | 5 / 5 |
Total | 20 / 20 Passed |