← ClaudeAtlas

playbook-builderlisted

Use whenever building, reviewing, fixing, or extending a SuperDialog voice-agent playbook YAML (the persona/llm/journeys/checkpoints/interrupts/policies/knowledge_base schema consumed by super/core/voice/livekit/lite_v2's PlaybookAgent/DialogMachine). Trigger on requests like "make a playbook for this agent", "build a YAML for [business] voice agent", "why is my agent hanging up / mixing up prices / answering the wrong program", "the caller's off-script question broke the flow", or any review of an existing playbook YAML — even if the user doesn't say "SuperDialog" or "playbook" by name, just describes a voice agent's booking/FAQ/pricing/routing behavior going wrong. Also trigger when asked to convert a raw client prompt/spec (a .txt persona doc) into this YAML format.
ankitai-s/superdialog-playbook-skill · ★ 2 · AI & Automation · score 70
Install: claude install-skill ankitai-s/superdialog-playbook-skill
# Building a SuperDialog Playbook A playbook is a Director+Talker voice-agent script: the **Director** (usually a fast/cheap LLM) reads the transcript each turn and decides whether to advance to a new checkpoint or fire an interrupt; the **Talker** (usually a stronger LLM) speaks based on whatever checkpoint the Director landed on. Almost every hard bug in a playbook traces back to one specific thing being left to Director/Talker *judgment* when it should have been made *structural* — a real slot, a real `judge: expr` rule, or a real code-side guard. This skill exists because that lesson kept getting relearned the hard way across three real playbooks (a golf-booking agent, a real-estate agent, a meditation-retreat agent) before it got written down here. ## Before writing anything: read the real schema Don't guess field names. Read `references/schema.md` — it's the actual `superdialog.playbook.models` Pydantic schema (persona, llm, journeys, checkpoints, slots, advance_when, interrupts, policies, knowledge_base), not a remembered approximation. Every field there was confirmed against the installed library, not assumed from a prior example. ## Workflow 1. **Source hygiene check, before anything else.** If you're compiling from a client-provided prompt/spec, skim the whole thing first for content that doesn't belong — a copy-pasted section from a *different* client's script is a real, recurring failure mode (a real-estate "off-topic termination" block once ended