Skills

At a glance

Skills registers 4 abilities: 1 that only read, 1 that write, and 2 marked destructive. That split is the practical answer to how much of this module can run unattended. Reads cost nothing and are safe to repeat, so discovery is the part to be generous with; the writes are where review belongs, and the destructive calls stop for an explicit confirmation every single time regardless of which profile is active.

What this module is for

WPPilot exposes reusable skill packs and their source so an AI client can load focused WordPress or integration guidance only when it is relevant.

Before you rely on it: Skills provide workflow context; live schemas, permissions, and the active site state still determine what is safe and possible.

Typical workflows

• Load a builder-specific skill before planning an edit
• Combine site instructions with an integration workflow
• Keep the initial MCP tool surface compact by retrieving guidance on demand

The WPPilot Skills integration page covers the same module from the workflow side, with the capability map and the questions worth asking before a first write.

Availability on your site

The Skills module ships in WPPilot Free, so it registers on every install where the plugin is active. No licence check and no dependency detection stand between the agent and these 4 abilities. What the connected agent can actually call is then narrowed twice more: by the safety profile active on the site, and by the WordPress capabilities of the user behind the credential. A read that succeeds for an administrator can be absent entirely for an editor.

Every write these abilities perform is recorded in the change ledger, and destructive calls can be routed through the approval queue so a person signs off before anything is applied. A successful tool result means the operation returned, not that the front end, the cache, and every dependent template are correct: that still needs a look.