CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

voice-conversation

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

Quality

81%

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

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

Highly actionable body with exact tool-call specifics, a concrete parameter table, and a worked example flow covering the full loop including clean exit. The main weakness is redundancy: the same rules are stated three times across the parameter table, Critical Rules, and Common Mistakes.

Suggestions

Merge 'Critical Rules' and 'Common Mistakes' into a single section (or drop one) — they restate the parameter table and exit conditions a third time, costing ~14 lines.

Replace the dot-graph workflow with a short numbered loop description or drop it, since the Example Flow already conveys the same sequence more concretely.

Add one line on handling a timed-out or empty listen response (e.g., re-prompt once, then confirm before exiting) to close the workflow's edge-case gap.

DimensionReasoningScore

Conciseness

The parameter table, exit conditions, and example flow are efficient, but 'Critical Rules' and 'Common Mistakes' restate the same wait_for_response/skip_tts/exit-detection guidance for a third time (~14 redundant lines), and the dot graph duplicates the loop already shown in the example flow. This is more than the minor trimming of a 4, though the bulk is not padded.

3 / 5

Actionability

Fully executable guidance: the exact tool name 'mcp__voicemode__converse', a parameter table with concrete values (wait_for_response=true, skip_tts=false, listen_duration_max=60), and copy-paste-ready example calls covering conversation start, mid-turn, and clean exit. Meets the 5 anchor for executable, common-case-covering commands.

5 / 5

Workflow Clarity

The loop is clearly sequenced (call converse → process response → exit check → farewell with wait_for_response=false) with an explicit exit checkpoint every turn. It stays below 5 because edge cases like a timed-out or empty listen response are unaddressed; it is not a destructive/batch operation, so no validation cap applies.

4 / 5

Progressive Disclosure

A self-contained skill with well-organized sections and no content that belongs in separate files; no external references are needed, satisfying the simple-skill bar for progressive disclosure.

5 / 5

Total

17

/

20

Passed

Description

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

A solid third-person description that explicitly covers both what the skill does and when to use it, with concrete actions and recognizable exit terms. Its weaknesses are a circular 'when' clause and missing natural synonyms like 'talk', 'conversation', or 'hands-free'.

Suggestions

Replace the circular trigger ('Use when user wants continuous voice dialogue') with distinct trigger phrases such as 'Use when the user asks to talk out loud, have a spoken conversation, go hands-free, or enables voice mode'.

Add natural synonyms users would say — 'talk', 'conversation', 'voice call', 'speak to me' — to broaden trigger term coverage toward the 5 anchor.

DimensionReasoningScore

Specificity

Phrases like 'speaks responses aloud and listens for follow-up, loops until user says stop or goodbye' list several concrete actions, but coverage has minor gaps (e.g., the clean-exit farewell is absent). A 3 would name only 1-2 actions; a 5 would require a comprehensive action inventory.

4 / 5

Completeness

Both 'what' ('speaks responses aloud and listens for follow-up, loops until user says stop or goodbye') and 'when' ('Use when user wants continuous voice dialogue') are explicitly present, but the when-clause is circular — it restates the skill's own name rather than naming distinct trigger phrases, so it does not reach a 5's concrete triggers.

4 / 5

Trigger Term Quality

Natural terms are present ('voice dialogue', 'speaks', 'listens', 'follow-up', 'stop', 'goodbye'), but common variations users would actually say ('talk', 'conversation', 'voice mode', 'hands-free') are missing. Coverage exceeds the sparse keyword set of a 3 but falls short of a 5's synonym and extension coverage.

4 / 5

Distinctiveness Conflict Risk

The continuous-voice-dialogue loop with explicit stop/goodbye triggers is a mostly distinct niche. Minor overlap risk with adjacent voice/TTS or voice-mode skills keeps it below 5; it is far more specific than the broad overlap of a 3.

4 / 5

Total

16

/

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

fernandezbaptiste/claude-playground-explorer

Path

voice-conversation/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.