You just walked an agent through a job and it went right: the monthly link check, a menu cleanup, a sale set up the way you like it. Next month you would have to explain it all again.
A playbook is where that explanation lives. The draft comes from what the Activity Log shows the agent actually called, so a step that was refused or failed shows up before it gets written into the playbook as if it worked.
That job went well and I want to save it as a playbook. Do not changeanything on the site.
1. Read this plugin's Activity Log newest first, 200 per page, until you pass the start of the job, about [45 minutes] ago. Log times are UTC. Keep only rows where the user login is [agent-editor], and list the tools that ran, in order, with their outcomes.2. List the Active playbooks and tell me if one already covers this job. If so, suggest changes to that one instead of a new one.3. Write the playbook in this format: - Title: 80 characters or fewer. - Description: 200 characters or fewer, saying whether it changes anything. - Steps: numbered, one action per step, naming each tool by its label (for example "the Get posts tool"). Include the checks we did, when to stop, and the report format I asked for. Add a Rules section saying what the agent must never do. Keep it well under 8,000 characters.4. List the tools I should tick for it in the playbook's ability picker.5. Leave out any password, key, private address or customer detail.
Give me the title, description and steps as three separate plain textblocks so I can paste each one into its box.Why this is safe to run
No tool can save a playbook, so what comes back is text for you to review. It reaches your agents only after you paste it into the Playbooks tab and set it to Active, and new playbooks start Off.
Read the steps before you save them. Every agent that loads the playbook later follows your wording, so a vague step now becomes a vague job every month.
Already connected from an admin account? Ask your agent to write up the job you just finished as a playbook draft, and it uses the same log read.