Playbooks
Build repeatable workflows and run or schedule them reliably
Playbooks turn successful one-off execution into repeatable workflows. Use them when you want consistency across operators, bots, and time.
What a playbook should contain
A strong playbook includes:
- Clear intent and trigger conditions
- Required inputs
- Ordered execution steps
- Guardrails and approval expectations
- Success criteria
- Optional model/workspace context
Creation paths
You can create playbooks from:
- Built-in catalog starters
- Custom authoring
- Teach-mode sessions (chat-to-playbook)
Guidance:
- Start from a proven real run
- Extract repeatable logic, not incidental details
Run modes
Playbooks can run in current or new chat flows (depending on context), and can also be scheduled.
Recommended rollout:
- Manual run with small scope
- Validate output quality and approval behavior
- Expand scope or schedule after reliability is proven
Auto Refine
Auto Refine captures improvement candidates from real executions and lets you apply changes intentionally.
Best practice:
- Batch review refine suggestions regularly
- Accept only changes that improve determinism and clarity
Playbooks and Skills
Claw supports conversion in both directions:
- Playbook -> Skill
- Skill -> Playbook
Use conversion when you want to move from conversational flow to reusable packaged behavior.
Common failure patterns
- Steps too broad or ambiguous
- Missing success criteria
- Unclear approval boundaries
- Overfitting to one dataset/project