Build from a template

The fastest way to a working Playbook is to copy one that already works. Every template in the Playbook Library publishes what it produces, what it needs and a real example of its output, so you can judge the work before it is in your account.

What copying gives you

Open a template and choose to use it. The whole definition copies into your account: the Playbook document, its ordered steps, its input contract, and a file for every reference it declares.

It is yours from that point. Your copy, your edits, and no live link back to the original: a later change to the template does not reach into what you already have.

What it asks you to replace

A template ships placeholders for the knowledge it cannot know. URL SEO Audit declares one reference, target-keywords.md, and copying it puts a file of that name in your draft with worked example content in it, so "replace this" comes with a picture of what good looks like rather than an empty box.

The setup checklist tracks every reference still on placeholder content and clears the item when you replace it. A Playbook will still run with a placeholder in place. It just works from the example knowledge rather than yours.

Where to start

URL SEO Audit is the one to try first, because it declares no Connectors. It runs on a brand new account with nothing authorised, so you can go from a copy to a finished piece of work without setting anything up first.

What copying is not

Copying a template is not subscribing to a Service. A template transfers an editable copy of the method to you. Running somebody's published Service does not: you get your own working context against their Service, and their Playbook stays theirs.

Once it is copied, the next steps are the same as for anything else you build: the steps, then Deploy.