Getting started
From a template to your first run: copy, customise, run.
YAMO runs Playbooks. A Playbook is how you do your best work, written down: a readable document plus the tools and reference files that do the job. This page takes you from a template to your first finished output.
A Playbook is the first stage of a Service, not a separate thing you own alongside one. The moment you start building, you have a Draft Service: it is yours, it has a name, and nobody can run it yet. Deploy is what makes it runnable. Publish is what makes it public.
The walkthrough below uses the URL SEO Audit template because it needs no Connectors: it runs on a brand-new account. Every template works the same way.
1. Copy a template
Sign in, open Services, then choose Create new Service. The creation page gives Create from scratch and Start from a template equal status. Each template shows its Outcome, the Connectors it needs, and an example Outcome, so you can judge the work before you copy anything.
Open URL SEO Audit and choose Use this template. The template copies into your account as a Draft Service. It's yours from that point: your copy, your edits, no live link back to the original.
2. Make it yours
Your Draft Service opens in the builder, where its Playbook lives: YAMO's chat on the left, the document as tabs in the middle (Playbook, Plays, Resources), and a preview of what a subscriber would see on the right. Two things help you finish the setup:
- The guided chat. A template draft opens with YAMO offering to walk the setup checklist with you: references still on placeholder content, Connectors not yet connected, config inputs not yet set. One item at a time, and each item names where to fix it. You can ignore it and edit directly; the document is always the interface.
- The Resources tab. The same state at a glance: every reference file and Connector the Playbook declares, with anything missing marked. The header also counts Connectors still to connect.
For URL SEO Audit the checklist shows one pending item: replace the
placeholder in target-keywords.md. The template ships that file as a
placeholder showing what good looks like: replace the example keywords with
the ones your page should rank for, and the item clears. If you skip this,
the audit still runs; it's just not aimed at your keywords yet.
3. Deploy, then run the private Service
Choose Deploy when the Playbook is ready. Deploy turns your Draft Service into a private one you can run; it does not publish anything publicly. Open that Service, create an Instance for the work, and choose Run Service. The conversation asks for the required run inputs one at a time. For this example, enter the full URL of the page to audit and confirm the Run.
Runs execute in the background, so you can close the tab. The Instance stays usable while the Run works, and the output appears in its work rail as it arrives. You are also notified when the Run finishes or needs attention.
The finished audit lands as the run's deliverable. Behind every output is the run folder: the inputs you gave, each stage's work in sequence, and an itemised receipt. What you see is what ran.