CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

google-tts

Convert documents and text to audio using Google Cloud Text-to-Speech. Use this skill when the user wants to: narrate a document, read aloud text, generate audio from a file, convert text to speech, create a recording of documentation or analysis, create a podcast from a document, or use Google TTS/text-to-speech. Trigger phrases: "read this aloud", "narrate this", "create a recording", "text to speech", "TTS", "convert to audio", "audio from document", "listen to this", "generate audio", "google tts", "create a podcast".

Quality

97%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

SKILL.md
Quality
Evals
Security

Quality

Content

93%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.

A tight, highly executable skill body: real commands, sensible defaults, and useful non-obvious parameter guidance. The only gap is validation in the podcast workflow, where errors in the generated script JSON would only surface after API synthesis has begun.

DimensionReasoningScore

Conciseness

The body is lean and purely operational — commands, options, and workflow steps with no explanation of concepts Claude already knows; even the Reference section contains only non-obvious facts (rate/pitch ranges, 5000-byte limit, pricing). Every token earns its place.

5 / 5

Actionability

All commands are copy-paste ready and verified against the actual script's CLI (voices/tts/podcast subcommands with matching --file, --voice, --rate, --encoding flags), and the podcast JSON script format is shown with a concrete example covering the common cases.

5 / 5

Workflow Clarity

Both workflows are clearly numbered with concrete commands, and single-voice narration ends with 'Report file location and size' as a checkpoint — but the podcast workflow has no validation step (e.g., checking the generated script JSON before synthesis or verifying audio output), so it sits between the 'most checkpoints' anchor and the 'checkpoints missing or implicit' anchor.

4 / 5

Progressive Disclosure

The ~70-line body is well-organized into Commands/Workflow/Reference sections, and the two bundle scripts it references (scripts/google_tts.py, scripts/extract.py) both exist and are invoked directly at one level of depth; no separate reference files are needed.

5 / 5

Total

19

/

20

Passed

Description

100%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.

An exemplary description: concrete third-person capabilities, an explicit use-when clause, and a rich list of natural trigger phrases. Its only nit is mild redundancy between the 'Use when' list and the 'Trigger phrases' list, which does not affect any dimension's anchors.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'narrate a document, read aloud text, generate audio from a file, convert text to speech, create a recording of documentation or analysis, create a podcast' — comprehensively covering the skill's capabilities in third-person voice, matching the anchor-5 example's breadth.

5 / 5

Completeness

It explicitly answers both parts: what ('Convert documents and text to audio using Google Cloud Text-to-Speech') and when ('Use this skill when the user wants to: ...' plus an explicit 'Trigger phrases:' list), mirroring the anchor-5 example structure exactly.

5 / 5

Trigger Term Quality

Trigger coverage is comprehensive and natural: 'read this aloud', 'narrate this', 'listen to this', 'text to speech', 'TTS', 'google tts', 'convert to audio', 'create a podcast', including synonyms a user would actually say. Not 4 because no common natural phrasing for this need is missing.

5 / 5

Distinctiveness Conflict Risk

It carves a clear niche (Google Cloud TTS) with distinct triggers like 'google tts' and 'text to speech', so conflict risk with unrelated skills is minimal — fitting the 'clear niche with distinct triggers' anchor rather than the 'minor overlap risk' anchor at 4.

5 / 5

Total

20

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

sanjay3290/ai-skills

Path

skills/google-tts/SKILL.md

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.