analyze-video
Skill1 starsChanged 3 months agoMITView on GitHub
Turn a video or audio source into timestamped markdown. Use when given a video or audio URL or file to read, analyze, or cite. Acquisition only; it does not analyze and does not write to the notes.
- Installs packages
7 other projects use a version of this.
Adopted by
Most recently taken up by
- evillollive/Analyze-Video-Skilltheir own version, first seen Nov 11, 2026
- tim-osterhus/video-analysis-kittheir own version, first seen Oct 20, 2026
- barefootford/buttercuttheir own version, first seen Sep 14, 2026
- novoads/agent-skillstheir own version, first seen Aug 8, 2026
- mrdainami/omni-video-directortheir own version, first seen Jul 9, 2026
- flintfromthebasement/skillstheir own version, first seen Jul 6, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 7
- barefootford/buttercut★ 625same name
- novoads/agent-skills★ 30same name
- mrdainami/omni-video-director★ 16same name
- evillollive/Analyze-Video-Skill★ 4same name
- flintfromthebasement/skills★ 1same name
- breethomas/bette-os★ 0same name
- tim-osterhus/video-analysis-kit★ 0same 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 repository12 other files it gives its agents.
- AGENTS.mdAGENTS.md
- add-sourceSkill
- archive-projectSkill
- clean-projectSkill
- code-standardsSkill
- global-heartbeatSkill
- map-projectSkill
- notes-heartbeatSkill
- researchSkill
- resolve-projectSkill
- sleepSkill
- test-projectSkill
The file
Files
analyze-video
Video and audio into text a model can cite. Timestamps survive as [MM:SS] so a claim built on this has a real locator.
~/Utils/browser/.venv/bin/python \
$VAULT/.claude/skills/analyze-video/scripts/transcribe.py <url-or-path>Writes to stdout. Redirect it, or land the path per $VAULT/.agent-instructions/add-source.md.
Want the whole video rather than its text? ~/Utils/browser/to-video.py wraps this with metadata, top comments, and described keyframes, landing one finished file in sources/. This skill is the transcript on its own.
Reading the keyframes
to-video.py cuts the runtime into 8 equal bins, finds the 8 most-different frames in each, and keeps the midpoint after each one rather than the cut itself, leaving a <!-- frame:NNN --> marker per frame and printing a manifest with every frame's n, at, bucket, and path.
That midpoint is the whole point, and it caps the run at 64 frames. A cut lands on the transition: a blur, a half-drawn slide, a page mid-scroll. The midpoint after it lands in the shot once it has settled. On the test video the cut at 00:28 was body text scrolling past and the midpoint at 00:33 was the paper's full architecture diagram, so keeping both would have paid twice to read the same moment and gotten the worse frame for free.
A bin yields fewer than 8 when it is a static stretch with too few scene changes to separate: the same video gives [3, 3, 4, 8, 8, 7, 8, 8], so 49 frames rather than the 64 ceiling.
Dispatch one haiku - low agent per bin, all 8 in a single message. Describing what is visibly in a frame is mechanical, which is haiku's tier; nothing here needs a model that reasons. Give each agent only its bin's frames and one instruction: say what is visible, never what the video means.
Each agent writes frames.<bin>.json and returns only that path. Asked for the JSON as its final text, an agent wraps it in a fence or opens with preamble often enough that merging becomes hand-work, and the readings cross context twice for nothing.
~/Utils/browser/to-video.py <the.md> --annotate frames.json--annotate names any frame still undescribed, so a partial pass is visible rather than silent. --buckets 0 skips frames entirely when a talking-head video has nothing to look at.
The descriptions are additive and labelled as a model's. Transcript, description, and comments stay verbatim.
The interpreter, and what is still borrowed
~/Utils/browser/.venv is the converter venv and now holds youtube-transcript-api and yt-dlp, so the captions route and every yt-dlp call run on a venv this directory owns.
faster-whisper is not in it, so the whisper route still reaches for $PROJECTS/briefing/.venv, and archiving or rebuilding that project takes the route down with an error that reads as a missing interpreter rather than a missing package. archive-project sweeps $VAULT/.claude/skills/ for exactly this. The fix is one command:
~/Utils/browser/.venv/bin/pip install faster-whisperUntil then: any YouTube video with captions works from the owned venv, and anything needing whisper does not.
Two routes
| Input | Route | Cost |
| YouTube URL with captions | captions API, no download | a second, free |
| YouTube without captions, any other URL | yt-dlp audio pull, then whisper | minutes, local CPU |
| Local file | whisper | minutes, local CPU |
The YouTube regex covers watch?v=, youtu.be/, and /shorts/. A captions failure (none published, private video, API shape change) falls through to the download route rather than returning empty.
Discovery is a separate job
This skill transcribes one thing you already chose. Finding candidates is search.py video, which returns IDs, channels, view counts, and lengths with no browser involved:
python3 ~/Utils/browser/search.py video "<terms>" -n 20research uses that pairing: discover cheaply across many videos, transcribe only the few worth reading.
Boundaries
- Acquisition only. It does not judge the source, extract claims, or touch the notes.
add-sourcefiles its output and cites it. - Captions are not a transcript. Auto-generated captions carry no punctuation and mangle proper nouns. Quote them as evidence, but expect names and numbers to need a second look.
- A whisper run on a long video is slow. Say so before starting one rather than going quiet for ten minutes.
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.

