sherpa-onnx-tts
Local text-to-speech via sherpa-onnx (offline, no cloud)
63
56%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./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 and distinctive niche (local offline TTS via sherpa-onnx), which is its main strength. However, it is too terse—it lacks specific actions the skill can perform, misses common trigger terms users would naturally use, and critically omits any 'Use when...' guidance for skill selection.
Suggestions
Add a 'Use when...' clause with explicit triggers, e.g., 'Use when the user asks to convert text to speech, generate audio, or synthesize voice locally without internet access.'
Include common natural trigger terms users would say: 'TTS', 'speech synthesis', 'read aloud', 'generate audio', 'voice generation', 'convert text to audio'.
List specific concrete actions the skill performs, e.g., 'Converts text to speech audio files, supports multiple voices and languages, generates WAV/MP3 output using sherpa-onnx models.'
| Dimension | Reasoning | Score |
|---|---|---|
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', '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 for when Claude should select this skill. Per rubric guidelines, missing 'Use when' caps completeness at 2, and the 'what' is also quite thin, warranting 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', or 'convert text to speech'. | 2 / 3 |
Distinctiveness Conflict Risk | The combination of text-to-speech, sherpa-onnx, and offline/local constraints creates a very clear niche that is unlikely to conflict with other skills. This 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 that efficiently communicates how to set up and use sherpa-onnx for local TTS. Its main weaknesses are the vague installation steps (no specific download URLs or commands) and the lack of any verification/validation steps to confirm the setup works before use.
Suggestions
Add specific download URLs or commands for the runtime and voice model (e.g., curl/wget commands or links to the sherpa-onnx releases page) to make the install steps fully actionable.
Add a verification step after installation, such as running a test command to confirm the runtime and model are correctly installed (e.g., 'Verify: `sherpa-onnx-tts --help` should print usage info').
| 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 | Provides concrete config and CLI examples, but the install section is vague—'Download the runtime for your OS' and 'Download a voice model' lack specific URLs, commands, or download instructions. The usage example is copy-paste ready, but the setup path is incomplete. | 2 / 3 |
Workflow Clarity | The install-configure-use sequence is present and logical, but there are no validation checkpoints—no way to verify the runtime installed correctly, that the model is valid, or that the config is correct before attempting TTS. For a multi-step setup process, this is a gap. | 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 need for external file references given the scope. | 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 | |
- Repository
- qsimeon/openclaw-engaging
- Commit
4467e04
- 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.