sag

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

Quality

51%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./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 guidance for using the `sag` CLI tool. Its main strengths are token efficiency and concrete examples. The primary weaknesses are the lack of validation/error-handling steps in workflows and slightly underdeveloped progressive disclosure for edge cases or advanced usage.

Suggestions

Add a brief validation step after generating audio (e.g., check file exists/size before including MEDIA reference) to improve workflow reliability.

Consider adding error handling guidance for common failure modes (missing API key, invalid voice ID, network errors) to cap workflow clarity higher.

Dimension	Reasoning	Score
Conciseness	The content is lean and efficient. It uses terse bullet points, avoids explaining what TTS or ElevenLabs is, and every line provides actionable information Claude wouldn't already know (CLI flags, model names, audio tags, voice IDs).	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 model names, specific audio tags with examples, and exact environment variable names.	3 / 3
Workflow Clarity	The chat voice response section has a clear two-step sequence (generate then include), and pronunciation rules are ordered by priority ('First fix: respell...'). However, there's no validation or error handling guidance—e.g., what to do if the API key is missing, if voice generation fails, or how to verify the output file was created before referencing it.	2 / 3
Progressive Disclosure	The content is well-organized with clear sections and appropriate length for a SKILL.md. However, it mentions `sag prompting` for model-specific tips without linking to any reference file, and the voice character tips section could benefit from a pointer to a more comprehensive guide if one exists. The structure is good but navigation signals are minimal.	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.

This description is far too terse to serve as an effective skill selector. It names the technology (ElevenLabs) and a vague UX pattern ('mac-style say') but fails to describe concrete capabilities or provide any trigger guidance for when Claude should select this skill. It reads more like a title than a description.

Suggestions

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

List specific concrete actions the skill performs, e.g., 'Converts text to speech audio using ElevenLabs API, plays audio locally via macOS say-style interface, supports voice selection and parameter tuning'.

Include common user phrasings and file types/formats involved, such as 'MP3', 'audio file', 'speak this text', to improve trigger term coverage.

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, adjusting voice parameters, etc. It's more of a label than a capability description.	1 / 3
Completeness	The 'what' is only vaguely implied (text-to-speech) and there is no 'when' clause at all. Missing a 'Use when...' clause caps this at 2, and the weak 'what' brings it to 1.	1 / 3
Trigger Term Quality	Includes 'text-to-speech', 'ElevenLabs', and 'say' which are relevant trigger terms a user 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 from generic audio or speech skills, but the description is too terse to clearly delineate its niche from other TTS or audio-related 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: qsimeon/openclaw-engaging
Commit: 4467e04

Reviewed: 3 months 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.