agentleFS
Sign inStart free
sonichisonichi/sutando/skills/audio-transcribe/SKILL.md

audio-transcribe

Skill396 starsChanged 6 months agoMITView on GitHub

Transcribes audio files and voice notes to text via Gemini 2.5-flash. Integrates with Slack, Discord, and Telegram bridges so voice clips surface as readable text in tasks.

  • Reads credentials

8 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 0

    Distinctive

    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:

    Fail-open design: Every bridge wraps the call in a helper that returns None on a non-zero exit.

    line 22
  2. Very specific:

    Delete skills/audio-transcribe/ — all three bridges fall back to [File attached:] automatically.

    line 50

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “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

audio-transcribe

Transcribes audio files (voice notes, clips) to text via Gemini 2.5-flash. Used by the Slack, Discord, and Telegram bridges to surface voice-note content in task bodies so the core agent can act on the words instead of a bare file path.

How it works

skills/audio-transcribe/scripts/transcribe.py <audio_file_path>

Reads the file, sends it inline (base64) to the Gemini 2.5-flash generateContent endpoint, and prints the transcript to stdout. Exits 0 on success, 1 on any failure (unsupported format, missing API key, network error, API error).

Fail-open design. Every bridge wraps the call in a helper that returns None on a non-zero exit. A failed transcription never blocks the task — the [File attached: /path] line still goes through so the agent can at least see a file was sent.

Supported formats

.m4a (Slack voice clips), .mp3, .ogg, .oga, .opus, .wav, .webm, .aac, .flac, .mp4

Key resolution order

  1. GEMINI_API_KEY or GOOGLE_API_KEY in the process environment
  2. <workspace>/.env (resolved via resolve_workspace())
  3. $CLAUDE_CONFIG_DIR/channels/slack/.env
  4. $CLAUDE_CONFIG_DIR/channels/discord/.env
  5. $CLAUDE_CONFIG_DIR/channels/telegram/.env

Bridge integration

Each bridge calls _transcribe_via_skill(local_path) after downloading a file. The helper locates the skill script relative to src/ (or the app bundle), runs it, and returns the transcript string or None. The bridge then appends either:

  • [Voice transcript: <text>] — when transcription succeeds
  • [File attached: /path] — when skill is absent or transcription fails

Removing the skill

Delete skills/audio-transcribe/ — all three bridges fall back to [File attached:] automatically. Core services are unaffected.

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.

Check your setup, free