family-video
Skill1 starsChanged 9 days agoMITView on GitHub
Make a family video with Vidova, the AI video editor. Use when someone asks for a family edit from the person's own clips and photos: a summer, a holiday, a year with the kids, a tribute, a wedding or an anniversary. Vidova cuts, captions, animates, adds music and renders the video in the cloud.
In this repository11 other files it gives its agents.
- beat-sync-editSkill
- birthday-videoSkill
- event-recap-videoSkill
- explainer-videoSkill
- motion-graphicsSkill
- music-videoSkill
- podcast-clipsSkill
- product-ad-videoSkill
- sports-highlightsSkill
- travel-recap-videoSkill
- vidovaSkill
The file
We split this skill into the rules it gives an agent
6 rules. About 0 are common, 2 are distinctive, and 4 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 13
Check that the Vidova tools are available, for example with get_active_project.
- Very specific: line 15
Read every clip and photo with read_asset: the moment with the most feeling and its time, where the faces are, whether its sound is worth …
- Very specific: line 16
If the server offers a routine for a new edit from uploads, start it and follow its handoff.
- Very specific: line 19
Call render_video, wait for it with wait_for_jobs, then give the person the project url and the link to the finished video.
- Distinctive: line 24
Use fewer, better moments, and leave out the soft, dark and shaky clips.
- Distinctive: line 30
Use the names, places and years they wrote.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Family video
The person's own clips of people they love, cut to music, made to be shared in the family chat.
Steps
- Check that the Vidova tools are available, for example with
get_active_project. If they are not, follow thevidovaskill to connect. - Make a project with
create_project. Bring the files in withimport_asset_urlfor a link,begin_asset_uploadfor a local file when you can run shell commands, orupload_filesto give the person the link where they add files. Callwait_for_assetuntil the files are ready. - Read every clip and photo with
read_asset: the moment with the most feeling and its time, where the faces are, whether its sound is worth keeping, and whether it is dark, shaky or soft. - If the server offers a routine for a new edit from uploads, start it and follow its handoff. Otherwise call
search_templates. When a template fits, useread_templateandapply_template, then adjust it withpatch_film. When none fits, build the film withpatch_film. - Cut to the music. Find a track with
search_stockkind music, add it withimport_stock, and read it withdetect_beats. Grade every clip to one look. - Watch the result with
preview_timeline, and withpreview_rangeacross the moments that move. Callcheck_edit, thenwait_for_jobswith its Job ID, and fix what it names. - Call
render_video, wait for it withwait_for_jobs, then give the person the projecturland the link to the finished video.
What makes it work
- The person's brief comes first: their order, song, length, format and rules. This skill fills in the rest.
- Use fewer, better moments, and leave out the soft, dark and shaky clips. A 25 second edit of eight good moments beats 60 seconds of everything.
- Make 20 to 40 seconds for sharing, or up to 60 seconds for a tribute.
- Open on the best moment, already happening, with people in frame 0.
- Cut every two beats in the lively parts. A hug or a sentence gets a whole bar. A wedding or a tribute is slower.
- Lower the music once for 1 to 2 seconds under a real sound, such as a laugh, then bring it back on a downbeat.
- End on the warmest wide shot for 3 seconds or more, still moving, with the music fading out with the picture.
- Use the names, places and years they wrote. Never invent them. Never darken a face, and keep text off faces.
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.

