# Playbooks · WordPress AI workflows that crystallize into tools

> Playbooks are typed JSON workflow compositions for WordPress AI agents. Each Playbook registers as a WordPress Ability and becomes a callable MCP tool. The agent authors once, runs many times.

Source: https://www.respira.press/playbooks

---

v7.1 · WordPress Playbooks · **1** public 

# Respira WordPress Playbooks 

The agent authors a workflow once.Future runs are one tool call. 

A Playbook is a JSON composition that registers itself as a WordPress Ability and shows up in the MCP tool catalog. The agent describes the workflow, Respira stores it, and future invocations are a single typed call instead of an instruction-by-instruction agent run. Production-safe by construction: destructive operations are refused at create-time, every step runs through Respira’s existing audit and snapshot belt. 

[See how it works](#how) [Read the docs](https://www.respira.press/docs/playbooks) 

[ The Respira playbook atlas · 1 public playbooks ![An architect's drafting table seen from above: an open atlas of luminous emerald-and-cream blueprints showing workflow diagrams, neat stacks of leather-bound volumes labeled 'create case study', 'audit accessibility', 'duplicate page', and a brass draftsman's compass at rest.](https://www.respira.press/hero/playbooks-hero-2048.jpg) ](#directory) 

**1** public playbooks · agent-authored **One** tool call per invocation · **\~200** bytes of agent context · **22** destructive ops refused at create-time · [Read the spec ↓](#how) 

## Three nouns. One agent. Zero PHP.

Respira’s v7.1 surface stacks cleanly. Pick the right tool by what the agent is doing, not by which file lives where. 

Skills

### The agent reads.

Markdown documentation the agent loads into context. 55 skills today (case study workflows, migrations, audits). Distributed via the agent- skills-wordpress repo; installed via `npx @respira/wordpress-mcp-server install-skills`. 

[Browse skills →](https://www.respira.press/skills) 

Playbooks

### The agent runs.

JSON workflow compositions the agent authors at runtime. Each registers as a WordPress Ability and becomes a callable MCP tool. One tool call, one typed result, \~200 bytes of agent context per invocation. 

[See the directory ↓](#directory) 

Abilities

### The WordPress primitives.

The wp\_register\_ability core API. Any plugin can expose abilities; Respira absorbs them through [Inhale](https://www.respira.press/inhale-mcp-abilities). The universal plug under everything — Playbooks themselves are abilities. 

[Browse abilities →](https://www.respira.press/abilities) 

## Production-safe by construction.

### Other AI integrations

Give the agent `execute_php` \+ filesystem write. The agent generates a PHP file, drops it in `wp-content/plugins/`, WordPress loads it on the next request. Powerful. No sandbox, no approval gate, no audit trail. Vendor footers admit it: “for development and staging environments only.” 

### Respira Playbooks

The agent crystallizes the workflow into a typed JSON composition. Respira stores it, registers it as a WordPress Ability, executes each step through the existing duplicate-before-edit + audit-log + snapshot belt. Destructive tools are refused at create-time — split the flow. Production-safe. Auditable. Reversible to the snapshot point, within the documented recovery limits. Customer can delete any Playbook anytime from wp-admin. 

## Public directory

Playbooks customers opted in to publish. Browse them, read the source (Playbooks are pure JSON), copy them to your own site via export/import. Last refreshed: 6/13/2026\. 

| Playbook | Description | Site | Used |
| --- | --- | --- | --- |
| | Build multiple pages from a template pattern with variable substitution. Define a pattern in the WordPress Pattern Library with {{VARIABLE}} placeholders, provide a data source (markdown, XML, or a list), and this Playbook instructs the agent to create one page per row — replacing each variable before injecting into the builder. | — | 0 |

## Teach your agent

Have a Respira-connected agent (Claude Code, Cursor, Codex, Windsurf, any MCP client). Paste this into the chat. The agent will use the Build-a- Playbook skill if installed, or fetch its source from the agent-skills repo if not. 

Use the build-a-playbook Respira skill on this site.

I want to crystallize this workflow into a reusable tool so future runs are one call:

[describe the workflow in plain English]

After you've designed the input schema and steps, confirm the playbook id and
label with me before calling respira_create_playbook. I want to review the JSON
before it lands.

After the agent confirms, the new Playbook lands in your site’s wp-admin under Respira → Playbooks and shows up in the MCP tool catalog on the next handshake as `respira-playbooks/<id>`.