Conciseness

The body is two lines — a generation comment and a single load instruction — with zero padding and no re-explanation of concepts Claude already knows. Every token present earns its place, matching anchor 5 exactly; anchor 4 would require trimmable over-explanation that does not exist here.

Actionability

The one instruction — "Load and follow the shared skill at `~/.agents/skills/new-project/SKILL.md`" — is concrete and executable, but all guidance for the actual scaffolding task is delegated away, leaving key details absent from the body. This is anchor 3 (some concrete guidance but incomplete) rather than 4, since the body contains no actionable direction for the task itself, and above anchor 2 because the directive is specific, not a high-level hint.

Workflow Clarity

No sequence for the multi-step scaffolding process appears in the body — only a single coherent delegation directive with no validation checkpoints. It sits above anchor 1 because the one instruction present is unambiguous, but below anchor 3 because no actual work steps are listed at all, leaving many gaps as in anchor 2.

Progressive Disclosure

The reference is clearly signaled and one level deep, but the body is a pure redirect with no overview content, and neither referenced path exists in the bundle (`~/.agents/skills/new-project/SKILL.md` is outside the skill and unverifiable; `scripts/agent-harnesses.py` is absent). This matches anchor 3 (some structure, organization concerns) rather than 4, since content is not appropriately placed or split within the skill itself.

Specificity

Lists several concrete, named actions — "scaffolds mise-pinned tools, a just task surface, ... and CI for Python (uv), TypeScript (bun), Rust (cargo), or Go" — but "the standard repo files" is unspecified, leaving a minor coverage gap. This matches anchor 4 (several specific actions, minor gaps) rather than 5, and is well above anchor 3's 1-2 actions.

Completeness

Explicitly answers "when" with a concrete "Use when invoked as $new-project or when creating a brand-new repository or project from scratch" clause and "what" with specific scaffolding actions and named per-language tooling. This clearly matches anchor 5 (both what and when with concrete trigger phrases); the 4 anchor requires a weaker or less explicit 'when', which does not apply.

Trigger Term Quality

Natural triggers like "creating a brand-new repository or project from scratch" and "invoked as $new-project" are present, but common variations users might say — "scaffold", "set up", "initialize", "boilerplate", "starter" — are missing. Good coverage without being comprehensive puts this at anchor 4, above anchor 3's partial keyword set and below anchor 5's full synonym coverage.

Distinctiveness Conflict Risk

The from-scratch scaffolding niche with a named toolchain (mise, just, uv/bun/cargo/Go CI) and the distinct "$new-project" invocation make it mostly distinct with only minor overlap risk against generic project-setup or language-specific init skills. Anchor 4 fits better than 5 because "creating a brand-new repository or project" remains somewhat broad as a trigger.