Conciseness

The body is lean and instructive throughout — a task line, an argument substitution, executable find commands, terse section directives, and a data-flow one-liner — with zero explanation of concepts Claude already knows, matching the "every token earns its place" anchor.

Actionability

The `find` commands are copy-paste ready and directives like "List pages and their routes (1 line each)" are concrete, but "grep in services" lacks the actual grep command and "the ARCHITECTURE.md pattern" is invoked without a path or link — minor gaps that fit the "mostly executable" anchor rather than the fully copy-paste-ready one at 5.

Workflow Clarity

The three-step sequence (map structure → summarize by section → output a 2-minute-readable summary) is clearly ordered and read-only, so no validation cap applies; it stays at 4 rather than 5 because checkpoints are implicit — there is no instruction for handling a missing module directory or how to verify the endpoint grep found everything.

Progressive Disclosure

The body is under 50 lines, well organized into a single flow with no inlined bulk that belongs in a separate file; no bundle references exist (no references/, scripts/, or assets/ directories), so per the simple-skill guideline well-organized sections alone merit a 5.

Specificity

"a quick summary of its structure, patterns, and key files" names the domain and deliverable facets, but the only action offered is a generic "summary" and "patterns" is vague — matching the anchor for 1-2 concrete actions without comprehensive coverage, not the several-specific-actions anchor at 4.

Completeness

Both parts are present: the "what" is "a quick summary of its structure, patterns, and key files" and the "when" is the explicit "Use when onboarding onto a module". It falls short of 5 because the "what" is a single general action rather than concrete capabilities paired with trigger phrases.

Trigger Term Quality

Terms like "onboarding", "module", and "quick summary" are somewhat natural, but the description misses common variations and synonyms a user might say (e.g., "ramp up", "get familiar with", "walkthrough"), matching the "some relevant keywords but missing variations" anchor rather than the good-coverage anchor at 4.

Distinctiveness Conflict Risk

"onboarding onto a module" carves out a fairly specific scenario with minimal conflict risk, though the generic word "module" (no stack context in the description) leaves minor overlap risk with general code-exploration skills, keeping it below the clear-niche anchor at 5.