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

91%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

83%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 concise, highly actionable skill body with executable commands and well-organized sections. Its main weakness is the podcast workflow, which performs batch synthesis without any validation or verification checkpoint, capping workflow clarity.

Suggestions

Add an explicit validation checkpoint to the Podcast from Document workflow before synthesis (e.g., verify the generated /tmp/podcast_script.json is valid JSON with the expected speaker/text structure, and confirm the output .mp3 exists with non-zero size after generation).

Add a verify/retry feedback loop for the batch TTS step — since the script auto-chunks at sentence boundaries, note how to detect partial failures and re-run, so errors are caught before reporting success.

Tighten progressive disclosure by either keeping the body under 50 lines or moving the Reference parameter table (voice type, rate, pitch, encoding limits) into a short separate reference file linked from the overview.

Dimension	Reasoning	Score
Conciseness	The ~70-line body is lean and well-organized into Setup, Commands, Workflow, and Reference sections with no over-explanation of concepts Claude already knows; every section earns its place. Not below 5 because there is no padding or redundant concept exposition.	5 / 5
Actionability	Provides copy-paste-ready, fully executable commands with real flags for voices, tts (text/file/voice/rate/pitch/encoding), and podcast generation covering the common cases. Not below 5 because the examples are concrete and complete rather than pseudocode.	5 / 5
Workflow Clarity	Both workflows (single-voice narration, podcast from document) are sequenced, but the podcast workflow is a batch/multi-chunk operation (the script auto-chunks at sentence boundaries) with no validation or verification checkpoint before synthesis, which caps this dimension at 3 per the batch-operations rule. Not 4 because explicit validate/verify steps are absent rather than merely minor gaps.	3 / 5
Progressive Disclosure	Clear section structure with real, one-level-deep script references (extract.py, google_tts.py both present in scripts/); no nested references. Not 5 because the skill is slightly over the 50-line simple-skill threshold and all detail lives inline with no split reference material, leaving minor organization room.	4 / 5
	Total	17 / 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.

A strong, well-structured description that explicitly states capabilities, provides an extensive natural trigger-phrase list, and clearly answers both what the skill does and when to use it. It is concise, in third person, and distinct from other skills.

Dimension	Reasoning	Score
Specificity	Names the domain (Google Cloud TTS) and lists multiple concrete actions — narrate a document, read aloud text, generate audio from a file, create a recording, create a podcast — giving comprehensive coverage. Not below 5 since no concrete action category is missing for this skill's purpose.	5 / 5
Completeness	Clearly answers 'what' ('Convert documents and text to audio using Google Cloud Text-to-Speech') and 'when' ('Use this skill when the user wants to:' plus a concrete trigger-phrase list). Not below 5 because both what and when are explicit and concrete.	5 / 5
Trigger Term Quality	An explicit 'Trigger phrases:' list provides comprehensive natural-language synonyms users would actually say ('read this aloud', 'narrate this', 'text to speech', 'TTS', 'google tts', 'create a podcast', 'listen to this'). Not below 5 because coverage of synonyms and variants is thorough.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (Google Cloud TTS / audio generation) with distinct, audio-specific triggers unlikely to fire for unrelated skills. Not below 5 because conflict risk with other skills is minimal.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository: sanjay3290/ai-skills
Path: skills/google-tts/SKILL.md
Commit: 281d88d

Reviewed: 2 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.