agentleFS
youneslaaroussiyouneslaaroussi/vidova-skills/skills/travel-recap-video/SKILL.md

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.

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
  1. Very specific:

    Check that the Vidova tools are available, for example with get_active_project.

    line 13
  2. Very specific:

    If the server offers a routine for a new edit from uploads, start it and follow its handoff.

    line 16
  3. Very specific:

    Call render_video, wait for it with wait_for_jobs, then give the person the project url and the link to the finished video.

    line 19
  4. Distinctive:

    Keep the real sound where it adds something: waves, a street musician, a laugh.

    line 28

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Travel recap

A trip told in under a minute, so the person relives it and their friends want to go.

Steps

  1. Check that the Vidova tools are available, for example with get_active_project. If they are not, follow the vidova skill to connect.
  2. Make a project with create_project. Bring the files in with import_asset_url for a link, begin_asset_upload for a local file when you can run shell commands, or upload_files to give the person the link where they add files. Call wait_for_asset until the files are ready.
  3. Work out where they went, in what order and when, from the message, the file names and what read_asset shows (landmarks, signs, food, dates). For each clip, note the place, the moment, and whether its sound is worth keeping.
  4. 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, use read_template and apply_template, then adjust it with patch_film. When none fits, build the film with patch_film.
  5. Cut on the downbeats. Find a track with search_stock kind music, add it with import_stock, and read it with detect_beats. search_elements has maps and route graphics for the stops.
  6. Watch the result with preview_timeline, and with preview_range across the moments that move. Call check_edit, then wait_for_jobs with its Job ID, and fix what it names.
  7. Call render_video, wait for it with wait_for_jobs, then give the person the project url and 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.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.