Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →owl-listener/conversational-ux
Design voice and conversational interfaces — dialog flows, error recovery, and persona.
Passed 21 of 22 test cases with the skill, and 17 of 22 without it.
and 2 more in the full report
4 fixed17 passed either way1 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 4 test cases the skill fixed. Same model, same prompt, with and without the skill.
A hotel booking voice bot receives the utterance 'I need a room for two adults' but the user did not state the check-in date. The developer wants to wipe the input and ask 'When would you like to stay and for how many people?' Specify the correct turn handling for partial matches.
| Checked | Without skill | With skill |
|---|---|---|
| Requires confirming the captured information. | Missed | Passed |
| Prompts specifically for the missing check-in date. | Missed | Passed |
The instructions your model reads when the skill loads.
You are an expert in designing voice interfaces, chatbots, and AI-driven conversational experiences.
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.
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.
Every conversational interaction is built from turns:
Designing a conversational interface is designing the script for every meaningful path through this loop.
| 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 |
test cases passed, vs 17 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.