video-analysis
Skill1 starsChanged 3 months agoMITView on GitHub
Analyze local video or audio files with ffmpeg/ffprobe, Parakeet MLX or Whisper transcription, contact sheets, checkpoint frames, and timestamped issue notes. Use ONLY when the user explicitly invokes this skill by name. Never trigger it automatically.
8 other projects use a version of this.
Adopted by
Most recently taken up by
- thatjuan/agent-skillstheir own version, first seen Nov 8, 2026
- SalZaki/video-analysis-workbenchtheir own version, first seen Oct 20, 2026
- ilamanov/skillstheir own version, first seen Oct 13, 2026
- ericosiu/ai-marketing-skillstheir own version, first seen Sep 2, 2026
- felvieira/claude-skills-fvtheir own version, first seen Sep 2, 2026
- sonilo-ai/skillstheir own version, first seen Aug 16, 2026
Other versions8 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 8
- ericosiu/ai-marketing-skills★ 3.8ksame name
- sonilo-ai/skills★ 117same name
- Starchild-ai-agent/official-skills★ 32same name
- felvieira/claude-skills-fv★ 27same name
- ilamanov/skills★ 1same name
- thatjuan/agent-skills★ 1same name
- kwana117/claude-skills★ 0same name
- SalZaki/video-analysis-workbench★ 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 repository13 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ask-claudeSkill
- battery-statsSkill
- coding-audit-assumptionsSkill
- coding-consult-designSkill
- coding-explain-problemSkill
- handoffSkill
- ntd-tasksSkill
- one-by-oneSkill
- record-macos-windowSkill
- show-meSkill
- tallySkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 3 are distinctive, and 3 are very specific to this project.
0
Common
Most of the 7 edited versions we read keep these.
3
Distinctive
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Run the bundled orchestrator (paths are relative to this skill directory):
- Very specific: line 22
If the skill lives in a different location, adjust the script path accordingly (e.g.
- Distinctive: line 49
Create broad evidence every 5 seconds and a focused window from 75s to 110s:
- Very specific: line 80
Read references/output-format.md before writing the final analysis.
- Very specific: line 84
Use timestamps like [00:01:27.520].
- Distinctive: line 87
Prefer a few high-confidence issues over speculative commentary.
“Common” is measured: kept by at least 6 in 10 of the 7 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
Video Analysis
Analyze a local media file pragmatically: capture metadata, transcribe speech, generate visual checkpoints, then produce timestamped notes that tie observations to evidence.
Quick Start
Run the bundled orchestrator (paths are relative to this skill directory):
python3 scripts/analyze-video.py \
--input "/absolute/path/to/recording.mov" \
--output-dir ".agent-data/video-analysis/recording"If the skill lives in a different location, adjust the script path accordingly (e.g. python3 path/to/video-analysis/scripts/analyze-video.py ...).
Workflow
- Inspect media metadata with
ffprobebefore assuming duration, streams, or frame rate. - Extract normalized mono 16 kHz audio with
ffmpegwhen an audio stream exists. - Transcribe with Parakeet MLX first. Fall back to Whisper when Parakeet is unavailable.
- Generate a broad contact sheet at a practical interval, usually 5-10 seconds.
- Generate focused 1-second frames around suspicious windows when the transcript or user report points to a timestamp.
- Review transcript and frames together. Write facts first, then hypotheses.
- Produce timestamped issue notes with exact evidence paths.
Output Artifacts
The script writes artifacts under the chosen output directory:
metadata.jsonandmetadata.md: raw and readable media metadata.audio.wav: normalized extracted audio when the input has audio.transcript.srt,transcript.vtt,transcript.txt,transcript.json: transcription outputs when a transcription engine is available.transcript.md: compact timestamped transcript for agent review.frames/: sampled frames and checkpoint frames.contact-sheet.jpg: broad visual contact sheet.focus-*/contact-sheet.jpg: focused visual contact sheets for specific time windows.issue-notes.md: scaffold for the final timestamped analysis.
Common Commands
Create broad evidence every 5 seconds and a focused window from 75s to 110s:
python3 scripts/analyze-video.py \
--input "/path/to/recording.mov" \
--sample-interval 5 \
--focus-window "75,110"Extract exact checkpoint frames without doing transcription:
python3 scripts/analyze-video.py \
--input "/path/to/recording.mov" \
--timestamps "00:01:25" "00:01:33.5" \
--no-transcriptLimit frame volume for long recordings:
python3 scripts/analyze-video.py \
--input "/path/to/long-demo.mp4" \
--sample-interval 15 \
--max-contact-frames 48Review Guidance
The primary deliverable is issue-notes.md in the output directory. Fill in the timeline and findings sections of the scaffold the script wrote, using the format from references/output-format.md. The chat reply should be a short TL;DR plus a pointer to the file, not the full analysis - the file is the artifact the user keeps and re-reads.
Read references/output-format.md before writing the final analysis. Read references/tooling.md when a tool is missing or transcription fails. Read references/video-review-rubric.md when deciding what to inspect in UX or bug-report recordings.
When reporting findings:
- Use timestamps like
[00:01:27.520]. - Link each finding to transcript text, frame files, or contact sheets.
- Distinguish observed behavior from inferred root cause.
- Prefer a few high-confidence issues over speculative commentary.
- Preserve user language from the transcript when it explains confusion or intent.
Tooling Notes
The script expects ffmpeg and ffprobe on PATH. It tries Parakeet MLX via either parakeet-mlx or uv run --with parakeet-mlx parakeet-mlx. Whisper fallback supports whisper, uvx --from openai-whisper whisper, and whisper-cli when a local whisper.cpp model is discoverable or WHISPER_CPP_MODEL is set.
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.

