voice-interaction

Q: How do I install voice-interaction?

Run npx skills add https://github.com/owl-listener/inclusive-design-skills --skill voice-interaction in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/voice-interaction/ (personal) or .claude/skills/voice-interaction/ (project).

by owl-listenerMedia & Creative

Design voice interactions and speech interfaces that work for people with diverse speech patterns, accents, and communication styles. Use when designing voice commands, voice search, dictation, voice assistants, or any interface that accepts speech input. Triggers on: voice, speech, dictation, voice command, voice search, speech recognition, accent, stutter, speech disability, non-verbal, AAC, voice assistant, talk to type.

Installs: 75
Last 24h: —
Trending rank: —
Security: Not audited

Install

Works with every agent the skills CLI supports.

npx skills add https://github.com/owl-listener/inclusive-design-skills --skill voice-interaction

01
Install
Run the command in your project. The CLI asks which agents to install for.
02
Describe the task
Ask your agent for something this skill covers. It loads voice-interaction automatically when relevant.
03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.

SKILL.md

The instructions your agent reads when the skill is triggered.

Voice Interaction Design

Design voice interfaces that work for the full range of human speech — including accents, speech disabilities, non-native speakers, and people in noisy or quiet environments.

Who This Is For

People with motor disabilities who use voice as primary input
People who stutter, have dysarthria, or other speech differences
Non-native speakers with varied accents
People in environments where typing is impractical
Anyone who prefers voice to typing for certain tasks

Core Principles

Voice Should Never Be the Only Option

Every voice interaction must have a text/touch/keyboard alternative
Voice is an accelerator, not a gatekeeper
Don't require voice for identity verification or critical actions unless an alternative exists

Design for Speech Variation

Support varied pacing — don't cut off slow speakers
Allow generous silence before timing out
Don't penalise repetition, filler words, or self-correction
Support multiple phrasings for the same intent ("go back", "previous page", "take me back", "undo")

Feedback Must Be Clear

Confirm what the system heard (visual transcript)
Make it easy to correct misrecognition
Show when the system is listening vs. processing vs. waiting
Never execute a destructive action on voice alone without confirmation

Design Patterns

Flexible Recognition

Accept multiple ways to say the same command
Don't require exact phrasing — intent matters more than syntax
Support "did you mean?" clarification for ambiguous input
Allow users to spell out words the system doesn't recognise

Graceful Failure

When recognition fails: show what was heard and offer correction
Never respond with just "I didn't understand" — offer alternatives
Provide a "type instead" option at every failure point
After repeated failures: proactively suggest switching to text input

Privacy and Control

Clear visual/audio indicator when microphone is active
Easy one-action mute/stop listening
Don't record or transmit audio without explicit consent
Allow users to review and delete voice data

Assessment Questions

Can every voice-activated feature also be completed without voice?
Does the system handle varied speech patterns without frustration?
Is there clear feedback showing what the system heard?
Can users easily correct misrecognition?
Is it obvious when the system is listening?

FAQ

What does the voice-interaction skill do?

How do I install voice-interaction?

Run npx skills add https://github.com/owl-listener/inclusive-design-skills --skill voice-interaction in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/voice-interaction/ (personal) or .claude/skills/voice-interaction/ (project).

Which AI agents can use voice-interaction?

Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.

Is voice-interaction safe to install?

No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.

Who maintains voice-interaction?

It is published by owl-listener in owl-listener/inclusive-design-skills. It has 75 recorded installs.