Conciseness

The body is a lean lookup table: every line carries semantics (exact names, node legality, constructor aliases like FDescribe/PDescribe/XIt, CLI overrides like --flake-attempts, constraints like 'No &|!,()/" chars'). It assumes Ginkgo knowledge and explains nothing Claude already knows, matching the anchor 'every token earns its place'.

Actionability

For an instruction-only reference skill, the guidance is fully actionable: an inline usage example (It("...", Serial, Label("slow"), func(){...})), exact decorator signatures (FlakeAttempts(n), SpecPriority(int), AroundNode's three forms), and per-item semantics. Per the rubric's scoring note, absence of code is not penalized when the guidance is this concrete.

Workflow Clarity

Single-purpose lookup skill with an unambiguous use pattern ('Terse lookup' up top, items grouped by purpose), so the simple-skill exception applies. No destructive or batch operations exist, so no validation checkpoints are required.

Progressive Disclosure

The body is under 50 lines with no need for external reference files (none exist in the bundle), and is well-organized into clear sections by category, with a single one-level-deep pointer to the official docs — the rubric's under-50-lines guideline for a score of 5 is satisfied.

Specificity

The description gives a concrete what ('One-line reference for every Ginkgo decorator, grouped by what it does, with the node types each can decorate') plus a concrete action ('Use to look up a decorator's exact name, semantics, and where it's legal'), and enumerates the full decorator inventory. It sits between anchor 3 (1-2 concrete actions) and anchor 5 (multiple actions, comprehensive) — the single lookup action is thorough but it is one action, not several.

Completeness

Both what and when are explicitly and concretely answered: the what ('One-line reference for every Ginkgo decorator... with the node types each can decorate') and an explicit trigger clause ('Use to look up a decorator's exact name, semantics, and where it's legal').

Trigger Term Quality

'Ginkgo decorator' plus every decorator name (Serial, Ordered, Label, Focus, Pending, FlakeAttempts, NodeTimeout...) gives strong keyword coverage — these are exactly the tokens a user would type. A few natural phrasings users actually say ('retry flaky tests', 'run specs in order', 'parallel') are absent, so it is not comprehensive coverage of synonyms.

Distinctiveness Conflict Risk

Clear niche — Ginkgo test framework decorators — with distinct, framework-specific trigger vocabulary (decorator names, 'Ginkgo'), so it is unlikely to fire for the wrong skill.