Local text-to-speech via sherpa-onnx (offline, no cloud)
70
56%
Does it follow best practices?
Impact
100%
1.51xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./openclaw/skills/sherpa-onnx-tts/SKILL.mdQuality
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 niche (offline TTS via sherpa-onnx) which makes it distinctive, but it is too terse—lacking specific actions, natural trigger terms users would say, and an explicit 'Use when...' clause. It reads more like a label than a functional description that would help Claude select it from a large skill set.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to convert text to audio, generate speech, read text aloud, or mentions TTS, voice synthesis, or sherpa-onnx.'
List specific concrete actions such as 'Converts text to speech audio files, supports multiple voices/languages, generates WAV/MP3 output' to improve specificity.
Include common natural-language trigger terms like 'TTS', 'read aloud', 'generate audio', 'speech', 'voice' to improve discoverability.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (text-to-speech) and the tool (sherpa-onnx), and clarifies it's offline/local, but doesn't list specific concrete actions like 'convert text to audio files', 'generate speech from documents', etc. | 2 / 3 |
Completeness | Provides a brief 'what' (text-to-speech via sherpa-onnx) but completely lacks a 'Use when...' clause or any explicit trigger guidance, which per the rubric caps completeness at 2, and the 'what' itself is thin enough to warrant a 1. | 1 / 3 |
Trigger Term Quality | Includes 'text-to-speech' and 'sherpa-onnx' which are relevant, but misses common user terms like 'TTS', 'read aloud', 'generate audio', 'speech synthesis', 'convert text to speech', or 'voice'. | 2 / 3 |
Distinctiveness Conflict Risk | Text-to-speech via a specific tool (sherpa-onnx) with the offline qualifier is a clear, distinct niche that is unlikely to conflict with other skills. | 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.
This is a well-structured, concise skill for local TTS setup. Its main weakness is the vague installation step—lacking specific download URLs or commands—which undermines actionability. Adding concrete download instructions and a quick verification step would significantly improve it.
Suggestions
Provide specific download URLs or commands for the runtime and voice model (e.g., `wget <url>` or a link to the releases page) instead of the vague 'Download the runtime for your OS'.
Add a verification step after installation, such as `sherpa-onnx-tts --help` or a test command to confirm the runtime and model are correctly installed.
| Dimension | Reasoning | Score |
|---|---|---|
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 | The usage command is concrete and copy-paste ready, and the config JSON is specific. However, the install section is vague—'Download the runtime for your OS' and 'Download a voice model' lack specific URLs, commands, or download instructions, leaving the user guessing. | 2 / 3 |
Workflow Clarity | The install → configure → use sequence is present and logical, but there are no validation checkpoints (e.g., verify the runtime extracted correctly, test that the model loads). For a multi-step setup process, explicit verification steps would improve reliability. | 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 advanced overrides. No unnecessary nesting or monolithic walls of text. | 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.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata.version' is missing | Warning |
metadata_field | 'metadata' should map string keys to string values | Warning |
Total | 9 / 11 Passed | |
0c1ec2b
Table of Contents
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.