Content
72%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 maximally concise and appropriately minimal for a small single-purpose skill, with no bundle overhead. Its main weakness is that the core step — moving the worktree to a new branch off origin/main — is stated as a goal rather than an executable command sequence, which is non-trivial in git worktrees and where the real value of the skill should live.
Suggestions
Provide the concrete command sequence for the branch move, e.g. 'git switch --detach origin/main && git switch -c <new-branch>' (noting a worktree cannot check out a branch that exists elsewhere), or equivalent.
Add brief guidance on choosing the new branch name (e.g. from the next task or ticket identifier).
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is two lean bullet lines with zero padding or explanation of concepts Claude already knows; every token earns its place. | 5 / 5 |
Actionability | 'Run `git fetch`' is a concrete executable command, but 'Move this worktree to a new branch off of `origin/main`' provides no command and is genuinely ambiguous — moving a worktree to a new branch involves a non-obvious command sequence (branch naming, worktree branch-checkout constraints) that the reader must reconstruct. | 3 / 5 |
Workflow Clarity | A rough two-step sequence is present and ordered, but step 2 is underspecified (no command, no branch-naming guidance) and there is no check that the new branch state is correct; the operation is neither destructive nor batch, so no hard cap applies. | 3 / 5 |
Progressive Disclosure | The skill is under 50 lines, has no bundle files, and needs no external references; nothing here belongs in a separate file, so the minimal bullet structure fully satisfies progressive disclosure for a skill of this size. | 5 / 5 |
Total | 16 / 20 Passed |