Lean command reference with no concept explanations: terse tables, code blocks, and project-specific gotchas (e.g. the STORE_ENCRYPTION_KEY warning) that add only what Claude would not already know.

Provides fully executable commands throughout — the rsync include/exclude block, the git ls-files copy loop, install/build/remove commands — with real example paths, copy-paste ready.

A single-purpose reference whose sections follow the worktree lifecycle and include explicit checkpoints ('Abort if WORKTREE already exists', 'After copying, list what landed', remove safety guidance); the batch/destructive operations are guarded, so the cap does not apply.

No bundle files are needed; the body is well-organized into focused sections and clearly delegates broader concerns to one-level sibling skills ('Prefer nv-worktree-create for the end-to-end flow', 'read nv-worktree-cleanup').

Lists multiple concrete operations — 'path naming, create/remove/prune, `.env*` copy, package-manager install, and cleanup' — matching the anchor for several specific concrete actions rather than vague language.

Explicitly answers both what ('Git worktree command reference: ...') and when ('Use when implementing or debugging worktree setup'), matching the anchor requiring an explicit trigger clause.

Uses natural terms a developer would say ('git worktree', 'worktree setup') and an explicit 'Use when implementing or debugging worktree setup' trigger, giving good coverage for this narrow domain.

Clear niche (git worktree commands) and it actively disambiguates from a sibling skill — 'not as the primary user-facing workflow (see nv-worktree-create)' — so it is unlikely to trigger for the wrong skill.