Conciseness

The body is dense and operational with no padding and no explanations of concepts Claude already knows; harness-specific facts (stash shared across worktrees, EnterWorktree re-rooting limits) genuinely need stating. Not 5 because a few passages restate the same constraint multiple ways — e.g., the agent-pinned-to-worktree limitation appears twice in step 3, and the repo/branch disambiguation paragraph is a long run-on that could be tightened.

Actionability

Fully executable throughout: exact tool calls (`EnterWorktree({name: "<branch>"})`, `ExitWorktree({action: "keep"})`), a copy-paste CLI command (`wt -C <repo> switch --create <branch> --no-cd --format=json`), the JSON `path` field to read, literal error strings to match ("Already in a worktree session", "Branch <branch> already exists", "Shell cwd was reset"), and four concrete invocation examples.

Workflow Clarity

Steps 1-3 are clearly sequenced with creation-first mandated on every invocation, and each failure path has an explicit feedback loop: stash push/pop with restore-on-failure, branch-exists rerun without `--create`, the `cd`-test recovery split into reachable (pin with `git -C`) vs. Unreachable (ask user to add the directory, then continue), and Denied (report path and ask). Stop-and-ask conditions are stated for unresolvable inputs.

Progressive Disclosure

Well-sectioned single file (argument grammar, examples, What to do, Cleanup, Scope) with all operational content appropriately inline, and maintainer rationale split out to a one-level reference. Not 5 because the referenced `rationale.md (same directory)` is absent from the bundle (no references/ or sibling file exists), leaving a dangling reference; not 3 because structure is clear and nothing that belongs in a separate file is inlined.

Specificity

Names several concrete actions — "Create a new worktrunk worktree (optionally in another repo) and switch this session's working directory into it" — three distinct capabilities in third person. Not 5 because coverage is not comprehensive (e.g., stash carry-over and cleanup are body-only); not 3 because it lists more than 1-2 actions.

Completeness

The what is explicit ("Create a new worktrunk worktree ... and switch this session's working directory into it") and the when is an explicit "Use when launching a session that should work in its own worktree" clause. Not 5 because the when-clause covers only the session-launch scenario with a single trigger phrase, while the body also supports mid-session worktree moves; not 3 because both what and when are clearly stated.

Trigger Term Quality

"worktree", "worktrunk", "session", "own worktree", "switch" are natural terms a user needing this skill would say. Not 5 because common variations like "git worktree", "isolate", or mid-session phrasings ("move to a worktree") are missing; not 3 because the dominant natural keyword plus context terms are present and prominent.

Distinctiveness Conflict Risk

"worktrunk worktree", session working-directory switching, and the launch-scenario trigger form a clear niche tied to a named tool with minimal overlap risk. It would not plausibly fire for unrelated skills; the create-plus-switch framing also distinguishes it from a plain switch command.