CtrlK
BlogDocsLog inGet started
Tessl Logo

voice-update

This skill should be used when the agent needs to give a spoken voice update to the user, or when reminded by a Stop hook to provide audio feedback. Use this skill to speak a short summary of what was accomplished.

67

Quality

80%

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 ./plugins/voice/skills/voice-update/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is a lean, actionable, well-organized single-purpose skill; its main weakness is minor redundancy between the How to Use and Summary Guidelines sections.

Suggestions

Merge the '1-2 sentences' guidance so it appears once, and trim the three example utterances to one or two to tighten conciseness.

State the uvx/afplay/aplay prerequisites up front in How to Use rather than only in Notes, so a failure path is obvious before the first call.

DimensionReasoningScore

Conciseness

The body avoids explaining concepts Claude already knows and stays focused, but the 1-2 sentence guidance is repeated across 'How to Use' and 'Summary Guidelines', and the three example utterances add length that could be trimmed.

2 / 3

Actionability

It provides a fully executable, copy-paste-ready command (`${CLAUDE_PLUGIN_ROOT}/scripts/say "..."`) with concrete examples including the `--voice azure` option, leaving no ambiguity about how to invoke it.

3 / 3

Workflow Clarity

For a simple single-task skill the sequence is unambiguous (summarize in 1-2 sentences, then call the say script), and the Notes surface prerequisites (uvx, afplay/aplay) and the first-use server delay.

3 / 3

Progressive Disclosure

The skill is under 50 lines with no need for external reference files, and content is organized into clearly headed sections (When to Use, How to Use, Calling the Say Script, Summary Guidelines, Notes) with no nested references.

3 / 3

Total

11

/

12

Passed

Description

75%

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 clearly defines a niche voice-output skill with explicit when-to-use guidance, though its action language is somewhat repetitive and its trigger terms lean partly on internal hook jargon.

Suggestions

Replace internal jargon like 'Stop hook' with user-facing phrasing or pair it with a natural term so trigger matching works in both agent-driven and user-driven cases.

Condense the repeated 'give a spoken voice update / provide audio feedback / speak a short summary' into one concrete action statement to sharpen specificity.

DimensionReasoningScore

Specificity

Phrases like 'give a spoken voice update', 'provide audio feedback', and 'speak a short summary' name the voice domain and a core action, but they restate one action rather than listing multiple distinct concrete capabilities.

2 / 3

Completeness

It states what the skill does ('speak a short summary of what was accomplished') and gives an explicit 'should be used when'/'Use this skill' trigger clause covering both agent-driven and hook-driven cases.

3 / 3

Trigger Term Quality

It includes some natural terms ('spoken voice update', 'audio feedback', 'summary'), but 'Stop hook' is an internal/technical trigger users would not say, and common variations like 'read it out loud' or 'TTS' are missing.

2 / 3

Distinctiveness Conflict Risk

The audio/voice-output niche ('spoken voice update', 'audio feedback', Stop-hook reminder) is distinct from typical text skills and unlikely to trigger for the wrong skill.

3 / 3

Total

10

/

12

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
pchalasani/claude-code-tools
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.