Conciseness

The body is two lines — a generated-by marker and "Load and follow the shared skill at `~/.agents/skills/cmux-workspace-status/SKILL.md`" — with zero padding and nothing Claude doesn't need. Every token earns its place; this matches the lean anchor 5 exactly.

Actionability

The single instruction is concrete (an exact path to load and follow), but the executable guidance for the skill's actual task — the `cmux workspace status set done` command, when to run it, how to verify the goal — is entirely absent from the body and delegated to an external file outside the bundle. This fits anchor 3 (concrete but incomplete, missing key details) better than anchor 4, which expects actual code or commands in the content.

Workflow Clarity

As a simple single-task skill the one action ("Load and follow the shared skill...") is unambiguous, which supports a high score under the simple-skill exception. However the body provides no checkpoints or fallback for the delegation itself — nothing to do if the shared skill file is absent — and no steps for the underlying status-setting operation, leaving minor validation gaps characteristic of anchor 4 rather than a clean 5.

Progressive Disclosure

The reference is clearly signaled and one level deep (no nested chains), and nothing that belongs in a separate file is inlined. It stops short of anchor 5 because the pointer targets an absolute path outside the bundle (`~/.agents/skills/...`) rather than a bundle-relative file, and the header comment cites `scripts/agent-harnesses.py` which does not exist in the bundle (no references/, scripts/, or assets/ directories are present).

Specificity

"Pin the current cmux workspace to the done lane with `cmux workspace status set done`" names the exact command, the target state (done lane), and the condition ("once a session goal is reached and verified") — fully concrete and comprehensive for a single-action skill. It exceeds anchor 4 because there are no gaps in coverage: the skill has one action and it is stated verbatim.

Completeness

Both questions are answered explicitly: the what ("Pin the current cmux workspace to the done lane with `cmux workspace status set done`") and the when ("Use at the end of a work session running inside a cmux terminal, right before the final response"), plus concrete skip conditions ("blocked, handed off, awaiting user input, or when nothing was changed"). This matches the anchor 5 example's structure of what + explicit trigger guidance, and the 'Use when' clause is present so no cap applies.

Trigger Term Quality

Natural domain terms are present: "cmux terminal", "workspace", "done", "work session", "session goal" — the phrases a cmux user would actually say. It falls short of anchor 5 because common synonyms and variations ("finish session", "wrap up", "complete", "mark done") are absent.

Distinctiveness Conflict Risk

The description occupies a clear niche — cmux workspace lifecycle management — anchored by the product-specific terms "cmux", "workspace", and "done lane" and the literal command. Minimal conflict risk with any generic skill; it would not plausibly trigger for the wrong skill.