| name | write-template-playbooks |
| description | Write a template playbook for the build-an-agent skill: a 1-2 KB per-use-case file that teaches the builder agent to configure one kind of Agenta agent (changelog writer, issue triager, support router, and so on). Use when the ask is "write a template playbook", "add an agent template", "author a playbook for the build-an-agent skill", or "write the <X> playbook". Encodes the file format, the prompting checklist, and the platform facts authors get wrong. |
| allowed-tools | Read, Edit, Write, Grep, Glob, Bash |
| user-invocable | true |
Write a template playbook
A playbook is one markdown file under references/agent-templates/<key>.md in the
build-an-agent skill. The builder agent reads the one that matches the user's ask, then follows
it to configure that specific agent. Your job: encode the use-case thinking so a Sonnet-class
model can execute it. You get one inventory row as input (name, one-line pitch, integrations,
trigger). Turn it into a spec-conforming playbook.
Keep each playbook 1 to 2 KB. An over-comprehensive playbook hurts: the agent cannot
extract what is relevant. Write a coherent, moderately detailed unit with a working
instructions template.
The skeleton
Fill this in. Omit any section the use case does not need (a no-tool template drops Explore and
Connections; a no-trigger template drops the trigger half of Verify).
# < > playbook
One line: when this playbook applies. The card key plus the shape of the ask, including
free-text asks that match no card.
One testconnection and stop. List the
tool-agnostic alternatives (Notion OR Confluence OR Google Drive).
The numbered per-run procedure for instructions.agentsrun with a blunt test message; read the verdict and the tools line, not a 200.
If a trigger: fire an artificial test message first; then ask the user to run the real
trigger test (Lightning "Test event" for a subscription, Play "Run" for a schedule).
What the agent became, what is connected, what is scheduled, what you verified, what still
needs the user.
