video-brief
Skill0 starsChanged 14 days agoMITView on GitHub
Make a short animated video (MP4) from the user's own brief - an explainer ("what is Docker?"), a concept or process diagram, a feature announcement, a tutorial step, a social clip - using the claude-veo look with smooth motion, dashed arrows and clean typography. Use when the user describes the video they want rather than asking to demo a codebase.
5 other projects use a version of this.
Adopted by
Most recently taken up by
- Design-of-Man/claude-skillstheir own version, first seen Oct 30, 2026
- indranilbanerjee/cutforgetheir own version, first seen Oct 20, 2026
- dawn840705/claude-code-studiostheir own version, first seen Aug 28, 2026
- dawn840705/codex-code-studiostheir own version, first seen Aug 28, 2026
- samir-sayyed/skillstheir own version, first seen Jul 21, 2026
Other versions5 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 5
- dawn840705/codex-code-studios★ 17same name
- dawn840705/claude-code-studios★ 1same name
- samir-sayyed/skills★ 1same name
- Design-of-Man/claude-skills★ 0same name
- indranilbanerjee/cutforge★ 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.
In this repository3 other files it gives its agents.
- gif-loopSkill
- product-demoSkill
- video-engineSkill
The file
We split this skill into the rules it gives an agent
5 rules. 0 are common, 3 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
3
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
- Very specific: line 26
Start from the closest template in ../video-engine/templates/:
- Very specific: line 32
Follow ../video-engine/references/workflow.md.
- Distinctive: line 35
No stock-looking clutter: one idea on screen at a time, generous space, two or three colours.
- Distinctive: line 36
No logos or trademarks of others beyond plain names used to refer to them.
- Distinctive: line 37
No real people's likeness or voice.
“Common” is measured: kept by at least 6 in 10 of the 5 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 from a brief
This skill uses the engine in ../video-engine/ (kit, templates, scripts). Read ../video-engine/SKILL.md first.
1. Pin down the brief
Settle these, asking only what the request leaves open, each with a recommended default:
| Item | Default |
| Purpose and audience | from the request |
| Length | explainer 15 s; announcement 20 to 30 s; tutorial up to 60 s |
| Format | 16:9, 1920 x 1080 (for social, 1080 x 1920 or 1080 x 1080: write <div id="stage" style="width:1080px;height:1920px"> and render with --width 1080 --height 1920; then re-lay out the scenes, since the templates are composed for 16:9) |
| Language of on-screen text | the user's language |
| Theme | dark for technical topics, light for business and HR |
| Sound | silent, unless the user provides music they have rights to; offer a voice-over script |
| Facts in the video must be correct: check anything you are not sure of, and keep claims general rather than invented (no made-up benchmarks). |
2. Storyboard
Three beats for a 15 s explainer (problem, idea, result), one beat per point for longer videos. Each beat: one visual change and one caption or panel. Write the table (seconds, visual, text) before building.
3. Build
Start from the closest template in ../video-engine/templates/:
explainer.html: title, one diagram that grows, a caption per beat, an end line.product-demo.html: window mocks with a side panel, for step-by-step flows. Reuse the kit components and motion recipes (../video-engine/references/style.md):arrow()for every connection,fx()for every entrance,count()for numbers,type()for text that appears. Draw diagrams with SVG paths in the 1920 x 1080 space and reveal them witharrow(..., { dash: "1 0", head: false })for solid lines.
4. Check, render, deliver
Follow ../video-engine/references/workflow.md. Deliver the MP4, the poster, the HTML source, and, when useful, a GIF preview and a voice-over script (../video-engine/references/voiceover.md). Say what you checked.
Do not
- No stock-looking clutter: one idea on screen at a time, generous space, two or three colours.
- No logos or trademarks of others beyond plain names used to refer to them.
- No real people's likeness or voice.
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.