agentleFS
kwana117kwana117/claude-skills/transcribe/SKILL.md

transcribe

Skill0 starsChanged 5 months agoMITView on GitHub

Transcribe audio or video files. Two methods: local Whisper (default, free, runs on your machine), or OpenAI Whisper API (faster, needs OPENAI_API_KEY). Use when the user asks to transcribe audio, video, podcasts, interviews, or any media with speech.

  • Reads credentials
  • Installs packages

47 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use spreadsheet, think and 9 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • JetBrainsSkill

    spreadsheet

    Use when tasks involve creating, editing, analyzing, or formatting spreadsheets (`.xlsx`, `.csv`, `.tsv`) with formula-aware workflows, cached recalculation, and visual review.

    Also in 3 projects that use this

  • vltingSkill

    think

    Lightweight plan-to-execution pipeline. Explores codebase, runs council deliberation, presents plan for approval, then executes via /run.

    Also in 3 projects that use this

  • robzolkosSkill

    done

    Reset the working directory for the next task by ensuring no uncommitted changes exist, then switching to the main branch and pulling latest.

    Also in 3 projects that use this

  • JaimeGBASkill

    ingest

    Digest an external source (article, paper, transcript, URL, book chapter) and integrate its content into the knowledge base

    Also in 3 projects that use this

  • AnthropicSkill

    onboarding

    Generate an onboarding checklist and first-week plan for a new hire. Use when someone has a start date coming up, building the pre-start task list (accounts, equipment, buddy), scheduling Day 1 and Week 1, or setting 30/60/90-day goals for a new team member.

    Also in 3 projects that use this

  • MicrosoftSkill

    diagnose

    Use to systematically diagnose why scenarios fail — identifies root causes by analyzing agent traces, codebase, and behavioral patterns

    Also in 3 projects that use this

The file

Show its rules and text

We split this skill into the rules it gives an agent

16 rules. 0 are common, 6 are distinctive, and 10 are very specific to this project.

  • 0

    Common

    Most of the 40 edited versions we read keep these.

  • 6

    Distinctive

    This author's own choices. Worth a look.

  • 10

    Very specific

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

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

    If method is not specified, default to local.

    line 19
  2. Distinctive:

    If no file path is present after parsing, ask the user for the file path.

    line 25
  3. Distinctive:

    Check the file exists and show basic info:

    line 31
  4. Distinctive:

    If the file doesn't exist, tell the user and stop.

    line 37
  5. Distinctive:

    If the user mentioned the language, use that.

    line 41
  6. Very specific:

    If unsure, ask the user, or use auto to let Whisper detect the language.

    line 47
  7. Very specific:

    Run with timeout up to 600000ms — the large model takes roughly ~4x realtime on CPU.

    line 77
  8. Very specific:

    If you prefer to offload transcription to a more powerful machine, you can run the same steps over SSH.

    line 85
  9. Very specific:

    If ffmpeg or whisper are installed in a non-default location on the remote host, prepend the appropriate directory to PATH inside the SSH …

    line 104
  10. Very specific:

    If you keep it in a secrets manager (e.g.

    line 112
  11. Very specific:

    If OPENAI_API_KEY is not set, ask the user to provide it (or to set it in their secrets manager) before continuing.

    line 118
  12. Distinctive:

    Read the transcript file and show a preview (first ~30 lines)

    line 147
  13. Distinctive:

    Ask if the user wants the full transcript displayed or any post-processing (summary, translation, formatting, etc.)

    line 149
  14. Very specific:

    local: ensure ffmpeg and whisper are on your PATH before running

    line 153
  15. Very specific:

    local: if whisper fails with memory errors on the large model, retry with medium (or small) and warn the user

    line 154
  16. Very specific:

    api: read the key from OPENAI_API_KEY (or from your secrets manager).

    line 157

“Common” is measured: kept by at least 6 in 10 of the 40 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

Transcribe Skill

Transcribes audio/video files using one of two methods:

  • local (default) — OpenAI Whisper running on your machine. Free, slower, great quality for many languages. Can optionally run on a remote host over SSH.
  • api — OpenAI Whisper API (whisper-1). Fast, uses OPENAI_API_KEY.

Input parsing

$ARGUMENTS may contain up to two parts: [filepath] [method]

  • Parse the last word of $ARGUMENTS. If it is local or api, that is the method; the rest is the file path.
  • If method is not specified, default to local.
  • Examples:
    • /transcribe interview.mp3 → file=interview.mp3, method=local
    • /transcribe interview.mp3 api → file=interview.mp3, method=api
    • /transcribe interview.mp3 local → file=interview.mp3, method=local

If no file path is present after parsing, ask the user for the file path.

Supported formats: .mp3, .m4a, .wav, .ogg, .flac, .aac, .wma, .mp4, .mov, .mkv, .webm, .avi

Step 1 — Validate input

Check the file exists and show basic info:

ls -lh "FILEPATH"

If the file doesn't exist, tell the user and stop.

Step 2 — Ask for language (if not obvious)

If the user mentioned the language, use that. Common options:

  • en — English
  • pt — Portuguese
  • es — Spanish
  • auto — auto-detect (mixed languages)

If unsure, ask the user, or use auto to let Whisper detect the language.


Method: local (Whisper on your machine)

By default this runs locally. It can optionally run on a remote host over SSH (see "Running on a remote host" below).

Prerequisites:

  • OpenAI Whisper installed: pip install -U openai-whisper (verify with python3 -m whisper --help)
  • FFmpeg installed and on your PATH (e.g. brew install ffmpeg on macOS, or your distro's package manager)

The first run of a model will download its weights. The large model gives the best quality; use medium/small/base for less memory or faster runs.

Step 3.5L — Convert to WAV

Whisper works best with WAV input. Always convert:

ffmpeg -i "FILEPATH" -ar 16000 -ac 1 -c:a pcm_s16le "FILEPATH_WITHOUT_EXT.wav" -y

Step 4L — Transcribe

python3 -m whisper "FILEPATH_WITHOUT_EXT.wav" --model large --language LANG --output_dir "LOCAL_OUTPUT_DIR" --output_format txt

For auto language detection, omit the --language flag.

Run with timeout up to 600000ms — the large model takes roughly ~4x realtime on CPU.

Step 5L — Locate transcript

The transcript is written to LOCAL_OUTPUT_DIR/FILENAME_WITHOUT_EXT.txt. Place it in the same directory as the original file.

Running on a remote host (optional)

If you prefer to offload transcription to a more powerful machine, you can run the same steps over SSH. Replace <your-remote-host> with your SSH host (as configured in ~/.ssh/config or user@hostname):

# 1. Send the file
scp "FILEPATH" <your-remote-host>:/tmp/

# 2. Convert to WAV on the remote host
ssh <your-remote-host> "ffmpeg -i '/tmp/FILENAME' -ar 16000 -ac 1 -c:a pcm_s16le '/tmp/FILENAME_WITHOUT_EXT.wav' -y"

# 3. Transcribe on the remote host
ssh <your-remote-host> "python3 -m whisper '/tmp/FILENAME_WITHOUT_EXT.wav' --model large --language LANG --output_dir /tmp/ --output_format txt"

# 4. Retrieve the transcript
scp <your-remote-host>:/tmp/FILENAME_WITHOUT_EXT.txt "LOCAL_OUTPUT_DIR/"

# 5. Clean up the remote host
ssh <your-remote-host> "rm -f '/tmp/FILENAME' '/tmp/FILENAME_WITHOUT_EXT.wav' '/tmp/FILENAME_WITHOUT_EXT.txt'"

If ffmpeg or whisper are installed in a non-default location on the remote host, prepend the appropriate directory to PATH inside the SSH command (e.g. export PATH=/path/to/bin:$PATH && ...).


Method: api (OpenAI Whisper API)

Prerequisites:

  • An OpenAI API key available in the OPENAI_API_KEY environment variable.
  • If you keep it in a secrets manager (e.g. a password manager, pass, your OS keychain, a .env file), read it from there and export it before running:
export OPENAI_API_KEY="sk-..."   # or load it from your secrets manager

If OPENAI_API_KEY is not set, ask the user to provide it (or to set it in their secrets manager) before continuing. Never hard-code or print the key.

Step 3A — Call Whisper API

The file must be ≤ 25MB. If larger, warn the user and suggest splitting or using the local method instead.

curl -s https://api.openai.com/v1/audio/transcriptions \
  -H "Authorization: Bearer $OPENAI_API_KEY" \
  -F file="@FILEPATH" \
  -F model="whisper-1" \
  -F language="LANG" \
  -F response_format="text"

For auto language detection, omit the -F language parameter.

Step 4A — Save transcript

Save the API response (plain text) to a .txt file alongside the original:

FILEPATH_WITHOUT_EXT.txt

Step 7 — Show result (both methods)

  1. Read the transcript file and show a preview (first ~30 lines)
  2. Report: file path of the saved transcript, approximate word count, method used
  3. Ask if the user wants the full transcript displayed or any post-processing (summary, translation, formatting, etc.)

Notes

  • local: ensure ffmpeg and whisper are on your PATH before running
  • local: if whisper fails with memory errors on the large model, retry with medium (or small) and warn the user
  • local: for very large files (> 500MB) sent to a remote host, warn the user that the SCP transfer may take a while
  • api: 25MB limit — suggest local for larger files
  • api: read the key from OPENAI_API_KEY (or from your secrets manager); never expose it in logs or responses

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.