Download brain/.raw/sources/claude-blog-skill/skills/blog-audio/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does blog-audio live?
The publisher keeps it at https://github.com/AgriciDaniel/claude-blog.
Which agents can use blog-audio?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.
>
name: blog-audio
description: >
Generate audio narration of blog posts using Google Gemini TTS.
Supports summary narration, full article read-aloud, and two-speaker
podcast/dialogue mode with 30 voice options. Outputs MP3 with HTML5
audio embed code. Works standalone via /blog audio or internally from
blog-write. Falls back gracefully when API key is not configured.
Use when user says "blog audio", "narrate blog", "audio version",
"text to speech", "tts", "podcast mode", "read aloud", "audio narration",
"voice", "narration", "generate audio".
user-invokable: true
argument-hint: "[generate|voices|setup] [file-or-text] [--mode summary|full|dialogue] [--voice name]"
license: MIT
metadata:
author: AgriciDaniel
version: "1.11.0"
Blog Audio: Gemini TTS Narration for Blog Posts
Generate professional audio narration of blog content using Google's Gemini TTS.
Three modes: summary (200-300 word spoken overview), full article read-aloud,
or two-speaker podcast dialogue. 30 voices, 80+ languages, HTML5 embed output.
Quick Reference
Command
What it does
/blog audio generate <file>
Generate audio narration of a blog post
/blog audio voices
Show available voices with characteristics
/blog audio setup
Check/configure API key for Gemini TTS
Prerequisites
Python 3.11+ (venv managed automatically by run.py)
GOOGLE_AI_API_KEY environment variable (same key used by blog-image)
FFmpeg (for WAV-to-MP3 conversion; falls back to WAV if missing)
test -n "${GOOGLE_AI_API_KEY:-}" && echo "GOOGLE_AI_API_KEY is set" || echo "GOOGLE_AI_API_KEY is not set"
If set: proceed with generation
If not set: guide the user:
"Audio generation requires a Google AI API key. Get one free at https://aistudio.google.com/apikey
Then set it: export GOOGLE_AI_API_KEY=your-key
This can be the same key used by /blog image, but it must be exported in the shell."
When called internally (from blog-write): return silently if key is missing.
Never block the writing workflow.
Setup
For /blog audio setup:
Check if GOOGLE_AI_API_KEY is set in environment
If blog-image uses project .mcp.json, confirm the referenced env var is exported
Insert the audio player after the introduction (below the first H2) or at the
very top of the article with a label: "Listen to this article" or "Audio version".
Graceful fallback: If GOOGLE_AI_API_KEY is not set, return immediately
with no error. The writing workflow continues without audio. Never block
blog-write because audio generation is unavailable.
Split into sections around 7,800 tokens; the script chunks and stitches prepared text
Unknown voice name
Run /blog audio voices to see valid options
API error
Check key validity and model availability
API key missing (internal call)
Return silently: writing workflow continues
Reference Documentation
Load on-demand: do NOT load all at startup:
references/voices.md: Full 30-voice catalog, recommendations by content type, dialogue pairings
How do I install blog-audio?
Download brain/.raw/sources/claude-blog-skill/skills/blog-audio/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
Where does blog-audio live?
The publisher keeps it at https://github.com/AgriciDaniel/claude-blog.
Which agents can use blog-audio?
Claude, Cursor, and Codex can read a SKILL.md you add from the publisher's repository.