creator-video
Skill18 starsChanged 47 days agoMITView on GitHub
Plan and script a short video presented by a person on camera. Use for founder demos, talking-head explainers, creator tutorials, launch clips, and shot lists.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- mehbylabs/creator-skillstheir own version, first seen Nov 8, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- mehbylabs/creator-skills★ 7same 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 repository10 other files it gives its agents.
- brand-filmSkill
- brand-grid-videoSkill
- feature-videoSkill
- narrated-product-filmSkill
- silent-product-demoSkill
- social-video-hooksSkill
- ui-component-clipSkill
- ui-tutorial-videoSkill
- video-brand-systemSkill
- video-thumbnailsSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 6 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 13
The real task: Follow the presenter doing useful work with the product.
- Distinctive: line 15
The guided screen: Put the presenter beside a legible screen recording.
- Distinctive: line 21
Start with the result, tension, or action.
- Distinctive: line 27
Keep each spoken line easy to say in one breath.
- Distinctive: line 34
Keep the lens near eye level.
- Distinctive: line 38
Use captions when they help silent viewing.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Creator video
Build the video around a real task and a claim the viewer can see tested. The presenter is part of the proof: their actions, screen, and result should agree.
Choose a shape
- The test: Show the same task two ways, measure the result, then inspect the output. Use when the claim can be checked on camera.
- The real task: Follow the presenter doing useful work with the product. Use when the value appears during the work itself.
- The day: Show a recurring problem and how the product changes it. Use when the environment and human context matter.
- The guided screen: Put the presenter beside a legible screen recording. Use when the interface is the main story.
Choose the shape that the available footage can prove. Do not invent a test result or stage work as spontaneous.
Write the beat sheet
Start with the result, tension, or action. Introduce the presenter once the viewer has a reason to care. Write one row for each beat:
| Time | Camera or screen | Exact spoken line | Evidence shown |
| 0:00 | Task already under way | “Can I finish this before the timer?” | Timer and task are visible |
Keep each spoken line easy to say in one breath. Replace broad claims with a specific result or an honest demonstration. If the product has a material limitation or privacy setting, show the relevant control and explain its scope precisely.
Turn the beat sheet into a shot list: camera setups, screen captures, props, and any measurements needed. State what can be filmed now and what is still missing.
Shoot and edit
- Record a clean voice track. Place the microphone close enough that the product and presenter remain intelligible on a phone.
- Keep the lens near eye level. Leave safe space for platform controls and captions.
- Capture screens directly at a readable resolution. Show the real product state, including loading or errors when they matter to the claim.
- Record each spoken beat twice: one precise take and one natural take.
- Cut pauses and repetition while preserving the sequence of actions. Do not edit a timed comparison in a way that changes its result.
- Use captions when they help silent viewing. Check that they do not hide the UI or contradict what was said.
Export the aspect ratios the user needs. Reframe each ratio deliberately; do not crop away the evidence. Choose a cover frame with a clear subject and legible result.
Before delivery
Watch the final export with sound and once muted. Check that the opening is understandable, the screen is readable, any numbers match the footage, captions are accurate, and the call to action describes one clear next step.
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.