Content
92%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.
The body is an exemplary lean, single-purpose skill: a clearly sequenced three-step workflow with genuine validation checkpoints (verify worktree exists, verify the cwd switch took effect) and stop-on-error guidance, with no padding or over-explanation. The only gap is that some steps read as templates with placeholders rather than fully copy-paste-ready commands.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The ~45-line body explains nothing Claude already knows and every step earns its place ("Verify the worktree exists in `git worktree list` output. If not, stop with an error."). The only nit is the line "Switch the current session to an existing worktree." echoing the title, which does not drop it below anchor 5. | 5 / 5 |
Actionability | Commands like `git worktree list`, `cd WORKTREE`, `pwd`, and `git branch --show-current` are concrete, but `WORKTREE`/`NAME` placeholders and the "Switched to worktree: WORKTREE" report block are templates rather than copy-paste-ready commands. This matches anchor 4 (mostly executable, minor gaps) rather than 5 (fully copy-paste ready). | 4 / 5 |
Workflow Clarity | The sequence resolve -> verify exists -> cd -> verify cwd persisted -> report has explicit validation checkpoints at both risky points with stop-on-error handling ("If `pwd` does not show `WORKTREE`, stop with an error"). This is a simple, non-destructive skill, so the batch/destructive validation cap does not apply, and the simple-skill exception holds. | 5 / 5 |
Progressive Disclosure | The skill is under 50 lines, needs no external references (none exist in references/scripts/assets), and is organized into clean 'Resolve / Switch cwd / Report' sections. Per the simple-skill guideline, well-organized sections alone merit anchor 5 here. | 5 / 5 |
Total | 19 / 20 Passed |