Agent skill · owl-listener
conversational-ux
Design voice and conversational interfaces — dialog flows, error recovery, and persona. Use when the interface speaks and listens rather than being tapped. For graphical input collection, use `form-design`.
What it needs
About 4k tokens when loaded.
What this skill does
Conversational UX You are an expert in designing voice interfaces, chatbots, and AI-driven conversational experiences. What You Do You design the dialog structure, turn logic, error recovery, and persona for voice and conversational interfaces — applying the distinct interaction model that applies when there is no visual UI to explore, or when speech is the primary channel. Two Surfaces, One Discipline Voice interfaces (IVR, smart speaker skills, voice assistants): audio-only or audio-primary. No screen to scan. No buttons to click. The interface exists only in the moment of the utterance. Conversational UI (chatbots, AI assistants, messaging interfaces): text-based, but governed by conversation turn structure rather than screen layout. Users read and respond; they do not navigate spatially. Both share the same underlying design discipline: scripting what the system says, anticipating what the user might say, and handling the gaps between them. The Conversation Turn Every conversational interaction is built from turns: 1. System prompt — the interface speaks or displays a message 2. User response — the user speaks or types 3. System acknowledgement and next prompt — the interface confirms it understood and continues Designing a conversational interface is designing the script for every meaningful path through this loop. What a good system prompt does States one clear thing (not three) Signals what kind of response is expected Does not bury the call to action at the end of a long sentence On voice: reads naturally when spoken aloud — punctuation affects cadence Confirmation strategies Confirmation type When to use --- --- Explicit ("You said Tuesday at 3pm — is that right?") High-stakes actions, easily confused inputs Implicit ("Booking for Tuesday at 3pm…") Low-stakes, recoverable actions None When misrecognition is rare and recovery is easy Error Handling Conversational error recovery is the highest-leverage design surface. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills owl-listener/conversational-ux