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.

68

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

92%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 body is a well-structured, actionable, and concise guide for a simple audio-feedback skill, with executable examples and a clear two-step workflow. Only minor tightening of the slightly redundant summary guidelines would push it to fully lean.

DimensionReasoningScore

Conciseness

The body is mostly lean with direct commands and examples that earn their place; the 'Summary Guidelines' section partly restates the 'How to Use' step about 1-2 sentence summaries, a minor instance of over-explanation that could be trimmed, matching the 4 anchor rather than the fully lean 5.

4 / 5

Actionability

Provides copy-paste-ready, fully executable bash commands ('${CLAUDE_PLUGIN_ROOT}/scripts/say "..."') with both a plain and a flagged ('--voice azure') example covering the common cases, matching the 5 anchor.

5 / 5

Workflow Clarity

This is a simple, non-destructive single-purpose skill with an unambiguous two-step sequence (summarize, then call the say script); per the simple-skill exception, clear and unambiguous single-action workflows score 5, and no validation checkpoint is required for audio output.

5 / 5

Progressive Disclosure

Under 50 lines, single-purpose, with well-organized sections (When to Use, How to Use, Calling the Say Script, Summary Guidelines, Notes) and no need for external reference files; per the guideline, such skills can score 5 with well-organized sections alone.

5 / 5

Total

19

/

20

Passed

Description

70%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 clearly communicates both purpose and trigger conditions for a spoken voice-update skill, with concrete actions and low conflict risk. It could be improved by listing more specific capabilities and adding common synonyms like 'announce' or 'text-to-speech'.

Suggestions

Expand the 'what' with 1-2 more concrete actions (e.g., 'announces task completion aloud, reads short summaries via text-to-speech') to lift specificity toward 5.

Add natural synonyms users might say ('announce', 'speak aloud', 'text-to-speech', 'TTS') to broaden trigger-term coverage.

Keep the explicit 'Use when...' clause but tighten the 'what' so both halves are equally concrete.

DimensionReasoningScore

Specificity

Names the domain (spoken voice updates/audio feedback) and one concrete action ('speak a short summary of what was accomplished'), but does not enumerate several specific actions, matching the anchor for 1-2 concrete actions rather than the comprehensive list at 5.

3 / 5

Completeness

Explicitly answers 'what' (speak a short summary / spoken audio feedback) and 'when' (when the agent needs to give a voice update, or when reminded by a Stop hook), with two concrete trigger conditions; the 'what' is somewhat brief so it sits at 4 rather than 5.

4 / 5

Trigger Term Quality

Includes natural user-facing terms ('spoken voice update', 'audio feedback', 'short summary') plus the 'Stop hook' trigger, giving good keyword coverage; a few common synonyms (e.g., 'announce', 'text-to-speech') are missing, keeping it just below 5.

4 / 5

Distinctiveness Conflict Risk

The spoken-audio-update niche with a Stop-hook trigger is a clear, distinct use case with minimal overlap risk; it is not quite as crisply bounded as the top anchor, so 4 rather than 5.

4 / 5

Total

15

/

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