Content
71%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 a lean, well-sectioned runbook with explicit confirmation and fail-fast validation for a destructive batch operation — stronger than typical. Its main gaps are mechanical: the referenced discovery script and asset files are absent from the bundle, and the per-branch deletion block omits the branch-to-worktree mapping and conditional guards that the surrounding prose promises.
Suggestions
Ship the discovery script in the skill's scripts/ directory (or inline the git commands it wraps, e.g. `git branch -vv` / `git for-each-ref` filtering for gone upstreams) so the core step is executable from the bundle.
Show how to resolve a branch to its worktree path (e.g. `git worktree list --porcelain`) and make non-root-worktree exclusion a condition on the `git worktree remove` command instead of relying on step 7 prose.
Remove or honor the dangling asset links and the reference pointer; either add the files or drop the "Full Context" section and the "Use references only..." line so every path in SKILL.md resolves.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is terse and imperative throughout with zero explanation of git concepts Claude already knows. It is not a 5 because the confirmation rule is restated across Philosophy, Procedure, Validation, Constraints, and Anti-Patterns, and the "Inputs" section ("Request, artifacts, repo context, and linked Linear issues") adds almost no value. | 4 / 5 |
Actionability | Concrete, executable commands are given for every phase (discovery script invocation, `git worktree list`, `git worktree remove --force "<worktree_path>"`, `git branch -D "<branch>"`). It is not a 5 because the core discovery script is not shipped in the bundle, and how to map a candidate branch to its `<worktree_path>` is never shown, leaving the deletion block not fully copy-paste ready. | 4 / 5 |
Workflow Clarity | The numbered procedure has real validation checkpoints (`__NONE__` exit, one yes/no gate before any destructive action, a dedicated fail-fast Validation checklist) plus failure-mode recovery including continuing after a per-branch failure. It is not a 5 because the per-branch block runs `git worktree list` inside the loop and applies `--force` unconditionally, leaving the root-worktree and active-branch guards as post-hoc prose in steps 7 and Validation rather than explicit conditions in the destructive sequence. | 4 / 5 |
Progressive Disclosure | Sections are well-organized, but scored against the actual bundle structure the references do not resolve: there is no scripts/, references/, or assets/ directory, so `Plugins/harness-engineering/.../scripts/clean-gone`, `./assets/icon-small.png`, and `./assets/icon-large.png` are dangling, and "Use references only when additional edge handling is needed" points at nothing. This matches the anchor for structure present but references not clearly backed/organized. | 3 / 5 |
Total | 15 / 20 Passed |