The body is lean and pointer-driven with no padding or explanation of concepts Claude already knows; the domain-vs-projection framing is a genuinely non-obvious domain insight that earns its tokens, matching the lean-and-efficient anchor.

Provides concrete search strings, meta keys, hook names, and diagnostic checks, but the core registration code (the actual wp_register_ability() call) is delegated to reference files rather than shown inline, leaving key executable detail out of the main body.

A clearly sequenced 6-step procedure pairs with an explicit Verification section (concrete success criteria like 'signals.usesAbilitiesApi: true') and a Failure modes section that supplies debug feedback loops, matching the clear-sequence-with-validation anchor.

The body is an overview that splits detailed material across 9 reference files, each signaled inline with its purpose and verified to exist; references are one level deep with no nested redirection, matching the well-signaled one-level-deep anchor.

Lists multiple concrete actions — 'defining abilities, categories, meta, REST exposure, and permissions checks' — matching the anchor for multiple specific concrete actions rather than the partial single-domain anchor at 2.

Explicitly answers both what ('defining abilities, categories, meta, REST exposure, and permissions checks') and when ('Use when working with the WordPress Abilities API...'), matching the both-what-and-when anchor; not capped at 2 since an explicit trigger clause is present.

Covers natural terms users/developers would say — 'WordPress Abilities API', 'wp_register_ability', 'wp_register_ability_category', '/wp-json/wp-abilities/v1/*', '@wordpress/abilities' — giving broad coverage rather than only some relevant keywords.

A highly specific API with named functions, REST namespace, and npm package gives it a clear niche unlikely to trigger for unrelated skills, matching the distinct-triggers anchor.