Content
87%Weight 40%Scale 1-3Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is actionable, concise, and well-organized. The main gap is workflow_clarity: the verification step for destructive worktree removal is decoupled from the numbered workflow rather than integrated as an explicit checkpoint.
Suggestions
Integrate the pre-removal verification directly into the Workflow as an explicit checkpoint, e.g. step 4: 'Before removing, verify changes are committed: `git -C ../project-feat status`; if uncommitted, commit or stash first, then `git worktree remove`.'
Add a brief feedback loop ('if remove fails due to uncommitted changes, commit/stash and retry') so the destructive step has a validate-fix-retry cycle.
De-duplicate the `git worktree add ../project-feat feature-branch` example between Quick Start and Commands to tighten token efficiency.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and assumes Claude's competence, using commands and a table rather than explaining git/worktree concepts; minor repetition between Quick Start and Commands keeps it just at the lean anchor. | 3 / 3 |
Actionability | Provides fully executable, copy-paste-ready commands (`claude -w`, `git worktree add/list/remove/prune`, `git -C ../project-feat status`) plus concrete usage patterns. | 3 / 3 |
Workflow Clarity | The 4-step Workflow is sequenced and a validation checkpoint exists ('Before removing a worktree, verify changes are committed'), but for a destructive operation that checkpoint sits in a separate Guardrails section rather than embedded as an inline validate-fix-retry loop in the workflow. | 2 / 3 |
Progressive Disclosure | Single well-organized file with clear logical sections and no nested/deep references; appropriate for a self-contained skill with no bundle files. | 3 / 3 |
Total | 11 / 12 Passed |