transcribe-video
Skill1 starsChanged 5 months agoMITView on GitHub
Transcribe a video or audio file to a plain-text .txt file. Use when the user says "transcribe this", "make a transcript", "get the text from this video", "what was said in this", or any variant of "give me the transcription". Fast (hardware decode + whisper) — runs in seconds on M-series Macs.
- Installs packages
4 other projects use a version of this.
Adopted by
Most recently taken up by
- CharlesLadera/claude-custom-skillstheir own version, first seen Oct 25, 2026
- AlemTuzlak/skillstheir own version, first seen Aug 3, 2026
- feiskyer/video-skillstheir own version, first seen Apr 15, 2026
- rameerez/claude-code-startup-skillstheir own version, first seen Feb 4, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- AlemTuzlak/skills★ 45same name
- rameerez/claude-code-startup-skills★ 30same name
- feiskyer/video-skills★ 14same name
- CharlesLadera/claude-custom-skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository2 other files it gives its agents.
- redashSkill
- thumbnail-videoSkill
The file
We split this skill into the rules it gives an agent
8 rules. 0 are common, 3 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Before running any commands, verify both dependencies are installed:
- Distinctive: line 19
If missing, guide the user:
- Very specific: line 62
If the source is already audio (.wav, .mp3, .m4a, .flac), still run this — it normalizes the format and gives whisper a clean input.
- Very specific: line 85
If the user asked for timestamps, use --output_format all to emit every format (.txt, .srt, .vtt, .json, .tsv).
- Very specific: line 86
If the user asked for a specific format only (e.g.
- Very specific: line 94
Don't auto-open the file — it's plain text, the user can cat or open it themselves.
- Very specific: line 105
Don't write the txt to
./tmpand stop: Always deliver alongside the source file so the user can find it. - Distinctive: line 108
Keep this skill focused on one thing: produce a plain-text transcript from a media file, fast.
“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.
Files
Transcribe Video
Produce a plain-text transcript of a video or audio file. Outputs a .txt next to the source. Optional: also emit .srt/.vtt/.json if the user asks for timestamps.
Prerequisites
Before running any commands, verify both dependencies are installed:
command -v ffmpeg >/dev/null || { echo "ffmpeg not found"; exit 1; }
command -v whisper >/dev/null || { echo "whisper not found"; exit 1; }If missing, guide the user:
- ffmpeg:
brew install ffmpeg(macOS) /sudo apt install ffmpeg(Ubuntu/Debian) - whisper:
pip install openai-whisper
Inputs
- Media file path (the user will provide; otherwise ask). Video or audio.
- Optional:
--modeloverride. Defaulttiny.enfor English,baseotherwise. - Optional:
--language(auto-detect if omitted; non-English forces a non-.enmodel). - Optional:
--with-timestampsto also emit.srt(segment-level) alongside the.txt.
Working directory
./tmp/<basename>/ — mkdir at start, leave artifacts for debugging.
Step 1 — Extract audio
Whisper only needs mono 16 kHz audio. Hardware-decode the source to skip a slow HEVC software pass.
macOS (Apple Silicon):
ffmpeg -y -hwaccel videotoolbox -i "$SRC" \
-vn -ac 1 -ar 16000 \
./tmp/$NAME/audio.wavLinux / other platforms:
ffmpeg -y -i "$SRC" \
-vn -ac 1 -ar 16000 \
./tmp/$NAME/audio.wavTo detect the platform: [[ "$(uname)" == "Darwin" ]] && HWACCEL="-hwaccel videotoolbox" || HWACCEL=""
Critical flags:
-hwaccel videotoolbox(macOS only) — hardware-decodes HEVC/H.264, ~5–10× faster on Apple Silicon. Omit on Linux/Windows.-vn— skip the video stream entirely; we only need audio.-ac 1 -ar 16000— mono 16 kHz is what whisper resamples to anyway; doing it in ffmpeg is faster than letting whisper do it.
If the source is already audio (.wav, .mp3, .m4a, .flac), still run this — it normalizes the format and gives whisper a clean input.
Step 2 — Transcribe with whisper
whisper ./tmp/$NAME/audio.wav \
--model tiny.en \
--output_format txt \
--output_dir ./tmp/$NAME \
--language enModel picker:
tiny.en— default for English. Fastest, quality fine for clear speech (tutorials, podcasts, voice-overs).base.en— bump up iftiny.enproduces noticeable errors (proper nouns, technical terms).small.en/medium.en— only if the user explicitly asks for higher accuracy and accepts longer wait.turbo— best quality-to-speed ratio for any language. Use whentiny.enquality isn't good enough but the user hasn't asked for a specific model.base(no.en) — non-English or mixed-language. Drop--language en.
Output format picker:
- Plain
.txtis the default — just the spoken words, one paragraph per whisper segment, no timestamps. This is what most users want. - If the user asked for timestamps, use
--output_format allto emit every format (.txt,.srt,.vtt,.json,.tsv). The user gets their.txtplus whichever timestamp format they need. - If the user asked for a specific format only (e.g. just
.srt), use--output_format srt.
Whisper writes audio.txt (and audio.srt/audio.vtt/audio.json if requested) into --output_dir.
Step 3 — Deliver
- Copy
audio.txtto<source_dir>/<source_basename>.txt(and.srt/.vttif produced). - Print one line: source path → output path, word count, runtime.
- Don't auto-open the file — it's plain text, the user can
cator open it themselves. Just report the path.
Pitfalls — don't repeat these
- Don't use
-hwaccel videotoolboxon Linux. It's macOS-only. Checkunamefirst. - Don't skip
-hwaccel videotoolboxon macOS. Software HEVC decode on a 4K source takes minutes; with the flag, seconds. - Don't feed whisper the raw video file. It works, but ffmpeg's resampling step is much faster than whisper's internal one — and you'd lose
-hwaccel. Always extractaudio.wavfirst. - Don't default to
small.enor larger.tiny.enis fine for English voice-overs, tutorials, podcasts. Only escalate if the user reports errors or asks for better quality. - Don't pass
--word_timestamps Trueunless the user asked for word-level timing. It roughly doubles whisper's runtime. - Don't write the txt to
./tmpand stop. Always deliver alongside the source file so the user can find it. - Don't strip whisper's paragraph breaks. The default
.txtoutput already segments sensibly — leave it alone unless the user asks for a single blob.
Keep this skill focused on one thing: produce a plain-text transcript from a media file, fast.
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
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.

