sherpa-onnx-tts

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

1.51x

Quality

56%

Does it follow best practices?

Impact

100%

1.51x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./openclaw/skills/sherpa-onnx-tts/SKILL.md

Quality

Content

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 reasonably well-structured skill that is concise and well-organized for its scope. Its main weakness is the vague installation instructions—lacking specific download URLs or commands—which undermines actionability. Adding a quick verification step after installation would also improve workflow clarity.

Suggestions

Provide specific download commands or URLs for the runtime and voice model (e.g., `wget https://...` or a script reference) 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 setup is working before proceeding to usage.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It doesn't explain what TTS is or how sherpa-onnx works internally. Every section serves a purpose: install, config, usage. The notes section is compact and covers edge cases without over-explaining.	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 scripts to execute. This leaves a critical step underspecified.	2 / 3
Workflow Clarity	The sequence (install → configure → use) is clear and logical. However, there are no validation checkpoints—no way to verify the runtime installed correctly, that the model is valid, or that the config is properly loaded. For a multi-step setup process, a verification step (e.g., 'Test: sherpa-onnx-tts --help should print usage') 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, Notes). No bundle files are provided, and the skill doesn't need external references given its scope. The structure is appropriate for the complexity level.	3 / 3
	Total	10 / 12 Passed

Description

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 to be effective for skill selection. It lacks specific actions, common trigger terms users would naturally use, and critically missing a 'Use when...' clause to guide Claude on when to select this skill.

Suggestions

Add a 'Use when...' clause such as 'Use when the user asks to convert text to speech, generate audio from text, or needs TTS functionality offline.'

Include common trigger term variations like 'TTS', 'speech synthesis', 'generate audio', 'read aloud', 'convert text to audio'.

List specific concrete actions such as 'Converts text to audio files, selects voice models, adjusts speech parameters using sherpa-onnx locally without cloud dependencies.'

Dimension	Reasoning	Score
Specificity	Names the domain (text-to-speech) and the tool (sherpa-onnx), and mentions key attributes (offline, no cloud), but does not list specific concrete actions like 'convert text to audio files', 'adjust speech rate', or 'select voices'.	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 weak, so this scores 1.	1 / 3
Trigger Term Quality	Includes 'text-to-speech' and 'sherpa-onnx' which are relevant keywords, but misses common user variations like 'TTS', 'speech synthesis', 'read aloud', 'generate audio', 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.	3 / 3
	Total	8 / 12 Passed

Validation

81%

Warnings & errors only

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: trpc-group/trpc-agent-go
Commit: fc01b4b

Reviewed: 3 days ago

Table of Contents

Discovery Implementation Validation

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.