CtrlK
BlogDocsLog inGet started
Tessl Logo

voice-conversation

Use when user wants continuous voice dialogue - speaks responses aloud and listens for follow-up, loops until user says stop or goodbye

60

Quality

69%

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

Fix and improve this skill with Tessl

tessl review fix ./voice-conversation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

The content is highly actionable with concrete tool calls, parameters, and a worked example, and the workflow is clearly sequenced with exit detection. Main weakness is mild redundancy across the diagram, critical rules, and common-mistakes sections that inflates token usage.

Suggestions

Remove the graphviz diagram (or the 'Critical Rules'/'Common Mistakes' tables) since they restate the same loop and exit logic already covered by the parameter table and example flow.

Collapse 'Critical Rules' and 'Common Mistakes' into a single concise list to cut redundancy.

If keeping the diagram, ensure the markdown code fence is a valid language tag rather than the stray 'dot' token to avoid rendering issues.

DimensionReasoningScore

Conciseness

The body is mostly efficient, but the graphviz diagram and the 'Critical Rules'/'Common Mistakes' sections restate information already conveyed by the parameter table and exit conditions, adding tokens that could be trimmed.

3 / 5

Actionability

Provides the concrete tool name mcp__voicemode__converse, an explicit parameter table with values, and a fully worked example flow with exact calls — copy-paste ready and covering common cases.

5 / 5

Workflow Clarity

The loop sequence is clear with an explicit exit-phrase checkpoint each turn and a clean farewell step; it stops short of 5 because the validation step is simple exit detection rather than a feedback loop for error recovery.

4 / 5

Progressive Disclosure

Content is well-organized into clearly headed sections with no nested references and no bundle files needed; it sits just over the ~50-line simple-skill threshold, so a 5 is not fully warranted.

4 / 5

Total

16

/

20

Passed

Description

62%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.

The description is clear and trigger-oriented, explicitly stating both what the skill does and when to use it. It is concise without padding and distinct from most other skills, though trigger-term coverage could be broadened.

Suggestions

Add more natural trigger variations such as 'voice chat', 'talk out loud', or 'hands-free conversation' so it matches a wider range of user phrasings.

Tighten the 'when' clause with concrete trigger phrasing (e.g., 'Use when the user asks for voice conversation, hands-free dialogue, or to talk back and forth aloud').

Optionally mention the underlying capability (MCP voice converse tool) to further distinguish it from generic TTS/listening skills.

DimensionReasoningScore

Specificity

Names the voice-dialogue domain with a few concrete actions ('speaks responses aloud', 'listens for follow-up', 'loops until user says stop or goodbye'), but coverage is not comprehensive enough for a 4.

3 / 5

Completeness

Explicit 'Use when user wants continuous voice dialogue' answers 'when', and the body lists what it does (speak aloud, listen, loop to exit); the 'when' could list more concrete trigger phrases to reach 5.

4 / 5

Trigger Term Quality

Includes natural phrases like 'continuous voice dialogue' and 'voice', but misses common variations/synonyms a user might say (e.g., 'voice chat', 'talk out loud', 'hands-free').

3 / 5

Distinctiveness Conflict Risk

'Continuous voice dialogue' is a distinct niche with a specific trigger, but it could overlap slightly with general voice/TTS skills, keeping it just below 5.

4 / 5

Total

14

/

20

Passed

Validation

100%

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

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
fernandezbaptiste/claude-playground-explorer
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.