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

event-recap-video

Skill1 starsChanged 9 days agoMITView on GitHub

Make an event recap with Vidova, the AI video editor. Use when someone asks for a recap or aftermovie of an event or a year: a party, a festival, a conference, a launch, a team or school year, or a community celebration. Vidova cuts, captions, animates, adds music and renders the video in the cloud.

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. binay-py/claude-skills★ 1same 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 repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 1 is distinctive, and 5 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.

  • 5

    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:

    Read every photo and clip with read_asset: who is in it, where the faces are, whether it is a stage, a crowd, a speaker or the group photo, …

    line 15
  3. Very specific:

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

    line 16
  4. Very specific:

    Follow the order they gave.

    line 17
  5. 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
  6. Distinctive:

    Use only the names, roles, dates, places and numbers they wrote or that appear on their own pictures.

    line 29

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

Event recap

The people who were there watch it to see themselves, and everyone else watches to wish they had been.

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. Read every photo and clip with read_asset: who is in it, where the faces are, whether it is a stage, a crowd, a speaker or the group photo, and whether its sound matters. Leave out blurry and dark files.
  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. Follow the order they gave. Find music with search_stock kind music, add it with import_stock, and read it with detect_beats. Keep a speech line or a cheer in its real sound, with captions from transcribe_asset.
  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.
  • Name the event in the first second, over faces and energy.
  • A named order is a hard rule.
  • Match the mood: a party or a festival is fast and upbeat, a memorial is warm and steady, a conference is clean and confident.
  • A photo fills the frame with a slow push, with the faces in the upper half.
  • End on everyone together, with a closing line or the next date they gave.
  • Use only the names, roles, dates, places and numbers they wrote or that appear on their own pictures. Spell names exactly.

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.