CtrlK
BlogDocsLog inGet started
Tessl Logo

sherpa-onnx-tts

Local text-to-speech via sherpa-onnx (offline, no cloud)

70

1.51x
Quality

56%

Does it follow best practices?

Impact

100%

1.51x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./skills/sherpa-onnx-tts/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Discovery

40%

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 identifies a clear and distinctive niche (offline TTS via sherpa-onnx) but is too terse to be effective for skill selection. It lacks specific actions the skill can perform, natural trigger terms users would use, and an explicit 'Use when...' clause to guide Claude on when to select this skill.

Suggestions

Add a 'Use when...' clause, e.g., 'Use when the user asks to convert text to speech, generate audio from text, or needs offline/local TTS without cloud APIs.'

Include natural trigger term variations such as 'TTS', 'speech synthesis', 'generate audio', 'read text aloud', 'voice output'.

List specific concrete actions, e.g., 'Converts text to speech audio files, supports multiple voice models, generates WAV/MP3 output using sherpa-onnx locally.'

DimensionReasoningScore

Specificity

Names the domain (text-to-speech) and the tool (sherpa-onnx), and mentions key characteristics (offline, no cloud), but does not list specific concrete actions like 'convert text to audio files', 'adjust speech rate', or 'select voice models'.

2 / 3

Completeness

Provides a brief 'what' (text-to-speech via sherpa-onnx) but completely lacks a 'when should Claude use it' clause. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and since the 'what' is also thin, this scores a 1.

1 / 3

Trigger Term Quality

Includes 'text-to-speech' and 'sherpa-onnx' which are relevant, but misses common user variations like 'TTS', 'speech synthesis', 'read aloud', 'generate audio', 'voice output', or 'convert text to speech'.

2 / 3

Distinctiveness Conflict Risk

The combination of 'text-to-speech', 'sherpa-onnx', and 'offline/local' creates a very specific niche that is unlikely to conflict with other skills. The tool name alone is highly distinctive.

3 / 3

Total

8

/

12

Passed

Implementation

72%

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

A concise and well-structured skill for local TTS via sherpa-onnx. Its main weakness is the vague installation step—lacking specific download URLs or commands—and the absence of any verification/troubleshooting guidance after setup. The usage section is clear and practical.

Suggestions

Provide specific download URLs or commands for the runtime and model (e.g., a curl/wget command or a link to the releases page) to make the install step fully actionable.

Add a quick verification step after installation, such as running a test command and checking for expected output (e.g., 'Verify: `sherpa-onnx-tts --help` should print usage info').

Define what `{baseDir}` resolves to or clarify that it's automatically substituted by the skill loader.

DimensionReasoningScore

Conciseness

The content is lean and efficient. No unnecessary explanations of what TTS is or how sherpa-onnx works internally. Every section serves a clear purpose and there's no padding.

3 / 3

Actionability

Provides concrete config and CLI examples, but the install step is vague ('Download the runtime for your OS') without specifying URLs, commands, or exact download steps. The wrapper script is referenced but not shown. The {baseDir} placeholder is used without explicit definition.

2 / 3

Workflow Clarity

The install → configure → use sequence is present and logical, but there are no validation checkpoints (e.g., how to verify the runtime installed correctly, how to confirm the model is valid, or what to do if the command fails). For a setup-oriented skill, verification steps would be valuable.

2 / 3

Progressive Disclosure

For a simple, single-purpose skill under 50 lines, the content is well-organized into clear sections (Install, Usage) with notes for edge cases. No unnecessary nesting or external references needed.

3 / 3

Total

10

/

12

Passed

Validation

81%

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

Validation9 / 11 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

metadata_field

'metadata' should map string keys to string values

Warning

Total

9

/

11

Passed

Repository
attilaczudor/Test
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.