sag

ElevenLabs text-to-speech with mac-style say UX.

3.50x

Quality

51%

Does it follow best practices?

Impact

91%

3.50x

Average score across 3 eval scenarios

Securityby

Passed

No known issues

Optimize this skill with Tessl

npx tessl skill review --optimize ./openclaw/skills/sag/SKILL.md

Quality

Content

79%

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-crafted, concise skill that provides highly actionable CLI commands and configuration details for ElevenLabs TTS. Its main strengths are token efficiency and concrete examples. Minor weaknesses include the lack of explicit validation/error handling steps and the absence of external references for deeper topics, though for a skill of this scope these are minor concerns.

Suggestions

Add a brief error handling note (e.g., what happens if the API key is missing or the voice ID is invalid, and how to recover).

Consider adding a validation step for long outputs, such as generating a short test clip before committing to full generation.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It assumes Claude knows how to use CLI tools and doesn't waste tokens explaining what TTS is or how APIs work. Every section delivers actionable information concisely.	3 / 3
Actionability	Provides concrete, copy-paste ready commands throughout (e.g., `sag "Hello there"`, `sag -v Clawd -o /tmp/voice-reply.mp3 "Your message here"`). Specific flags, model names, voice IDs, and audio tags are all directly usable.	3 / 3
Workflow Clarity	The 'Chat voice responses' section has a clear two-step workflow (generate then include), but the pronunciation/delivery rules section is more of a reference list than a sequenced workflow. There's a note to 'confirm voice + speaker before long output' but no explicit validation or error recovery steps.	2 / 3
Progressive Disclosure	The content is well-organized with clear sections and headers, but everything is inline in a single file. The `sag prompting` command reference is a nice touch for progressive disclosure via the CLI itself, but there are no references to external files for advanced topics like detailed model comparisons or voice catalog.	2 / 3
	Total	10 / 12 Passed

Description

22%

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 extremely terse and reads more like a label than a functional skill description. It lacks concrete actions, explicit trigger guidance ('Use when...'), and sufficient natural keywords for reliable skill selection. While 'ElevenLabs' provides some distinctiveness, the description needs significant expansion to be effective.

Suggestions

Add a 'Use when...' clause with trigger terms like 'text-to-speech', 'TTS', 'read aloud', 'generate audio', 'voice', 'speak text'.

List specific concrete actions such as 'Converts text to speech audio using ElevenLabs API, plays audio via macOS say-style interface, supports voice selection and audio file export'.

Include common keyword variations users might say: 'TTS', 'voice generation', 'audio output', 'speech synthesis', 'ElevenLabs'.

Dimension	Reasoning	Score
Specificity	The description mentions 'text-to-speech' and 'mac-style say UX' but does not list concrete actions like generating audio files, converting text to speech, or specifying supported formats. It's more of a label than a capability description.	1 / 3
Completeness	The description loosely addresses 'what' (text-to-speech) but has no explicit 'when' clause or trigger guidance. Per the rubric, a missing 'Use when...' clause caps completeness at 2, and the 'what' is also weak, so this scores a 1.	1 / 3
Trigger Term Quality	Includes 'text-to-speech', 'ElevenLabs', and 'say' which are relevant keywords users might use, but misses common variations like 'TTS', 'voice generation', 'audio', 'speak', or 'read aloud'.	2 / 3
Distinctiveness Conflict Risk	Mentioning 'ElevenLabs' and 'mac-style say' provides some distinctiveness, but the description is too terse to clearly delineate its niche from other potential audio or TTS skills.	2 / 3
	Total	6 / 12 Passed

Validation

72%

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 — 8 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	8 / 11 Passed

Repository: trpc-group/trpc-agent-go
Commit: 63e87f0

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.