video-digest
Skill0 starsChanged 4 months agoMITView on GitHub
Fetch a video's transcript via the Supadata API and deliver a digest - summary, key points, action items - plus 3 personalized follow-up questions drawn from the user's memory files. Use this skill whenever the user shares a video URL (YouTube, TikTok, Instagram Reel, X/Twitter, Facebook, or a direct video/audio file link) and wants to know what it says, get a summary, extract takeaways or action items, or asks things like "summarize this video", "what's this video about", "get the transcript of", "pull the key points from this talk", or pastes a video link with minimal context. Also use it when the user asks to transcribe any video or audio URL, even without asking for a summary.
- Reads credentials
4 other projects use a version of this.
Adopted by
Most recently taken up by
- RobBrautigam/video-digesttheir own version, first seen Nov 8, 2026
- bonniegeng-max/video-digesttheir own version, first seen Oct 27, 2026
- cycleuser/Skillstheir own version, first seen Oct 25, 2026
- legenxxx/video-digesttheir own version, first seen Jul 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
- cycleuser/Skills★ 13same name
- bonniegeng-max/video-digest★ 1same name
- legenxxx/video-digest★ 1same name
- RobBrautigam/video-digest★ 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.
The file
We split this skill into the rules it gives an agent
7 rules. 0 are common, 5 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
5
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Run the bundled script (handles auth, async job polling for videos over ~20 minutes, and error mapping):
- Very specific: line 27
Read transcript.txt afterward.
- Distinctive: line 29
If the script errors, report the plain-language cause (missing key, restricted video, no transcript available) and suggest the fix.
- Very specific: line 56
Memory files: Check what's available in this session: a memory directory or memory tool, CLAUDE.md / user context files, or files like …
- Distinctive: line 58
Fallback: If neither yields anything, ask three natural next questions about the video's topic - the questions a curious viewer would ask …
- Distinctive: line 67
If the user gives multiple URLs, digest each separately in one response, with one combined "Your turn" section at the end.
- Distinctive: line 68
If the user only asks for the raw transcript, run step 1, share the transcript file, and skip the digest - but offer it.
“Common” is measured: kept by at least 6 in 10 of the 3 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 Digest
Turn any public video URL into a transcript-backed digest: summary, key points, action items, and three follow-up questions personalized to the user.
Requirements
SUPADATA_API_KEYenvironment variable (from https://dash.supadata.ai/organizations/api-key). If it's missing, the script exits with a clear message - relay it to the user and stop; don't guess at the video's content.- Supported sources: YouTube, TikTok, Instagram, X (Twitter), Facebook, and public file URLs (MP4, MP3, WAV, etc., up to 1 GB). Only publicly accessible videos work - private, paywalled, age-restricted, or login-required videos return 403/404.
Workflow
1. Fetch the transcript
Run the bundled script (handles auth, async job polling for videos over ~20 minutes, and error mapping):
python scripts/get_transcript.py "<VIDEO_URL>" --out transcript.txtOptional flags: --lang en (preferred transcript language), --mode native (existing captions only - cheaper, no AI generation) or --mode generate (force AI transcription). Default auto tries native first.
Read transcript.txt afterward. For very long transcripts (>50k chars), read in chunks and build the summary incrementally. Long videos process asynchronously - the script polls and this can take a minute or two; that's normal.
If the script errors, report the plain-language cause (missing key, restricted video, no transcript available) and suggest the fix. Don't summarize a video you couldn't transcribe.
2. Write the digest
Deliver in chat, in this shape:
## <Video title or topic, inferred from transcript>
**Summary** - 2-4 paragraphs capturing the core argument or narrative, in the
speaker's framing. Prose, not bullets.
**Key points** - 4-7 bullets, each a substantive claim or insight from the
video (not chapter titles). Include specific numbers, names, or examples the
speaker used.
**Action items** - concrete things a viewer could do based on the video's
content. If the video isn't instructional, extract implications instead
("worth watching X", "reconsider Y"). Skip filler - 2-5 items.Ground everything in the transcript. Don't pad with knowledge the video didn't cover, and don't soften or reinterpret claims the speaker made - the user wants to know what this video says.
3. Ask 3 personalized questions
End with three questions connecting the video to the user. Personalization source, in order:
- Memory files. Check what's available in this session: a memory directory or memory tool,
CLAUDE.md/ user context files, or files likeMEMORY.md,memories/*.mdin the working or home directory. Read whatever exists and look for the user's projects, role, goals, and interests. - Conversation context. Anything the user has said this session about their work or aims.
- Fallback. If neither yields anything, ask three natural next questions about the video's topic - the questions a curious viewer would ask after watching (deeper dives, counterpoints, practical application).
Good personalized questions bridge the video to the user's actual situation: "The speaker recommends X for early-stage teams - would that fit the pipeline you're building at <their project>?" Bad ones just restate the video or bolt the user's name onto a generic question. If memory gives you only partial context, blend: one or two personalized, the rest topic-driven.
Present the questions as a short numbered list under a "Your turn" heading, and invite the user to answer any of them or ask their own.
Notes
- One native transcript = 1 credit; AI-generated = 2 credits/minute. Prefer
automode unless the user asks otherwise. - If the user gives multiple URLs, digest each separately in one response, with one combined "Your turn" section at the end.
- If the user only asks for the raw transcript, run step 1, share the transcript file, and skip the digest - but offer it.
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.

