agentleFS
gyujeongiongyujeongion/claude-life-agent/skills/stt/SKILL.md

stt

Skill2 starsChanged 4 months agoMITView on GitHub

Transcribe an audio file to text (speech-to-text). Use when the user types "stt" or attaches an audio file (mp3, m4a, wav, flac, aac, ogg, opus, webm, mp4) and asks to "transcribe", "turn this into text", "write this up", or "pull the audio". Uses Deepgram (nova-2) with speaker diarization on by default. Pairs with the `add` skill to file the result.

  • Reads credentials
  • Installs packages

3 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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. Distinctive:

    If none was given: *"What's the path to the audio file?"* Handle multiple files in turn.

    line 28
  2. Very specific:

    Default Korean (ko) unless the filename/context says otherwise (change the default in your fork).

    line 34
  3. Very specific:

    If the audio was notes/a meeting/a memo worth keeping, hand the transcript to the add skill to route it into the workspace.

    line 54

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

stt — speech to text

Transcribes audio with Deepgram, speaker-labelled, and saves a .txt next to the source.

Setup (once)

Needs a Deepgram API key (generous free tier). Put it in your environment — never in a file the agent might commit:

echo 'export DEEPGRAM_API_KEY="your-key"' >> ~/.zshrc && source ~/.zshrc

pip install requests if you don't have it.

Step 1 — get the file path

If none was given: "What's the path to the audio file?" Handle multiple files in turn.

Supported: .mp3 .m4a .wav .flac .aac .mp4 .ogg .webm .opus

Step 2 — language

Default Korean (ko) unless the filename/context says otherwise (change the default in your fork). If unclear, ask briefly.

Step 3 — run

python3 ~/.claude/skills/stt/transcribe.py "<path>" --lang <code>

Options: --lang en (or ko, es, …) · --no-diarize (single speaker, faster) · --model nova-2.

Quote paths that contain spaces.

Step 4 — output

Print the transcript to the conversation. It's also saved as <path>.txt.

Step 5 — file it (optional)

If the audio was notes/a meeting/a memo worth keeping, hand the transcript to the add skill to route it into the workspace. Remember add's rule: cross-check transcribed names against people.md — STT mangles proper nouns.

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.