tts

Synthesize local text-to-speech via configurable multi-backend proxy with fallbacks.

12|2|Updated Feb 2, 2020
One-click install
npx skills add https://github.com/servitola/dotfiles --skill tts-servitola
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tts
Source: https://github.com/servitola/dotfiles/tree/main/claude-code/skills/tts
Command: npx skills add https://github.com/servitola/dotfiles --skill tts-servitola

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill enables local text-to-speech synthesis using a configurable multi-backend proxy, avoiding reliance on external cloud services and enabling offline or tightly controlled playback workflows.

Core Features & Use Cases

  • Multibackend support (Gemini tts, tts-piper, tts-azure) with clear fallback paths.
  • Long-text handling via chunking and concatenation.
  • Russian and multilingual voice support with SSML control.

Quick Start

Synthesize the Russian phrase 'Привет, мир' using the default local tts backend.

Frequently Asked Questions about tts

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I run local text-to-speech synthesis without relying on cloud services?

Local text-to-speech synthesis is achieved by configuring a multi-backend proxy that routes requests to local services, avoiding external cloud dependencies. This enables offline or tightly controlled playback workflows.

Does this text-to-speech proxy support Russian and multilingual voices?

Yes, the text-to-speech proxy supports Russian and multilingual voice synthesis. It provides optional SSML control to manage voice parameters and pronunciation accurately across different languages.

How do I handle long-text chunking for text-to-speech playback?

Long-text chunking for text-to-speech playback is handled automatically by splitting extended text inputs into smaller segments. The proxy synthesizes these chunks individually and concatenates the resulting audio for continuous playback.

What backends can I use for local text-to-speech synthesis?

Available backends for local text-to-speech synthesis include Gemini tts, tts-piper, and tts-azure. The proxy supports clear fallback paths between these backends, requiring explicit voice configuration for each.

Do I need a LiteLLM proxy to use these local text-to-speech backends?

Yes, a running LiteLLM proxy is required to route synthesis requests. You must also have the respective backend services running and provide explicit voice configuration per backend to generate speech successfully.

What happens when a primary text-to-speech backend fails during synthesis?

When a primary text-to-speech backend fails during synthesis, the configurable multi-backend proxy utilizes predefined fallback paths. It automatically routes the request to an alternative configured backend to ensure continuous speech generation.