wp-abilities-api
/wp-abilities-api
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.
- Author
- pleaseai ↗
- Repository
- claude-code-plugins ↗
- Licence
- MIT
- Last repository change
- 27.10.2026
Assessment and security
- Files in this package
- 10
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 0
No signals detected. Repository changed on 27.10.2026, without references to retired models or APIs.
MIT, open: use and modify while retaining author attribution.
What it does and when to use it
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.
Original author description
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.
How it works
- When to use
- Inputs required
- Procedure
- Verification
- Failure modes / debugging
- Escalation
SKILL.md preview
--- name: wp-abilities-api description: 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. compatibility: Targets WordPress 7.0+ (PHP 7.4.0+). Filesystem-based agent with bash + node. Some workflows require WP-CLI. --- # WP Abilities API ## When to use Use this skill when the task involves: - registering abilities or ability categories in PHP, - exposing abilities to clients via REST (`wp-abilities/v1`), - consuming abilities in JS (notably `@wordpress/abilities`), - diagnosing “ability doesn’t show up” / “client can’t see ability” / “REST returns empty”. ## Inputs required - Repo root (run `wp-project-triage` first if you haven’t). - Target WordPress version(s) and whether this is WP core or a plugin/theme. - Where the change should live (plugin vs theme vs mu-plugin). ## Procedure Before deciding what to register, read `references/domain-vs-projection.md` — abilities live at the domain capability layer; MCP / Command Palette / REST exposure is a projection. Registration shape and exposure shape are different decisions, and conflating them forces re-registration every time a consumer's constraints change. ### 1) Confirm availability and version constraints - If this is WP core work, check `signals.isWpCoreCheckout` and `versions.wordpress.core`. - If the project targets WP < 6.9, you may need the Abilities API plugin/package rather than relying on core. ### 2) Find existing Abilities usage Search for these in the repo: - `wp_register_ability(` - `wp_register_ability_category(` - `wp_abilities_api_init` - `wp_abilities_api_categories_init` - `wp-abilities/v1` - `@wordpress/abilities` If none exist, decide whether you’re introducing Abilities API fresh (new registrations + client consumption) or only consuming. ### 3) Register categories (optional) If you need a logical grouping, register an ability category early (see `references/php-registration.md`). ### 4) Register abilities (PHP) For grouping decisions (how many abilities to register, and where to put filters vs. new ability names), read `references/grouping-heuristic.md` first — it keeps you from shipping one atomic ability per REST operation. To avoid drift between the ability and the existing UI / REST code path, see `references/shared-core-service.md` — abilities, REST handlers, CLI commands, and UI controllers should be thin adapters over a shared service. The reference also covers the metric trap (REST handlers that emit usage telemetry) and the `AGENTS.md` rule for keeping registrations in sync when underlying code paths change. For shared helper patterns when multiple execute callbacks delegate to existing REST controllers, see `references/plugin-family-patterns.md` (identify the shared-API-client vs zero-arg-controllers shape) and `references/delegate-helper-pattern.md` (one helper shape that works, and when not to use it). For standardized `WP_Error` codes that let agents reason about retry vs. escalation, see `references/error-code-vocabulary.md`. Implement the ability in PHP registration with: - stable `id` (namespaced), - `label`/`description`, - `category`, - `meta`: - add `readonly: true` when the ability is informational, - set `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`). ### 5) Confirm REST exposure - Verify the REST endpoints exist and return expected results (see `references/rest-api.md`). - If the client still can’t see the ability, confirm `meta.show_in_rest` is enabled and you’re querying the right endpoint. ### 6) Consume from JS (if needed) - Prefer `@wordpress/abilities` APIs for client-side access and checks. - Ensure build tooling includes the dependency and the project’s build pipeline bundles it. ## Verification - `wp-project-triage` indicates `signals.usesAbilitiesApi: true` after your change (if applicable). - REST check (in a WP environment): endpoints under `wp-abilities/v1` return your ability and category when expected. - If the repo has tests, add/update coverage near: - PHP: ability registration and meta exposure - JS: ability consumption and UI gating ## Failure modes / debugging - Ability never appears: - registration code not running (wrong hook / file not loaded), - missing `meta.show_in_rest`, - incorrect category/ID mismatch. - REST shows ability but JS doesn’t: - wrong REST base/namespace, - JS dependency not bundled, - caching (object/page caches) masking changes. - Execute callback returns unexpected errors or silently ignores input: - `input_schema` defaults aren't being applied, pagination key drift between the ability and the backing, or `empty()`-based ID validation — see `references/input-schema-gotchas.md`. ## Escalation - If you’re uncertain about version support, confirm target WP core versions and whether Abilities API is expected from core or as a plugin. - For canonical details, consult: - `references/rest-api.md` - `references/php-registration.md`
Files in this package (10)
- SKILL.md 5 KB
- references/delegate-helper-pattern.md 12 KB
- references/domain-vs-projection.md 9 KB
- references/error-code-vocabulary.md 7 KB
- references/grouping-heuristic.md 8 KB
- references/input-schema-gotchas.md 13 KB
- references/php-registration.md 6 KB
- references/plugin-family-patterns.md 12 KB
- references/rest-api.md 1 KB
- references/shared-core-service.md 15 KB
Versions
| Repository | Score | Licence |
|---|---|---|
| This page · pleaseai/claude-code-plugins | 90 | MIT |
| Lonsdale201/wp-agent-skills | 100 | MIT |
Identical content appears in 1 other GitHub folders. We show one copy with the highest score.
Database snapshot: 13.11.2026 · package version d583fdbe7456 (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100lw-seo-automation-compatibility
Automate or review LW SEO 1.7.x through WP-CLI, public REST, WordPress Abilities, and LW Site Manager MCP, and verify compatibility with LW Cookie 1.8.x and headless LW LMS 2.0.x. Use when calling `wp lw-seo`, `lw-seo/*` abilities, `/wp-json/lw-seo/v1`, Site Manager discovery,… - 100lw-site-manager-extend-abilities
Add companion-plugin abilities to LW Site Manager 1.5.x through lw_site_manager_register_categories and lw_site_manager_register_abilities. Covers namespaces, REST and MCP exposure metadata, PermissionManager, object-level authorization, schemas, annotations, WP_Error failure… - 90wordpress-rest-api
Use when talking to a WordPress site over REST: read or write posts, pages, media, users, taxonomy, settings. - 100wordpress
WordPress framework guardrails, patterns, and best practices for AI-assisted development. Use when working with WordPress projects, or when the user mentions WordPress. Provides theme development, plugin architecture, REST API, blocks, and security guidelines. - 90wordpress-wp-rest-api
Use when building, extending, or debugging WordPress REST API endpoints/routes: register_rest_route, WP_REST_Controller/controller classes, schema/argument validation, permission_callback/authentication, response shaping, register_rest_field/register_meta, or exposing… - 90wordpress-wpforms-ops
Use when managing WPForms on a WordPress site: list forms, read entries, pull form statistics, and (with write access) create forms and update fields via the REST API.