RepoAI
Browse MCPs

WP Abilities API

94TrustedInstructions only

WordPress capability definitions, REST exposure, and client-side access control management.

What it does

Wp Abilities API integrates the structure of WordPress ability registration into your assistant's workflow. By clarifying the relationship between domain capabilities and their REST projections, this skill ensures that new features are properly surfaced to clients without creating drift between PHP registration and JavaScript consumption. It helps maintain consistent state when defining categories and meta-attributes for system permissions.

Installing this skill gives your assistant the logic to distinguish between backend capability requirements and frontend display needs. It provides a structured approach for checking the availability of abilities, configuring metadata for REST visibility, and implementing the necessary hooks for correct registration timing.

When it earns its place

Reach for it when…

Use this skill when developing custom WordPress plugins or themes that need to expose granular actions to client-side interfaces or external services via the REST API, specifically when handling ability registration, categorization, and client-side capability verification.

Look elsewhere when…

Do not use this for managing standard WordPress user roles or core capabilities that rely solely on the legacy user-permission system, as this skill is specialized for the modern Abilities API framework. It is unnecessary for simple sites that do not require structured client-side ability discovery or complex permission mapping.

What to say to use it

You never invoke a skill directly — the assistant picks it up when your request matches what it covers. These are the kinds of things that do that.

  • register a new ability category for the dashboard
  • how do I make this custom capability visible in the REST API
  • check why the client cannot see the abilities list
  • update the ability registration for the new plugin feature

Install it

Install for all your projects

Copy the skill directory into your personal skills folder. Claude picks it up on its own the next time your request matches what it does — there is nothing to enable.

bash
git clone --depth 1 --branch trunk https://github.com/WordPress/agent-skills.git /tmp/agent-skills
mkdir -p ~/.claude/skills
cp -r /tmp/agent-skills/skills/wp-abilities-api ~/.claude/skills/wp-abilities-api

Install for one project only

Put it in the project's own skills folder instead, so it can be committed and shared with everyone working on that repository.

bash
cp -r /tmp/agent-skills/skills/wp-abilities-api .claude/skills/wp-abilities-api

If a skill of the same name exists in both places, the personal one wins.

Installing on Claude.ai or through the API instead? The full guide covers every surface.

Pair it with an MCP server

WP Abilities API changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →