watch
Skill1 starsChanged 56 days agoMITView on GitHub
Watch and analyze any YouTube video by fetching its transcript, then summarizing it, extracting key takeaways, pulling quotes, building timestamped chapter notes, listing action items, or answering a specific question about it. Use this whenever the user shares a YouTube link (youtube.com or youtu.be) and wants to know what's in it, says "watch this", "summarize this video", "give me the key points / notes / takeaways from this talk", "what does this video say about X", "tldr this YouTube video", or wants to skip watching something and get the content fast. Trigger even when the user just pastes a YouTube URL with a brief instruction, and even if they never say the word "watch".
- Installs packages
48 other projects use a version of this.
Adopted by
Most recently taken up by
- athina-ai/goose-skillstheir own version, first seen Nov 9, 2026
- chrisconviviera/conviviera-claude-plugintheir own version, first seen Nov 8, 2026
- Conviviera/conviviera-claude-plugintheir own version, first seen Nov 8, 2026
- blauwtje/exotheir own version, first seen Nov 8, 2026
- leolou0512/claude-skillstheir own version, first seen Nov 8, 2026
- inematds/claude-videotheir own version, first seen Nov 8, 2026
Used with
Projects with it also use decision-map, map and 6 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
Mathews-TomSkilldecision-map
Use when mapping unresolved architecture, policy, or scope decisions before planning, or working one decision ticket, including a prototype ticket whose throwaway evidence the prototype package builds. Also applies to "map the decisions", "decision map", and "wayfinder". Not for implementation slices of a known feature, milestone plans, general UI generation, standalone prototypes outside a decision map (use prototype), or adopting experimental code into production.
Also in 3 projects that use this
AWSSkillmap
Map verified service capabilities against customer-provided control framework and threat model. Produces mapping-results.json, controls-catalog.md, and framework-mapping.md. Supports pluggable frameworks: CCMv4, NIST 800-53, CIS Benchmarks, ISO 27001, etc. Split into 4 focused sub-skills for better accuracy; this skill orchestrates them.
Also in 3 projects that use this
dubwoahSkillask
Answer questions about the codebase without generating or modifying any code. Use when the user wants to understand how something works, find where something is defined, or explore the project structure. Invoked with /ask.
Also in 3 projects that use this
renatorozasSkillgrill
Adversarial code review. Don't let me ship until the changes pass your scrutiny.
Also in 3 projects that use this
VercelSkillsetup
Set up Vercel CLI and project configuration. Use when the user says "set up Vercel", "configure Vercel", "link to Vercel", or "vercel init".
Also in 7 projects that use this
IgorGanapolskySkillgraphify
Query the local Graphify-Labs AST knowledge graph for ThumbGate architecture questions (what connects X to Y, explain a symbol, PreToolUse/gates/adapters). Slash: /graphify.
Also in 3 projects that use this
Other versions48 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 48
- bradautomates/claude-video★ 18ksame name
- athina-ai/goose-skills★ 1.3ksame name
- gooseworks-ai/goose-skills★ 1.3ksame name
- SethGammon/Citadel★ 927same name
- Mathews-Tom/armory★ 340same name
- diffusionstudio/skills★ 146same name
- hidai25/eval-view★ 140same name
- romarayt/raytsystem-public-os★ 140same name
- mathiaschu/watch★ 127same name
- INo-xious/stockbit-mcp★ 58same name
38 more not listed
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 repository64 other files it gives its agents.
- accioSkill
- anthropic-doc-validatorSkill
- archifySkill
- cavecrewSkill
- caveman-compressSkill
- caveman-exploreSkill
- caveman-helpSkill
- cavemanSkill
- codebase-designSkill
- conference-talk-deckSkill
- config-gcSkill
- context-budgetSkill
- domain-modelingSkill
- excalidrawSkill
- explain-yogi-like-he-is-5Skill
- field-guide-builderSkill
- gateguardSkill
- geo-contentSkill
- goal-creatorSkill
- grillingSkill
- grill-meSkill
- grill-with-docsSkill
- hindsightSkill
- implementSkill
- improve-codebase-architectureSkill
- loop-design-checkSkill
- mental-modelsSkill
- migrationSkill
- modern-pythonSkill
- no-ai-slopSkill
- onboard-lightSkill
- onboard-repoSkill
- ponytail-auditSkill
- ponytail-reviewSkill
- ponytailSkill
- primitive-classifierSkill
- prompt-fixerSkill
- prompt-optimizerSkill
- prototypeSkill
- qa-deckSkill
- read-wikiSkill
- researchSkill
- resolving-merge-conflictsSkill
- safe-refactorSkill
- scope-creep-checkSkill
- sdd-workshop-walkthroughSkill
- setup-matt-pocock-skillsSkill
- skill-complySkill
- skill-scoutSkill
- smellsSkill
- spec-interviewSkill
- surgical-patchSkill
- teachSkill
- the-llm-councilSkill
- to-questionnaireSkill
- to-specSkill
- to-ticketsSkill
- triageSkill
- wait-whatSkill
- wayfinderSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 44 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Prefer the most robust method available.
- Distinctive: line 48
If neither tool is installed, tell the user once, plainly:
- Distinctive: line 53
Don't loop on install errors.
- Very specific: line 66
Keep timestamps where useful.
- Distinctive: line 92
If you could not get a transcript, say so and stop, then ask the user to paste it.
“Common” is measured: kept by at least 6 in 10 of the 44 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
Watch (YouTube-first video analysis)
Point Claude at a YouTube video and get its content back as structured notes, without watching it yourself. The skill fetches the transcript, then analyzes it for whatever you need: a summary, timestamped chapters, key takeaways, action items, quotes, or answers to a specific question.
There is no magic here. The model cannot "see" a video; everything depends on getting a text transcript first. So the skill's real job is to (1) reliably pull the transcript, (2) clean it, (3) analyze it well, and (4) be honest when the transcript can't be obtained instead of inventing content.
Step 1 - Identify the video
Extract the video ID and note the URL form: youtube.com/watch?v=ID, youtu.be/ID,
/shorts/ID, or /live/ID. If the user pasted a non-YouTube link, say this skill is
YouTube-first and offer the paste-the-transcript fallback (Step 4).
Step 2 - Fetch the transcript
Prefer the most robust method available. Check what is installed and degrade gracefully.
Method A - yt-dlp (most robust; also gets metadata). Handles auto-generated captions when manual ones are absent.
yt-dlp --skip-download --write-auto-subs --write-subs --sub-langs "en.*" --sub-format vtt --convert-subs srt -o "%(id)s.%(ext)s" "<URL>"
yt-dlp --skip-download --print "%(title)s :: %(uploader)s :: %(duration_string)s :: %(upload_date)s" "<URL>"Then read the resulting .srt / .vtt. Auto-captions repeat rolling lines, so dedupe: each
line of speech should appear once, keeping its earliest timestamp.
Method B - youtube-transcript-api (cleanest timestamped text).
python -c "import json,sys; from youtube_transcript_api import YouTubeTranscriptApi as Y; print(json.dumps(Y.get_transcript(sys.argv[1])))" <VIDEO_ID>Returns [{text, start, duration}, ...], already clean. Good when it works; falls over if
transcripts are disabled for the video.
If neither tool is installed, tell the user once, plainly:
I need a transcript tool. Install either with
pip install yt-dlporpip install youtube-transcript-api, or paste the transcript here and I'll work from that.
Don't loop on install errors. Surface the problem and offer the paste fallback.
Step 3 - Analyze for the user's intent
With no specific ask, default to the Structured summary template below. Otherwise match the request:
- Deep notes - section-by-section detail, faithful to the speaker's logic.
- Action items - concrete, do-able steps the video recommends.
- Quotes - the most striking verbatim lines, with timestamps.
- Chapters - a timestamped table of contents.
- Answer a question - answer only from the transcript; if it isn't covered, say so.
Keep timestamps where useful. Deep-link form: https://youtu.be/<id>?t=<seconds>.
Structured summary (default)
# <Title> - <Uploader> (<duration>)
**TL;DR:** <2-3 sentence gist>
## Key takeaways
- <takeaway> [mm:ss]
- ...
## Section notes
### <Section title> [mm:ss]
<what's covered>
## Worth quoting
> "<quote>" [mm:ss]Offer to save the output to a markdown file if it's long or the user wants to keep it. In a repo
with a knowledgebase/ wiki, save the capture under knowledgebase/raw/ and offer to hand it to
write-wiki for ingest.
Step 4 - Honesty guardrail
If you could not get a transcript, say so and stop, then ask the user to paste it. Never summarize a video you don't have the transcript for, never guess at content from the title, and don't present a thumbnail or description as if it were the video. A wrong summary is worse than an honest "I couldn't fetch 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.

