CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

chatbot-flow-design

Designing conversational flows for website chatbots and AI agents. Intent recognition architecture, branching logic, fallback handling, escalation to human, conversation analytics. Honest about scripted-bot (rigid trees, fail edge cases), hallucinating-bot (LLM without structure, makes things up), and structured-guided-conversation (LLM-powered with intent architecture and fallback discipline) patterns. Distinguishes chatbot DESIGN (this skill) from chatbot IMPLEMENTATION (engineering and platform work). Triggers on chatbot, conversational AI, AI agent, chat widget, intent design, conversational flow, bot escalation, LLM grounding. Also triggers when a chatbot is hallucinating, when a scripted bot is failing edge cases, or when a chatbot is being scoped for the first time.

Quality

87%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

71%Weight 40%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

A well-structured design playbook: overview-level sections with concrete thresholds, named patterns, diagnostics, and a 12-item framework, backed by nine real one-level-deep reference files. Its main weakness is token efficiency — the intro and closing restate the description and taxonomy, adding rhetorical padding without new guidance.

Suggestions

Trim the opening two paragraphs (which restate the frontmatter description almost verbatim) to a two-sentence orientation, cutting the persona paragraph ('The voice is the senior growth practitioner...') entirely.

Cut or shrink the Closing section — it restates the scripted-bot/hallucinating-bot/structured-guided taxonomy a third time; a 2-3 line restatement of the bar would preserve the takeaway at a fraction of the tokens.

Flesh out the thin framework considerations (e.g., #11 Brand voice, #12 Audience-fit) with a concrete method or example, since they currently state what good looks like without how to achieve or verify it.

DimensionReasoningScore

Conciseness

The core sections are dense and useful (e.g., 'The bot's intents should cover 70-90 percent of expected conversations... Trying to cover 100 percent often produces bloated intent sets'), but padding sits at the seams: the opening paragraphs restate the frontmatter description nearly verbatim, 'The voice is the senior growth practitioner who has watched chatbots become trusted brand surfaces...' is persona rhetoric, and the Closing section restates the scripted/hallucinating/structured taxonomy a third time. Matches the 3 anchor ('mostly efficient but includes some unnecessary explanation or could be tightened'); not 2 because the padding is confined to intro/voice/closing rather than several padded sections throughout.

3 / 5

Actionability

For an instruction-only skill, the guidance is largely actionable: concrete thresholds ('coverage targets 70-90 percent', '3-5 turns is often the practical limit', 'After 2-3 unclear exchanges, the bot escalates'), rehearsed fallback phrasings, per-intent metrics with diagnostic mappings ('High fallback rate: intents missing or unclear; expand or refine intent set'), and a litmus test ('Ask the bot a question outside its intended scope'). Not 5 because a few framework considerations state what without how (e.g., 'Brand voice consistent. The bot sounds like the brand it represents' offers no method), and there are no worked artifacts like a sample intent table.

4 / 5

Workflow Clarity

A clear implicit sequence runs decision ('Before designing the chatbot, decide whether a chatbot is the right tool') through pattern choice, intent architecture, grounding, branching, fallback, escalation, to analytics, and the 12-consideration framework provides an explicit ordered checklist with embedded checkpoints ('The litmus test', 'The escalation-quality test'). Matches the 4 anchor ('clear sequence with most checkpoints present; minor validation gaps'); not 5 because sections read as reference material rather than a stepwise process with validate-then-proceed gates, and not 3 because the framework section explicitly sequences the considerations and the failure-modes section provides diagnostic loops.

4 / 5

Progressive Disclosure

Scored against the actual bundle: all 9 referenced files exist in references/, and grep confirms no links inside reference files, so references are exactly one level deep. Each core section signals its detail file ('Detail in [references/...]') and the Reference files section indexes all nine with one-line summaries, making navigation easy. The SKILL.md itself stays at overview altitude while detail lives in references — matching the 5 anchor; the only nit (chatbot-anti-patterns.md is indexed but has no 'Detail in' pointer from a section body) is covered by the index.

5 / 5

Total

16

/

20

Passed

Description

100%Weight 40%Scale 1-5

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

An exemplary description: explicit trigger keywords and scenarios, a concrete capability inventory, a memorable three-pattern taxonomy, and an explicit design-vs-implementation boundary. It is dense rather than padded — every clause is load-bearing for triggering or scoping.

DimensionReasoningScore

Specificity

The description lists multiple concrete capability areas — 'Intent recognition architecture, branching logic, fallback handling, escalation to human, conversation analytics' — plus a three-pattern taxonomy and a design-vs-implementation boundary, covering the skill's full scope. This matches the 5 anchor ('lists multiple specific concrete actions; comprehensive coverage') rather than 4, since coverage mirrors the body's complete section set with no gaps.

5 / 5

Completeness

Both what ('Designing conversational flows for website chatbots and AI agents. Intent recognition architecture, branching logic, fallback handling, escalation to human, conversation analytics') and when ('Triggers on... Also triggers when...') are explicit and concrete, matching the 5 anchor exactly. Not 4, because the 'when' is not merely present but enumerates specific trigger keywords and three distinct usage scenarios.

5 / 5

Trigger Term Quality

An explicit trigger list — 'chatbot, conversational AI, AI agent, chat widget, intent design, conversational flow, bot escalation, LLM grounding' — plus natural scenario phrases ('when a chatbot is hallucinating, when a scripted bot is failing edge cases, or when a chatbot is being scoped for the first time'). These are terms a user would naturally say, with synonym variations (chatbot / conversational AI / AI agent / chat widget), matching the comprehensive 5 anchor; no file-extension terms apply to this domain.

5 / 5

Distinctiveness Conflict Risk

The description draws an explicit boundary — 'Distinguishes chatbot DESIGN (this skill) from chatbot IMPLEMENTATION (engineering and platform work)' — establishing a clear niche with distinct triggers, matching the 5 anchor. The broad term 'AI agent' carries slight overlap risk with agent-building skills, but the website-conversational-flow framing keeps it minimal.

5 / 5

Total

20

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository

rampstackco/claude-skills

Path

skills/chatbot-flow-design/SKILL.md

Reviewed

Table of Contents

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.