Playbooks

Version 1.10.1 added playbooks: step-by-step instructions you write for agents, such as how to check a draft before it goes live or how to build a weekly report. You write them on the Playbooks tab, next to Abilities. Agents read them through two tools, and no agent can change one.

Tool	Kind	What it does
List playbooks (aafm/list-playbooks)	Read	Lists your Active playbooks
Get playbook (aafm/get-playbook)	Read	Loads one Active playbook by slug, with its steps

Both are off until you turn them on in the Site section of the Abilities tab, and Quick Connect never turns them on. Copyable playbooks, including the five starters, are on the playbook library.

Writing a playbook

The Playbooks tab has three cards: Your playbooks, Starter playbooks and Write a playbook. A playbook has:

• Title, up to 80 characters.
• Description, optional, up to 200 characters. This is the one line agents see in the list.
• Steps, plain text up to 8,000 characters. Agents read them word for word, so keep passwords and private details out.
• Abilities it uses, ticked in a picker. Agents get this list with the playbook, so the steps can name tools in plain words.
• Active. Only Active playbooks reach agents.

A site can hold up to 50 playbooks. Select Save playbook to store one, or New playbook to start another.

The five starters are Publish checklist, Weekly content report, Content health check, Draft a new post and Shop tidy-up, which needs WooCommerce. Select Add to my playbooks on one and it arrives switched Off, so you can read and edit it before any agent sees it. Their exact text is on the playbook library.

What agents get

List playbooks returns each Active playbook’s slug, title, description, the abilities it uses, and which of those this connection cannot use, plus a count.

Get playbook takes a slug and returns the same fields plus the steps and, for each ability, its MCP tool name, its label and whether this connection can use it. A tool counts as unavailable when you have not enabled it, its plugin is not active, or the connection’s user or access rules do not let it see the tool.

While at least one playbook is Active and the connection can see both tools, a short index of your Active playbooks is added to the server instructions at the start of each session, so the agent knows they exist. The index is capped at 600 characters and ends with a pointer to List playbooks when there are more.

Instructions, not permissions

A playbook turns nothing on. The agent can only call the abilities you enabled, as the WordPress user it connected as, and every call is checked and written to the Activity Log as usual.

Why agents cannot edit a playbook

Playbooks are stored in one option, written only from the Playbooks tab in wp-admin. No ability, REST route or post type can reach it, so an agent can never rewrite the instructions it is given. Site administrators can edit them. If the site cannot read its playbooks, nothing is served and every save refuses, so a read error is never mistaken for an empty list and overwritten.