product-demo
Skill0 starsChanged 15 days agoMITView on GitHub
Make a short, polished product demo video (MP4) for a tool, app or library by reading the project itself - README, docs, UI strings, routes, CLI help, sample files - and turning its main workflow into animated HTML mock scenes with smooth transitions and dashed arrows. Use when the user asks for a demo, promo, walkthrough, launch or "how it works" video of their product, or for a hero video for a landing page.
13 other projects use a version of this.
Adopted by
Most recently taken up by
- pedronauck/skillstheir own version, first seen Nov 15, 2026
- nuthinking/skillstheir own version, first seen Nov 8, 2026
- ImBIOS/skillstheir own version, first seen Nov 8, 2026
- zuckenbert/video-from-codetheir own version, first seen Nov 8, 2026
- akachandan1/video-studiotheir own version, first seen Nov 8, 2026
- CatCatUncle/openworkbuddytheir own version, first seen Nov 5, 2026
Other versions13 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 13
- pedronauck/skills★ 655same name
- CatCatUncle/openworkbuddy★ 413same name
- Alexwtlf/agentic-product-demo★ 71same name
- charlie947/reel-editing-skills★ 9same name
- Anshgrover23/product-demo-playbook★ 6same name
- ucsandman/claude-skills★ 5same name
- akachandan1/video-studio★ 2same name
- LogicOber/Worldview-Skills★ 2same name
- ofoxai/skills★ 2same name
- Anshgrover23/product-demo-skill★ 1same name
3 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 repository3 other files it gives its agents.
- gif-loopSkill
- video-briefSkill
- video-engineSkill
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 10 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 19
Write down the sources for each fact.
- Very specific: line 31
Follow ../video-engine/references/workflow.md: shots.mjs loop, render.mjs, then mix.mjs.
- Distinctive: line 39
Do not invent features, numbers, platforms or prices.
- Distinctive: line 40
Do not use screenshots of other companies' products or their logos.
- Distinctive: line 41
Do not exceed 60 s; cut a step before you speed up the pace.
“Common” is measured: kept by at least 6 in 10 of the 10 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
Product demo from the codebase
Goal: a 35 to 55 s video that shows what the tool does, step by step, so a new user understands every main feature in one watch. It demonstrates functions, not the interface: scenes are clean mocks of the idea (a document, a table, a list, a result), not screenshots.
This skill uses the engine in ../video-engine/ (kit, templates, scripts). Read ../video-engine/SKILL.md first.
1. Read the tool
Find out, from the project and not from guesses:
- What it is for and who uses it: README, landing page,
package.json/pyprojectdescription, docs, spec. - The main workflow: the steps a user goes through, in order. Look at the UI routes or wizard steps, menu items, CLI commands and their
--help, i18n string files (they hold every visible label), tests that walk the happy path (e2e tests are gold). - Inputs and outputs: file types, sample or fixture files, what gets produced (names, formats, where).
- What makes it different: offline, speed, privacy, price, platforms. Only claims the project states; check licence and supported platforms before you write them.
- Brand: the name, the logo or app icon file, the main colour, the site URL. Write down the sources for each fact. Anything you could not confirm stays out of the video, or you ask.
2. Plan
- One scene per main step, three to six steps. Merge minor options into a panel line ("Missing one? Pick it by hand").
- For each step pick the visual metaphor: a document whose blanks become tags, a table whose rows slide in, chips joined by dashed arrows, numbers that count up, cards that fan out and fly into a ZIP or PDF, an image with dashed field boxes, a result filled in by typing.
- Sample data: the project's own fixtures if suitable, otherwise realistic made-up data for the target audience (names, dates, amounts). Use the audience's language for the on-screen text; English for an international audience.
- Show the storyboard (scene, seconds, visual, panel text) to the user when choices are open: audience, language, length, music. Recommend defaults instead of asking open questions.
3. Build
Copy ../video-engine/kit/ and ../video-engine/templates/product-demo.html into a video/ folder (or where the user wants it). Replace the made-up "Ledgerly" content scene by scene. Keep: the left visual / right panel layout, the brand mark, the step tracker, intro and outro, and the motion recipes in ../video-engine/references/style.md. Use the project's logo and colour (--accent) when it has them.
4. Check, render, sound
Follow ../video-engine/references/workflow.md: shots.mjs loop, render.mjs, then mix.mjs.
- Music: only a file the user provides and has rights to. Otherwise deliver silent and say so.
- Voice-over: write the timed script with
../video-engine/references/voiceover.mdand offer it; mix the clips when the user sends them.
5. Deliver
The MP4 (1080p), a 720p web copy if it goes on a site, the poster frame, the HTML source, and the voice-over script. If the video goes into the project (landing page hero, README), follow that repository's rules for branches and pull requests, and check the page where it plays (aspect ratio, size, poster).
Do not
- Do not invent features, numbers, platforms or prices. Do not show real people's personal data.
- Do not use screenshots of other companies' products or their logos.
- Do not exceed 60 s; cut a step before you speed up the pace.
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.

