Use when working with the WordPress Abilities API (wp_register_ability, wp_register_ability_category, /wp-json/wp-abilities/v1/*, @wordpress/abilities) including defining abilities, categories, meta, REST exposure, and permissions checks for clients.
Use this skill when the task involves:
wp-abilities/v1),@wordpress/abilities),wp-project-triage first if you haven’t).signals.isWpCoreCheckout and versions.wordpress.core.Search for these in the repo:
wp_register_ability(wp_register_ability_category(wp_abilities_api_initwp_abilities_api_categories_initwp-abilities/v1@wordpress/abilitiesIf none exist, decide whether you’re introducing Abilities API fresh (new registrations + client consumption) or only consuming.
If you need a logical grouping, register an ability category early (see references/php-registration.md).
Implement the ability in PHP registration with:
id (namespaced),label/description,category,meta:
readonly: true when the ability is informational,show_in_rest: true for abilities you want visible to clients.Use the documented init hooks for Abilities API registration so they load at the right time (see references/php-registration.md).
references/rest-api.md).meta.show_in_rest is enabled and you’re querying the right endpoint.@wordpress/abilities APIs for client-side access and checks.wp-project-triage indicates signals.usesAbilitiesApi: true after your change (if applicable).wp-abilities/v1 return your ability and category when expected.meta.show_in_rest,references/rest-api.mdreferences/php-registration.md