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).

# <Template name> playbook