agentleFS
lordmaculordmacu/nexo-rs/skills/msedge-tts/SKILL.md

Microsoft Edge TTS

Skill8 starsChanged 7 months agoApache-2.0View on GitHub

Synthesize text to speech using Microsoft Edge Read Aloud voices (no API key).

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use this skill to convert text into spoken audio.

    line 11
  2. Very specific:

    Default output dir: $TMPDIR/agent-msedge-tts/speech-<timestamp>.mp3.

    line 37

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Microsoft Edge TTS

Use this skill to convert text into spoken audio. Backed by the msedge-tts extension which uses the free Microsoft Edge Read Aloud backend via the msedge_tts crate — no API key required.

Use when

  • "Read this aloud" / "say this out loud"
  • "Generate audio from this text"
  • "Make a voice note that says ..."
  • User wants an MP3/WAV of spoken text

Do not use when

  • Speech-to-text (transcription) — use openai-whisper
  • Real-time streaming TTS with low latency — this writes a file after full synthesis
  • Cloned / custom voices — only the public Edge voice catalog is available

Tools

  • status — returns defaults (voice, audio format, output dir)
  • list_voices — list Edge voices; supports query substring filter and limit
  • synthesize — write an audio file from text; optional voice, audio_format, rate, pitch, volume, output_path

Default voice: en-US-EmmaMultilingualNeural. Default format: audio-24khz-48kbitrate-mono-mp3. Default output dir: $TMPDIR/agent-msedge-tts/speech-<timestamp>.mp3.

Typical flow

  1. list_voices with a language query (e.g. "es-", "en-US", "multilingual") to pick a voice.
  2. synthesize with text and the chosen voice. Grab output_path from the response to send or play the audio.

Notes

  • rate, pitch, volume are provider-native integer adjustments (0 = neutral).
  • File extension is inferred from audio_format (mp3 / wav / webm / ogg / opus / amr).
  • Empty text is rejected.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.