sag

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

3.50x

Quality

55%

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 ./skills/sag/SKILL.md

Quality

Content

87%

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 immediately actionable guidance for using the `sag` CLI tool. Its strengths are token efficiency and concrete examples with real commands and flags. The main weakness is the lack of error handling or validation guidance, particularly around API key issues, voice availability, or failed generations.

Suggestions

Add a brief error handling note (e.g., what to do if the API key is missing/invalid or if a voice ID isn't found) to improve workflow robustness.

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 there's no validation or error handling guidance. For a tool that requires an API key and network calls, missing feedback on failures (invalid key, network errors, voice not found) is a gap. The pronunciation/delivery rules are listed but not sequenced as a troubleshooting workflow.	2 / 3
Progressive Disclosure	For a skill of this size and scope (under 50 lines, single-purpose CLI tool), the content is well-organized into logical sections (quick start, models, pronunciation, audio tags, voice responses) without needing external references. The built-in `sag prompting` command serves as a progressive disclosure mechanism for model-specific tips.	3 / 3
	Total	11 / 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 title than a functional skill description. It lacks concrete actions, explicit trigger guidance, and natural keyword coverage. While 'ElevenLabs' and 'text-to-speech' provide some specificity, the description fails to communicate what the skill actually does or when Claude should select it.

Suggestions

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

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

Expand natural keyword coverage to include variations users might say: 'speak', 'narrate', 'voice', 'audio output', 'speech synthesis', '.mp3'.

Dimension	Reasoning	Score
Specificity	The description mentions 'text-to-speech' and 'mac-style say UX' but does not list any concrete actions like generating audio files, converting text, or specifying output formats. It's more of a label than a capability description.	1 / 3
Completeness	The description weakly addresses 'what' (text-to-speech) but completely lacks any 'when' clause or explicit trigger guidance. There is no 'Use when...' or equivalent instruction for Claude to know when to select this skill.	1 / 3
Trigger Term Quality	Includes 'text-to-speech' and 'ElevenLabs' which are relevant keywords a user might use, and 'say' references the macOS command. However, it misses common variations like 'TTS', 'voice generation', 'audio', 'speech synthesis', or 'read aloud'.	2 / 3
Distinctiveness Conflict Risk	Mentioning 'ElevenLabs' and 'mac-style say UX' provides some distinctiveness, but the description is too terse to clearly carve out a niche. It could overlap with other audio or TTS-related skills without clearer boundaries.	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: deepgram/dglabs-deepclaw
Commit: ec8d4f8

Reviewed: about 1 month 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.