agentleFS
solankipravin374solankipravin374/visuals-skills/skills/thanos-snap/SKILL.md

thanos-snap

Skill0 starsChanged 21 days agoMITView on GitHub

Video effect - snap your fingers and the laptop crumbles into drifting ash, wave by wave from the snap, while your hand stays in front; the laptop stays gone and the shot settles on a clean plate of the empty desk. Use when the user types /thanos-snap (or /thanos-finger) or wants an object to disintegrate into dust after a snap.

The file

We split this skill into the rules it gives an agent

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

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    After the snap a dissolve wave spreads across the laptop from the snapping hand.

    line 8
  2. Very specific:

    No outline of the laptop is left on the wall after the dust.

    line 49

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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

/thanos-snap

After the snap a dissolve wave spreads across the laptop from the snapping hand. Each pixel chars, lets go and becomes an ash particle that drifts up and away with a little turbulence. The background behind is revealed from a clean plate, the real hand stays composited on top, and the shot ends on the empty desk. ~3.4 s.

Needs:

  1. A locked-off clip with one clear snap near the laptop.
  2. A clean plate: the same shot without the laptop. Lift the laptop out after the take, and keep the phone still.
  3. A frame with the laptop in place and the hand not over it (--ref-time). Its colours are what turn to dust.

Requires visuals-core next to this folder.

Steps

  1. Align and colour-match the plate to the clip (once):
    python plate.py --in clip.mp4 --t 90.8 --plate empty_desk.jpg --out plate.png --mask laptop_mask.png
    Open plate_seam_check.jpg: the laptop area is filled from the plate, and wall marks should line up. A video plate works too (--plate empty.mov --plate-t 2). Cover a leftover marker with --patch x0,y0,x1,y1,dx.
  2. Find the snap frame (local time from --start) and preview:
    python thanos_snap.py --in clip.mp4 --start 91.5 --dur 3.4 --out preview --preview 0.6,1.1,1.5,2.0,3.3 \
        --plate plate.png --snap-time 0.72 --ref-time 90.8 --mask laptop_mask.png
  3. Render without --preview, with --out thanos.mp4. Add the real snap sound in the edit if the audio is quiet.

Flags

flagdefaultmeaning
--platerequiredoutput of plate.py
--snap-timerequiredlocal time of the snap
--ref-timerequiredframe with the laptop, hand not over it
--origin x,ytop-right of the laptopwhere the wave starts (put it at the snapping hand)
--spread1.55seconds for the wave to cross the laptop
--ash#3C322Cash colour
--settle0.5final crossfade onto the plate (0 = off)
--thr34hand-difference threshold

Check before delivering

  • No outline of the laptop is left on the wall after the dust. If a lighter rectangle shows, re-run plate.py from a closer --t, or check that the plate was shot with the same exposure.
  • The hand stays solid in front of the dust, with no halo. A halo means the ref frame has a different screen state, so pick another.

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.