Conciseness

The two-sentence intro conveys only non-obvious environment facts ('on PATH in the gateway', 'persist across tool-call boundaries'), and every command carries a single-purpose comment with zero padding — every token earns its place.

Actionability

All commands are copy-paste executable and cover the common cases (new-session -d, capture-pane with -S -1000 scrollback, send-keys with the C-m note), and the status-flag pattern is a complete, correctly escaped executable script.

Workflow Clarity

Each single action is unambiguous (simple-skill case), and the flagship pattern sequences start → later check of /tmp/build.exit → report status or tail the log, providing an explicit checkpoint with no validation gaps.

Progressive Disclosure

No bundle files exist and none are needed at this scope — all content is core overview material appropriately inlined, organized into clear one-level sections with easy navigation.

Specificity

Lists four concrete actions ('start a detached session, run a long task, reattach later, capture output'), but omits sending input and ending sessions, which the body covers — minor gaps in coverage matching the 4 anchor rather than the comprehensive 5 anchor.

Completeness

Explicitly answers both what ('start a detached session, run a long task, reattach later, capture output') and when ('Use when a task takes longer than a single tool call (build, test, log tail)') with concrete trigger phrases, matching the 5 anchor exactly.

Trigger Term Quality

Includes natural trigger phrases users would say ('build, test, log tail', 'long-running', 'reattach') alongside the tool name tmux, but misses common variations like 'background task' or 'keep it running', so it falls short of the 5 anchor's synonym coverage.

Distinctiveness Conflict Risk

Names a specific tool (tmux) with a niche trigger condition (tasks outlasting a single tool call), giving it a clear trigger surface with minimal conflict risk against other skills.