RepoAI
Browse MCPs

WP Abilities Audit

94TrustedInstructions only

Standardized REST API audit reports for WordPress plugin capability planning.

What it does

Wp Abilities Audit transforms your assistant into a technical researcher capable of surveying a WordPress plugin's REST surface. It identifies existing controllers, maps permission gates, and drafts a structured document that organizes functionality by semantic intent rather than simple HTTP routes.

This artifact provides a blueprint for planning an Abilities API implementation. By consolidating class locations, capability checks, and proposed registration schemas into one reference, it helps developers and stakeholders evaluate the agent-readiness of a codebase before starting any integration work.

When it earns its place

Reach for it when…

Apply this when preparing a WordPress plugin for an Abilities API rollout or when a technical lead requires a formal scope-of-work document for a REST-based feature set.

Look elsewhere when…

Do not attempt this for projects lacking a REST API component or for plugins that rely entirely on custom non-REST hooks, as the tool relies on identifying standard controller classes and permission callbacks.

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.

  • Audit this plugin to see if it supports the Abilities API
  • Create a plan for mapping our REST routes to new abilities
  • Examine the REST controllers in this folder and propose an ability structure
  • Draft an audit document for the plugin REST API

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-audit ~/.claude/skills/wp-abilities-audit

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-audit .claude/skills/wp-abilities-audit

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 Audit changes how the work is done. These servers change what Claude can reach while doing it.

How skills and MCP servers differ →