transcribe-video
Skill14 starsChanged 7 months agoMITView on GitHub
Extract transcript or subtitles from a local video file. Use this skill whenever the user asks to transcribe a video, extract speech-to-text, get subtitles, or wants a text version of what's said in a video. Also trigger on "提取字幕", "视频转文字", "语音转文字", "transcribe", "extract audio text", or when the user references getting a script/transcript from any video file (mp4, mkv, mov, avi, webm). This skill is for LOCAL video files — for YouTube or other online URLs, use the download-video skill first to get the file, then transcribe it.
- Reads credentials
- 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
- smitmartijn/claude-skillstheir own version, first seen Jun 20, 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
- CharlesLadera/claude-custom-skills★ 1same name
- smitmartijn/claude-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.
- download-videoSkill
- narrate-videoSkill
The file
We split this skill into the rules it gives an agent
10 rules. 0 are common, 6 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
6
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
If subtitle streams exist → go to Step 3a (extract embedded subtitles)
- Distinctive: line 21
If no subtitle streams → go to Step 3b (API transcription)
- Distinctive: line 25
If multiple subtitle tracks exist, prefer the one matching the video's primary language or ask the user which track to use.
- Distinctive: line 32
After extraction, convert SRT to clean text:
- Very specific: line 34
Remove timestamp lines (lines matching \d{2}:\d{2}:\d{2})
- Very specific: line 35
Remove HTML-like tags (<i>, </i>, etc.)
- Very specific: line 42
Use the bundled transcription script.
- Distinctive: line 46
Verify the env file exists:
- Very specific: line 51
If MISSING, tell the user to create ~/.transcribe_video.env with:
- Distinctive: line 59
Wait for the user to confirm before proceeding.
“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
Extract transcript text from a local video file. The skill checks for embedded subtitles first (faster and more accurate), and only falls back to API-based speech recognition if none are found.
Step 1: Identify the video file
Confirm the video file path with the user. Supported formats: mp4, mkv, mov, avi, webm, and any format ffmpeg can handle.
Step 2: Check for embedded subtitles
ffprobe -v quiet -select_streams s -show_entries stream=index,codec_name:stream_tags=language,title -of json "<video_path>"- If subtitle streams exist → go to Step 3a (extract embedded subtitles)
- If no subtitle streams → go to Step 3b (API transcription)
Step 3a: Extract embedded subtitles
If multiple subtitle tracks exist, prefer the one matching the video's primary language or ask the user which track to use.
# Extract as SRT (stream index 0 for first subtitle track; adjust if needed)
ffmpeg -i "<video_path>" -map 0:s:0 -c:s srt "<output_path>.srt" -yAfter extraction, convert SRT to clean text:
- Remove sequence numbers
- Remove timestamp lines (lines matching
\d{2}:\d{2}:\d{2}) - Remove HTML-like tags (
<i>,</i>, etc.) - Join remaining non-empty lines
Save the clean transcript to <video_name>.txt next to the video file. Done — skip Step 3b.
Step 3b: API-based transcription
Use the bundled transcription script. It reads credentials from ~/.transcribe_video.env.
Prerequisites check
- Verify the env file exists:
test -f ~/.transcribe_video.env && echo "OK" || echo "MISSING" - If MISSING, tell the user to create
~/.transcribe_video.envwith:
Wait for the user to confirm before proceeding.OPENAI_API_KEY=your-key-here # Optional Base URL: # OPENAI_API_BASE=https://<base-url>/v1/ # Optional Model Name: # TRANSCRIBE_MODEL=gpt-4o-transcribe - Verify dependencies:
If missing:python3 -c "from openai import OpenAI; from dotenv import load_dotenv; print('OK')" 2>&1pip install openai python-dotenv
Run transcription
python3 <skill_directory>/scripts/transcribe.py "<video_path>"The script extracts audio (WAV, 16kHz mono), sends it to the API, and saves the transcript to <video_name>.txt next to the video file.
Step 4: Report results
Tell the user:
- Where the transcript file was saved
- How many lines / approximate word count
- Whether it came from embedded subtitles or API transcription
- Display the first few lines as a preview
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.

