The body is lean and rule-based with zero padding and no explanation of concepts Claude already knows; every line states a concrete rule. Not score 2 because there is no unnecessary explanation to tighten.

Gives concrete, specific guidance with real paths and package mappings ('internal/cloud/dashboard/*.templ', 'store/cloudstore', 'New route -> handler + tests in dashboard/server package'). Not score 2 because the mappings are complete and copy-applicable, not pseudocode.

A simple single-purpose skill under 50 lines with clear, well-organized sections and an unambiguous input->location mapping; per the rubric's simple_skills note this qualifies for 3 without a multi-step workflow. Not score 2 because there are no unclear steps or validation gaps needing checkpoints.

Under 50 lines with no external references needed and four well-organized sections (When to Use, Placement Rules, File Creation Rules, Anti-Patterns); per the rubric this scores 3 on organization alone. Not score 2 because content is appropriately sectioned rather than a monolithic wall.

Names the domain ('Repository structure and placement rules for Engram') and enumerates multiple concrete creation types ('files, packages, handlers, templates, styles, or tests'), well above vague single-verb descriptions. Not score 2 because it lists several specific concrete items rather than 'some actions'.

Explicitly states what ('structure and placement rules for Engram') and when (an explicit 'Trigger:' clause equivalent to 'Use when'), satisfying both halves. Not capped at 2 because equivalent explicit trigger guidance is present.

The explicit 'Trigger:' clause lists natural terms a contributor would say (files, packages, handlers, templates, styles, tests, repo), giving good coverage. Not score 2 because common variations across creation scenarios are present rather than a single keyword.

Scoped to the Engram repo with a clear niche (project structure/placement) and repo-specific triggers, making conflict with unrelated skills unlikely. Not score 2 because it is not merely 'somewhat specific' but tied to a named repository.