minutes-video-review
Analyze a product walkthrough, bug report video, Loom, or ScreenPal using Minutes transcription plus visual review
Install / Use
npx skills add silverstein/minutes --skill minutes-video-reviewInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
Development & EngineeringSupported Platforms
Our assessment of minutes-video-review
minutes-video-review scores 86/100 on our quality scale, 2403rd of 4,700 Development & Engineering skills we index.
Its SKILL.md is 5.6 KB long, well organised into 13 sections with 5 code examples: a solid amount of guidance for an agent.
With 1,500 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so minutes-video-review is actively maintained.
- Our last check on 2026-11-03 found the source still online.
- It is released under the MIT license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-01. Automated pattern scan on 2026-10-01. It catches known dangerous patterns, not every risk — read a skill before letting an agent act on it.
minutes-video-review compared with similar skills
All 4 of these similar skills score higher than minutes-video-review; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| minutes-video-review (this skill)by silverstein | 86 | 1.5k | 54d ago | SKILL.md |
| taste-skillby Leonxlnx | 100 | 116.8k | 8d ago | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 8d ago | CLAUDE.md |
| ai-job-searchby ai-job-search-dev | 100 | 72.1k | today | CLAUDE.md |
| claude-howtoby luongnv89 | 100 | 47.3k | 2d ago | CLAUDE.md |
Frequently asked questions
- How do I install minutes-video-review?
- Run
npx skills add silverstein/minutes --skill minutes-video-review. The install tabs above show the steps for each supported agent. - Which AI agents does minutes-video-review work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is minutes-video-review safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is MIT-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is minutes-video-review still maintained?
- The repository was last updated about 2 months ago, so minutes-video-review is actively maintained.
Skill content
View source on GitHubname: minutes-video-review description: Analyze a product walkthrough, bug report video, Loom, or ScreenPal using Minutes transcription plus visual review. Use when the user wants a recorded demo or bug clip turned into a durable brief with transcript, key frames, issues, and next steps. compatibility: opencode
Skill Path
Before running helper scripts or opening bundled references, set:
export MINUTES_SKILLS_ROOT="$(git rev-parse --show-toplevel)/.opencode/skills"
export MINUTES_SKILL_ROOT="$MINUTES_SKILLS_ROOT/minutes-video-review"
/minutes-video-review
Analyze a product walkthrough, bug report video, Loom, ScreenPal, or local recording into a durable artifact bundle that agents can keep working from.
This skill is for meeting-adjacent product artifacts, not for generic "understand any video" requests. Use it when the user wants a recorded demo, bug repro, or walkthrough turned into something actionable for engineering, product, support, or follow-up agent work.
What this skill does
The bundled script handles the deterministic pipeline:
- resolve a local file or hosted video URL
- download hosted video when needed
- extract audio with
ffmpeg - transcribe with Minutes first, using the user's existing Minutes transcription setup
- sample key frames with adaptive caps so long videos do not blow up context
- write a durable artifact bundle under
~/.minutes/video-reviews/
Then you review the resulting artifacts and return the actual user-facing brief.
Primary command
Local file:
python3 "$MINUTES_SKILL_ROOT/scripts/video_review.py" \
"/absolute/path/to/video.mp4"
Hosted video:
python3 "$MINUTES_SKILL_ROOT/scripts/video_review.py" \
"https://go.screenpal.com/watch/..."
Useful options:
python3 "$MINUTES_SKILL_ROOT/scripts/video_review.py" \
"https://www.loom.com/share/..." \
--focus "customer signup bug repro" \
--cookies-from-browser chrome \
--env-file /absolute/path/to/.env \
--frame-step 15 \
--max-frames 36 \
--keep-temp
How to use it
Phase 1: Run the pipeline
Run the script on the provided local file or hosted video URL.
The script prints JSON with the output artifact paths. Important outputs include:
analysis_mdanalysis_jsontranscript_mdmetadata_jsonframes_dircontact_sheet_artifact
Phase 2: Inspect the artifacts
Read the generated analysis.md and analysis.json first.
Then inspect:
transcript.mdfor the actual spoken content- selected images from
frames/when visual state matters contact-sheet.jpgfor a quick visual sweep across sampled framesmetadata.jsonfor transcript method, duration, source kind, and frame sampling details
Phase 3: Produce the real brief
Return a concise, useful brief to the user that includes:
- what the video is trying to show
- likely bug / proposal / walkthrough intent
- key moments or timestamps
- likely impacted area or flow
- the clearest next actions
Do not just echo the generated markdown blindly. Use the artifacts as evidence and produce a thoughtful agent answer.
Minutes-first transcription rules
This skill should prefer transcript backends in this order:
- hosted captions / VTT when the source exposes them
minutes processwith an isolated temporary config- local
whisperCLI if available - OpenAI audio transcription only as a last resort when configured
Important:
- the Minutes path should use the user's current Minutes transcription setup
- if Minutes is configured for Whisper, use Whisper
- if Minutes is configured for Parakeet, use Parakeet
- do not silently fork a separate transcription stack unless the Minutes path is unavailable
When reporting the artifacts back to the user, preserve the transcript method exactly. Prefer labels like:
vtt_captionsminutes-whisperminutes-parakeetminutes-whisper-fallbacklocal_whisper_cliopenai_audio_transcription
Context discipline
This skill must stay disciplined about context size.
- Do not send the full video itself to the reasoning layer.
- Do not dump a long transcript and dozens of frames into the final answer.
- Treat the transcript as the backbone and frames as supporting evidence.
- Prefer inspecting a curated subset of frames instead of every sampled image.
The bundled script already caps frames adaptively, but you should still exercise judgment when deciding what to read or mention.
Output contract
The script writes a durable bundle under:
~/.minutes/video-reviews/<timestamp>-<slug>/
Expected files:
analysis.mdanalysis.jsontranscript.mdmetadata.jsonframes/
These artifacts are not part of the normal ~/meetings/ corpus by default.
Dependencies
See:
$MINUTES_SKILL_ROOT/references/dependencies.md$MINUTES_SKILL_ROOT/references/output-schema.md
Gotchas
- Hosted URLs need
yt-dlp. Local file review still works without it. - Frame caps are intentional. The script samples enough evidence to review the video without turning this into a generic video-intelligence pipeline.
- Minutes artifacts stay isolated. The script uses a temp config/output path for the Minutes transcription run so it does not pollute the user's normal archive.
- Model-powered auto-analysis is optional. The generated
analysis.md/jsonmay be heuristic when no multimodal provider key is available. You still need to read the artifacts and produce the final answer. - Long videos need synthesis, not brute force. If the transcript is long, work from the generated artifacts and only open the most relevant frames and transcript sections.
Related Skills
taste-skill
116.8kAgent skills that give coding agents taste: art direction, reference images and a browser check instead of generic AI pages
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ai-job-search
72.1kThe job search that runs on your machine. AI job application framework built on Claude Code: evaluate postings, tailor CVs, write cover letters, prep interviews. Fork it and own it.
claude-howto
47.3kA visual, example-driven guide to Claude Code — from basic concepts to advanced agents, with copy-paste templates that bring immediate value.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
