Chatbot Flow Design — intent architecture, grounding, fallbacks and human escalation
A senior growth practitioner's playbook for designing conversational flows: intent architecture, knowledge-base grounding, branching, multi-layer fallbacks, escalation discipline, analytics — structured-guided-conversation over scripted or hallucinating bots
- What
- A senior growth practitioner's playbook for designing conversational flows: intent architecture, knowledge-base grounding, branching, multi-layer fallbacks, escalation discipline, analytics — structured-guided-conversation over scripted or hallucinating bots
- Cost
- Free
- Needs
- a chatbot project to scope, design or audit — the skill is a design playbook the agent follows, not software
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Curated by Skill Harbor — @rampstackco's chatbot-flow-design: a senior growth practitioner's playbook for designing conversational flows for website chatbots and AI agents — intent recognition architecture, branching logic, fallback handling, escalation to human, conversation analytics. The keystone framing: scripted-bots (rigid trees that fail edge cases) vs hallucinating-bots (LLM without structure that makes things up) vs structured-guided-conversation (LLM-powered with intent architecture, knowledge-base grounding and fallback discipline — the goal). Covers the chatbot decision (when a bot earns deployment and when it doesn't), intent design patterns and coverage targets (70–90%), RAG-style grounding and citation discipline, multi-layered fallbacks (clarify → suggest → resource handoff → human escalation), escalation triggers with clean context handoff, per-intent analytics, common failure modes, and a 12-point design framework. Honest caveats: explicitly design-only — it distinguishes chatbot DESIGN (this skill) from chatbot IMPLEMENTATION (engineering work handed off via specs); it references sibling skills in its series (ai-content-collaboration, integration-orchestrator, pm-spec-writing) and bundled references/ files that ship with the repo. The skill's frontmatter states no license; the catalog manifest records MIT — manifest takes precedence. MIT licensed per the manifest. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: a chatbot project to scope, design or audit — the skill is a design playbook the agent follows, not software Install "Chatbot Flow Design — intent architecture, grounding, fallbacks and human escalation" for me. It gives my agent @rampstackco's conversational design playbook: decide whether a chatbot earns deployment, apply the scripted-vs-hallucinating-vs-structured-guided-conversation framing, design the intent architecture (named intents, hierarchies, boundaries, 70-90% coverage), ground responses in a knowledge base (RAG patterns, citation discipline), build multi-layer fallbacks (clarifying question, suggested intents, resource handoff, human escalation), define escalation triggers with clean context handoff, and instrument per-intent analytics. Design only — implementation is out of scope. License note: the skill's frontmatter states no license; the catalog manifest records MIT — manifest takes precedence. Repository: https://github.com/rampstackco/claude-skills/blob/main/dist/codex/.agents/skills/chatbot-flow-design/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "chatbot-flow-design". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. describe the chatbot to scope or the failing bot to audit; nothing else — it's a design playbook). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.