Google Ai Studio Tts logo

Google Ai Studio Tts

Community
maystudios
google-ai-studio-tts

Generate speech, podcasts, voiceovers, and multi-speaker dialogue with Google AI Studio's Gemini Flash TTS by driving the live web app in Chrome via the claude-in-chrome MCP server. Use whenever the user asks to (1) create a podcast, audiobook chapter, narration, audio drama, or voiceover with Gemini / Google AI Studio TTS; (2) turn a script into multi-speaker audio (e.g. "two-host podcast", "Speaker 1 / Speaker 2 dialogue", "Puck and Zephyr"); (3) tweak a TTS prompt with Scene, Sample Context, Director's note (Style/Pace/Accent), Audio Profile, voice picker, or Temperature; or (4) render audio with inline tags like [enthusiastic], [whispers], [laughs]. Triggers on phrases like "use AI Studio TTS", "generate this podcast in AI Studio", "render with gemini-3.1-flash-tts-preview", "speak this with Aoede/Puck/Zephyr", or any request for browser-driven Gemini speech generation.

Overview

Publishermaystudios
Repositoryclaude-skills
Skill namegoogle-ai-studio-tts
Stars
26
Forks
2
Bundled files
3
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 3 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by maystudios on GitHub. Read the source before you install it.

Installation

Install the Google Ai Studio Tts AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/maystudios/claude-skills/tree/main/google-ai-studio-tts
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/maystudios/claude-skills.git /tmp/claude-skills
mkdir -p .claude/skills
cp -r /tmp/claude-skills/google-ai-studio-tts .claude/skills/google-ai-studio-tts
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Google Ai Studio Tts in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Google Ai Studio Tts on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Google Ai Studio Tts is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Google AI Studio TTS (browser-driven)

Overview

This skill drives https://aistudio.google.com/generate-speech in the user's already-open Chrome (via the claude-in-chrome MCP tools) to render audio with Gemini Flash TTS. The user must already be signed in to Google AI Studio in Chrome — never create accounts, never enter passwords, never share credentials.

There are two input modes in the UI. Choose based on what the user asked for:

User intentModeWhy
Single narrator, monologue, or short voiceoverTextOne textarea, fastest path.
Multi-speaker dialogue with simple Speaker 1: … linesTextSame single textarea — prefix lines with Speaker 1:, Speaker 2:.
Multi-speaker with per-line speaker chip, finer control, easy editingComposerOne block per utterance, each with its own voice chip.
Anything where the user explicitly mentions "scene", "sample context", "director's note", or wants the speaker chips visibleComposerMatches the visible UI elements they're referring to.

Both modes share the Scene and Sample Context fields and the Speaker settings panel on the right.

Required tools

Load these claude-in-chrome MCP tools via ToolSearch before starting:

select:mcp__claude-in-chrome__tabs_context_mcp,mcp__claude-in-chrome__tabs_create_mcp,mcp__claude-in-chrome__navigate,mcp__claude-in-chrome__find,mcp__claude-in-chrome__form_input,mcp__claude-in-chrome__javascript_tool,mcp__claude-in-chrome__computer

End-to-end workflow

1. Open the page

tabs_context_mcp({ createIfEmpty: true })
navigate({ tabId, url: "https://aistudio.google.com/generate-speech?model=gemini-3.1-flash-tts-preview" })

If the URL shows a banner that the chosen model is unavailable and AI Studio auto-switched to another (e.g. gemini-3.1-flash-tts-preview), accept it — don't fight the redirect. Close the dismiss-banner ("X") with a click before continuing so it doesn't cover Run controls.

2. Pick the mode

The two toggle buttons live at the top right of the playground:

js
// Switch to Composer
document.querySelectorAll('button.toggle-button').forEach(b => {
  if (b.innerText.trim().endsWith('Composer')) b.click();
});
// or for Text
document.querySelectorAll('button.toggle-button').forEach(b => {
  if (b.innerText.trim().endsWith('Text')) b.click();
});

The active toggle has class ms-button-active.

3. Fill the shared fields

Both modes share:

  • Scene (sets the acoustic / situational frame): textarea[aria-label="Scene"]
  • Sample Context (gives the model a tone reference): textarea[aria-label="Sample Context"]

These are Angular textareas. Plain el.value = ... will NOT trigger Angular's form binding — use the helper in references/selectors.md, or prefer the form_input MCP tool with a ref obtained from find.

Leave these fields empty if the user did not provide a scene / sample context. They are optional.

4a. Fill input — Text mode

One textarea: textarea[aria-label="Enter a prompt"].

Format conventions (these are not validated by the UI but are what the model is trained on):

  • Single narrator: just write the text. Optionally prepend an inline tag, e.g. [warm] Welcome to today's episode.
  • Multi-speaker: prefix each line with Speaker 1:, Speaker 2:, …
Speaker 1: [enthusiastic] Welcome back to the show!
Speaker 2: [agreement] Thanks, glad to be here.

See references/audio-tags.md for the inline-tag vocabulary.

4b. Fill input — Composer mode

Composer renders one speech block per utterance. Each block has:

  • A speaker chip: button.voice-chip.ms-button-filter-chip (text reads Speaker N - VoiceName)
  • A textarea: textarea[aria-label="Speech block text"]

To add a new block: click button.add-speech-block-button. The new block inherits the previous speaker by default.

To populate Composer from a script:

  1. Make sure the existing blocks match what you need (delete extras with the per-block × button if necessary).
  2. For each line in the script, ensure a block exists; click "add speech block" to create more.
  3. Set the text of each block (textarea[aria-label="Speech block text"], indexed in DOM order).
  4. Set the speaker chip per block (see Step 5).

5. Choose voices

The right-hand Speaker settings panel shows one card per active speaker (Speaker 1, Speaker 2, …). Clicking a card opens the full voice picker drawer with 32 voices. See references/voices.md for the full catalogue with their character traits.

Inside the voice picker drawer:

  • Audio Profile — free text, e.g. "An authoritative main news anchor."
  • Director's note — three dropdowns: Style (e.g. Vocal Smile), Pace (e.g. Rapid Fire), Accent (e.g. American (Gen)).
  • Voice — searchable list. Click a voice to select it.

Close the drawer by clicking the × in its top-right when done. The active voice card on the playground has class active-voice-card.

In Composer mode each block's voice chip can be changed independently — clicking it opens a popover where you assign that block to Speaker 1, Speaker 2, … or add a new speaker.

6. (Optional) Adjust Temperature

Expand "Model settings" (right panel, above Speaker settings) to reveal Temperature. Range 0–2, default 1. The number input is input.slider-number-input near the label "Temperature". Higher = more variation in delivery. Only touch this if the user asked for it.

7. Run generation

Click button.ctrl-enter-submits (the "Run Ctrl ↵" button at the bottom right), or press Ctrl+Enter while focus is in the prompt area:

js
document.querySelector('button.ctrl-enter-submits').click();

Generation usually takes 5–30 s depending on length. Poll for completion by checking the audio player's duration counter (the right-hand 0:00 / X:XX increments once render is done) or by watching for the download icon to become enabled.

8. Hand off / download

Tell the user the audio is ready and point at the playback controls. Downloading is the user's choice — only click the download (cloud-arrow) icon if the user asked for a file.

Style guidance for prompting

  • Inline tags belong inside the speaker line, e.g. Speaker 1: [whispers] don't tell anyone. They do not stack across lines.
  • Scene is for acoustics + setting, not the script. Bad: "Speaker 1 says hi". Good: "Quiet kitchen, morning light, minimal reverb."
  • Sample Context is for delivery tone, e.g. "Podcast style, fast, slightly overlapping pacing, energetic and warm."
  • For two-host podcasts, Puck (Upbeat / Middle pitch) + Zephyr (Bright / Higher pitch) is the AI Studio default and a safe baseline. See references/voices.md for alternatives.

What NOT to do

  • Don't sign in, accept new ToS, or change account settings — those are off-limits.
  • Don't download generated audio without an explicit user ask.
  • Don't navigate away from the AI Studio tab while a render is in flight.
  • Don't fabricate voice names — the catalogue is fixed at 32 (see references/voices.md). If the user asks for a voice not in the list, suggest the closest match.
  • Don't el.value = "…" on Angular textareas without dispatching input and change events; the form will revert. Use the helper in references/selectors.md or form_input.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Google Ai Studio Tts AI skill do?

Generate speech, podcasts, voiceovers, and multi-speaker dialogue with Google AI Studio's Gemini Flash TTS by driving the live web app in Chrome via the claude-in-chrome MCP server. Use whenever the user asks to (1) create a podcast, audiobook chapter, narration, audio drama, or voiceover with Gemini / Google AI Studio TTS; (2) turn a script into multi-speaker audio (e.g. "two-host podcast", "Speaker 1 / Speaker 2 dialogue", "Puck and Zephyr"); (3) tweak a TTS prompt with Scene, Sample Context, Director's note (Style/Pace/Accent), Audio Profile, voice picker, or Temperature; or (4) render a...

Why use Google Ai Studio Tts on TypingMind?

Because you install it once and use it with any model. Google Ai Studio Tts is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Google Ai Studio Tts in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/maystudios/claude-skills/tree/main/google-ai-studio-tts. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Google Ai Studio Tts?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Google Ai Studio Tts?

As many as you like. As long as a model supports skills, you can use Google Ai Studio Tts with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Google Ai Studio Tts AI skill free?

Yes. It is published on GitHub by maystudios under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇