video-explainer
Skill1 starsChanged 3 months agoMITView on GitHub
Create polished narrated MP4 walkthroughs of live websites, dashboards, and web applications. Use this skill whenever the user asks for a demo video, product tour, screen recording, narrated walkthrough, dashboard explainer, feature video, or a repeatable video that must be regenerated after a UI change. Use the bundled runner instead of manually editing a screen recording. Do not use it to summarize an existing video or create a slide deck.
- Reads credentials
4 other projects use a version of this.
Adopted by
Most recently taken up by
- norton77930/understanding-ai-outputstheir own version, first seen Oct 11, 2026
- mhylle/claude-skills-collectiontheir own version, first seen Oct 9, 2026
- runesleo/claude-video-kittheir own version, first seen Oct 7, 2026
- Galbaz1/video-research-mcptheir own version, first seen Oct 6, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- runesleo/claude-video-kit★ 123same name
- Galbaz1/video-research-mcp★ 23same name
- mhylle/claude-skills-collection★ 20same name
- norton77930/understanding-ai-outputs★ 3same 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
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 8 are distinctive, and 6 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
8
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- could be automatic: a setting could enforce it
- Distinctive: line 9
Create a scripted 1080p product walkthrough that stays synchronized with its narration.
- Very specific: line 14
If login is required, run node src/login.js <url> and save state under .auth/.
- Distinctive: line 17
Write narration first. Keep each line focused on one idea.
- Very specific: line 18
Create or update a scene file under demos/.
- Distinctive: line 20
Read every selector warning and fix missing targets.
- Distinctive: line 22
Add narration only after the silent version is correct.
- Distinctive: line 26
Use a 1280 by 720 viewport unless the product needs a different aspect ratio.
- Distinctive: line 28
Use at least two zooms in a video longer than one minute.
- Distinctive: line 30
Prefer visible text selectors over generated CSS class names.
- Distinctive: line 32
Write narration in short sentences that sound natural when spoken.
- Very specific: line 37
Use src/login.js to create a Playwright storage state file.
- Very specific: line 39
Never put cookies or tokens in a demo JSON file.
- Very specific: line 51
Use the schema and examples in README.md and demos/sample.json.
- Very specific: line 64
Keep the output under output/ and share it through the user's chosen file service.
“Common” is measured: kept by at least 6 in 10 of the 4 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 Explainer
Create a scripted 1080p product walkthrough that stays synchronized with its narration. Keep credentials, browser state, source data, and rendered videos out of Git.
Workflow
- Inspect the target page before writing selectors.
- If login is required, run
node src/login.js <url>and save state under.auth/. - Take a screenshot and identify the smallest useful story.
- Probe important selectors with
node src/probe.js <url> <selector...>. - Write narration first. Keep each line focused on one idea.
- Create or update a scene file under
demos/. - Render silently with
node src/demo.js <name> --voice=none. - Read every selector warning and fix missing targets.
- Inspect the MP4 and representative frames before sharing it.
- Add narration only after the silent version is correct.
Quality rules
- Use a 1280 by 720 viewport unless the product needs a different aspect ratio.
- Open and close with title cards.
- Use at least two zooms in a video longer than one minute.
- Zoom out before clicking so the cursor lands predictably.
- Prefer visible text selectors over generated CSS class names.
- Highlight a useful container instead of a tiny label.
- Write narration in short sentences that sound natural when spoken.
- Spell out numbers in narration when text-to-speech pronunciation matters.
Authentication
Use src/login.js to create a Playwright storage state file. Pass it with --storage-state=.auth/state.json or set VIDEO_EXPLAINER_STORAGE_STATE.
Never put cookies or tokens in a demo JSON file. Never commit .auth/ or .env.
Voice choices
--voice=noneis free and is the default.--voice=elevenlabsusesELEVENLABS_API_KEYandELEVENLABS_VOICE_IDfrom the environment or.env.--voice=systemuses the macOSsaycommand.
Tell the user before using a metered voice provider. State which provider will receive the narration text.
Scene types
Use the schema and examples in README.md and demos/sample.json. The runner supports title, navigate, wait, click, hover, type, caption, highlight, scroll, zoom, zoomOut, and narrate scenes.
Any scene can include say. Its screen time expands to fit the spoken clip. A caption without say narrates its own text.
Verification
Before delivery:
- Confirm the run log has no unresolved selector warnings.
- Confirm no private data appears in the scene file or captured page.
- Confirm captions stay inside the frame.
- Confirm audio finishes before the associated visual changes.
- Confirm the final file is 1920 by 1080 and opens successfully.
- Keep the output under
output/and share it through the user's chosen file service.
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.

