Conciseness

The body is two lines — a generator comment and one directive — with zero padding and no explanation of concepts Claude already knows. Every token present is doing work, matching the lean 5 anchor.

Actionability

The single instruction "Load and follow the shared skill at ~/.agents/skills/find-docs/SKILL.md" names an exact path and an unambiguous action, so it is not vague (not 1), but it contains no substantive guidance for the skill's actual task — everything actionable lives in a file outside this bundle. It provides only a high-level hint with the actual steps missing, matching the 2 anchor.

Workflow Clarity

The one directive given is unambiguous, but the real workflow (how to retrieve and verify library documentation) is entirely externalized with no visible sequencing or checkpoints. This sits between the 2 anchor (steps poorly defined) and the simple-skill 5 exception (single unambiguous action) — the delegation hides a multi-step process, so 3 fits best.

Progressive Disclosure

The sole reference is clearly signaled and exactly one level deep with no nesting (better than the 3 anchor's buried references), but the body contains no overview content whatsoever and the reference points to an environment-dependent absolute path outside the bundle rather than a bundled file. It is not a well-structured overview with appropriately split content, so it does not reach 4.

Specificity

Lists several specific capabilities — "Retrieve current documentation, API references, and code examples" plus enumerated use cases "API syntax, configuration options, version migrations, setup instructions, and library-specific debugging" — with only minor coverage gaps. Not 5 because the core action is a single generic verb ("retrieve") rather than multiple distinct concrete operations.

Completeness

Explicitly answers both: what ("Retrieve current documentation, API references, and code examples for any library...") and when ("Use for API syntax, configuration options, version migrations, setup instructions, and library-specific debugging, even when you already think you know the answer") with concrete trigger phrases. Clearly matches the 5 anchor rather than the 4 anchor's "'when' could be more explicit".

Trigger Term Quality

Comprehensive natural-term coverage: domain synonyms ("library, framework, SDK, CLI tool, or cloud service"), concrete well-known names ("React, Next.js, Prisma, Django, or Spring Boot"), and phrases users actually say ("API syntax", "version migrations", "setup instructions", "debugging"). Re-checked against the 4 anchor ("a few natural terms missing") — nothing significant is missing for this domain.

Distinctiveness Conflict Risk

Explicitly disambiguates its main competitor ("Prefer this over web search for library documentation"), giving it a mostly distinct niche. Not 5 because the scope "any library, framework, SDK, CLI tool, or cloud service" is broad and overlaps with narrower, framework-specific skills.