agentleFS
solankipravin374solankipravin374/visuals-skills/skills/visuals-core/SKILL.md

visuals-core

Skill0 starsChanged 21 days agoMITView on GitHub

Shared tools and the shooting guide for the /visuals effect skills (orbit, zooming, words-from-behind, icon-on-palm, zig-zag-graph, paper, thanos-snap, share-comment). Use it to plan or film a laptop-on-a-desk reel for these effects, to measure coordinates (grid.py), to build the laptop mask (mask.py), or to stitch the rendered effect clips together.

  • Installs packages

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:

    Keep the folders side by side: Every effect script imports ../visuals-core/vfx.py, so install all 9 folders into the same skills directory.

    line 18
  2. Distinctive:

    Find the moment: Ask the user for the clip and the rough time of each beat, or scrub it with ffmpeg stills.

    line 23
  3. Very specific:

    Measure: Run grid.py on a still from the beat and read coordinates off the grid.

    line 25
  4. Very specific:

    Preview: Every effect takes --preview 0.3,1.0,2.0 (effect-local seconds) and writes PNG stills in seconds instead of a video.

    line 32

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

visuals-core

The engine under the 8 /visuals skills. Each effect skill is a Python script that turns a few seconds of your own footage into a finished effect clip (MP4 with the original audio). This folder holds what they share:

  • vfx.py: ffmpeg video I/O, laptop/screen/hand masks, easing and springs, RGBA compositing, sticker text
  • grid.py: writes a still with a labelled pixel grid, so you can read off coordinates for flags like --target
  • mask.py: builds laptop_mask.png, the cut-out every "behind the lid" effect uses, plus a red check overlay

Requirements: Python 3.9+, pip install opencv-python numpy pillow, and ffmpeg on PATH. SVG logos are drawn with headless Chrome/Edge if installed (or pip install cairosvg); PNG always works.

Keep the folders side by side. Every effect script imports ../visuals-core/vfx.py, so install all 9 folders into the same skills directory.

The workflow (same for every effect)

  1. Find the moment. Ask the user for the clip and the rough time of each beat, or scrub it with ffmpeg stills. Times are in seconds of the source clip.
  2. Measure. Run grid.py on a still from the beat and read coordinates off the grid. Look at the image; do not guess.
    python <skills>/visuals-core/grid.py --in clip.mp4 --t 30.9 --out grid.jpg
    python <skills>/visuals-core/mask.py --in clip.mp4 --t 30.9 --out laptop_mask.png   # hand-free frame
    Open laptop_mask_check.jpg: the red area must cover the whole laptop and nothing else. If it spills onto a dark table, raise --min-y or lower --v-max.
  3. Preview. Every effect takes --preview 0.3,1.0,2.0 (effect-local seconds) and writes PNG stills in seconds instead of a video. Look at them and adjust flags.
  4. Render. Drop --preview, set --out effect.mp4. Output is 1080x1920 30 fps H.264 + the clip's audio.
  5. Stitch. Concatenate in your editor, or:
    printf "file 'orbit.mp4'\nfile 'zoom.mp4'\n" > list.txt
    ffmpeg -f concat -safe 0 -i list.txt -c copy reel.mp4

Flags every effect has

flagmeaning
--in, --start, --dur, --outsource clip, effect start (s), effect length (s), output
--size 1080x1920, --fps 30output format (portrait by default)
--mask laptop_mask.pngthe laptop cut-out (auto-detected if omitted)
--preview t1,t2,...write stills at these effect-local times instead of rendering
--gamma 0.86brighten dark footage (lifts the mids; 1.0 = off)
--wb 1.045,0.995,1white-balance gains B,G,R (this example cools a yellow wall)
--no-audiodo not copy the source audio

Shooting guide (what makes these effects possible)

  1. Locked-off camera. Phone on a tripod, vertical, never touched. The hand and lid tricks key against a still frame.
  2. Framing. Laptop in the lower ~55% of the frame, plain wall above it: orbit, words, graph and the sticker live there.
  3. Even front light, exposure and focus locked (long-press AE/AF lock). 4K if you can: /zooming dives deeper.
  4. Big screen text. Zoom the app in (Ctrl/Cmd +), dark or light mode, notifications off.
  5. Hand-free moments. Hold still with hands off the laptop for 2-3 s now and then. Those frames are the --ref-time the hand effects key against.
  6. Clean plate for /thanos-snap: after the take, lift the laptop out and record 5 s of the empty desk without moving the phone.
  7. Per beat: say the line, type the slash command slowly, Enter, then do the action:
effectwhat to do on camera
/orbithands off the keyboard, hold still 3-4 s
/zoominghands still 4 s (choose a target on screen: an icon, a mascot's eye)
/words-from-behindhands still 3 s
/icon-on-palmraise an open palm, flat and facing up, beside the laptop; hold 4 s, move it only slightly
/zig-zag-graphone index finger draws a rising zig-zag left to right above the laptop (~2 s)
/paperhands on the keyboard, mostly still, 3-4 s
/thanos-snaphand up beside the laptop, one clear snap, hold 1 s, then hands out of frame
/share-comment4 s of the empty desk (or use the clean plate as the background)

Full guide with the reasons behind each rule: docs/SHOOTING.md in the repository.

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.