travel-recap-video
Skill1 starsChanged 9 days agoMITView on GitHub
Make a travel recap with Vidova, the AI video editor. Use when someone asks for a trip video from the person's clips: a holiday, a road trip, a city break or a honeymoon, with the places on a map or in titles, cut to the beat. 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
- family-videoSkill
- motion-graphicsSkill
- music-videoSkill
- podcast-clipsSkill
- product-ad-videoSkill
- sports-highlightsSkill
- vidovaSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 1 is distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
3
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 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 28
Keep the real sound where it adds something: waves, a street musician, a laugh.
≈ “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
Travel recap
A trip told in under a minute, so the person relives it and their friends want to go.
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. - Work out where they went, in what order and when, from the message, the file names and what
read_assetshows (landmarks, signs, food, dates). For each clip, note the place, the moment, and whether its sound is worth keeping. - 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 on the downbeats. Find a track with
search_stockkind music, add it withimport_stock, and read it withdetect_beats.search_elementshas maps and route graphics for the stops. - 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.
- Build a journey: leaving, getting there, the best days, the last evening.
- Open on the most striking shot, already moving, with the place name or the start of the route.
- Speed up toward the best days. Hold the last evening for 3 to 4 seconds while it keeps moving.
- Name each place once, on the first shot of its section. Text stays off landmarks and faces.
- Keep the real sound where it adds something: waves, a street musician, a laugh.
- Make 20 to 45 seconds for a short, or 60 to 90 seconds for a 16:9 film. Never invent a place.
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.

