CtrlK
BlogDocsLog inGet started
Tessl Logo

sherpa-onnx-tts

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

83

1.51x
Quality

75%

Does it follow best practices?

Impact

100%

1.51x

Average score across 3 eval scenarios

SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./openclaw/skills/sherpa-onnx-tts/SKILL.md

The canonical home for this skill is sherpa-onnx-tts in Hung-Reo/hungreo-openclaw

SKILL.md
Quality
Evals
Security

Quality

Content

86%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 content is a tight, well-structured simple skill with executable commands and clear sequencing. The only gaps are a missing verification checkpoint and an unverified bundle reference for the bin wrapper.

DimensionReasoningScore

Conciseness

The body is lean with no padding or explanations of concepts Claude already knows; every section (Install, Usage, Notes) earns its place and assumes Claude's competence.

5 / 5

Actionability

Concrete executable commands and a config snippet are copy-paste ready, but the JSON5 config uses unquoted keys and the bin wrapper path is referenced without listing the bundle, leaving a minor gap.

4 / 5

Workflow Clarity

Install → config → run is clearly sequenced and unambiguous for this simple single-purpose skill, though no explicit validation/checkpoint step is given.

4 / 5

Progressive Disclosure

Well-organized sections in under 50 lines with no need for external references; the simple-skill exception allows a 5 for clean structure alone.

5 / 5

Total

18

/

20

Passed

Description

65%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 is concise, distinct, and uses natural trigger terms, but it lacks an explicit "Use when..." clause and a broader enumeration of capabilities. Adding trigger guidance would lift the completeness and specificity scores.

Suggestions

Add a "Use when..." clause naming natural triggers (e.g., "Use when the user needs speech/audio output, voice generation, or offline TTS without cloud calls").

Broaden capability phrasing to cover common actions (e.g., generating WAV/audio files, picking voices/models) for fuller specificity.

Include common synonyms or extensions ("speech synthesis", "voice", ".wav") to round out trigger term coverage.

DimensionReasoningScore

Specificity

"Local text-to-speech via sherpa-onnx" names the domain plus one concrete action (TTS) but offers no comprehensive list of capabilities, matching the anchor for naming domain with 1-2 concrete actions.

3 / 5

Completeness

The "what" is clear (local TTS via sherpa-onnx) but there is no "Use when..." clause or equivalent trigger guidance, which per the rubric caps completeness at 3.

3 / 5

Trigger Term Quality

Natural terms "text-to-speech", "TTS", "local", and "offline" give good coverage a user would say, though common synonyms like "speech synthesis", "voice", or file extensions are absent.

4 / 5

Distinctiveness Conflict Risk

"Local text-to-speech via sherpa-onnx (offline, no cloud)" carves a clear niche with distinct triggers and minimal overlap risk against other skills.

5 / 5

Total

15

/

20

Passed

Validation

87%

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

Validation14 / 16 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

14

/

16

Passed

Repository
trpc-group/trpc-agent-go
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.