agentleFS
scrollmarkscrollmark/social-skills/skills/editor-camera-directing/SKILL.md

editor-camera-directing

Skill19 starsChanged 29 days agoMITView on GitHub

Use when adding zooms, pans or Ken Burns moves to a Scrollmark editor video, or a first recut that should feel directed rather than static.

The file

We split this skill into the rules it gives an agent

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

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Do not: a move on every keep-range.

    line 30

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

Editor Camera Directing

Requires

A running Scrollmark editor whose commands you can call: the SocialGPT editor chat, or scrollmark mcp from @scrollmark/cli for a coding agent. Without it the moves can't be applied; the rule for when a move is earned holds in any editor.

Directing, not a quota

This is directing, not a one-zoom quota and not a move on every clip.

Find beats in this order:

  1. Transcript — punchlines, reveals, "look at this," named objects, joke landings.
  2. The project's semanticBrief scenes (in the project snapshot) — silent B-roll, gestures, look-aways, props.
  3. media_inspectSourceFrames at 1–3 file seconds on those candidates. After apply, preview_inspectFrames at the timeline seconds.

A move only if the line is motivated and the subject (or a face, for a joke beat) is in the picture. If inspect cannot show it, skip. Several moves per video is fine. No count cap.

Applying a move

element_applyCameraMove on video/image only. Named kinds: zoom_in / zoom_out / pan_left / pan_right / tilt_up / tilt_down. Default amount 0.15. startS/endS are clip-local and cover the beat, not the whole take.

Stills/B-roll that would sit dead get a slow Ken Burns (zoom_in or a pan) over the hold. Talking-head: punch in on the beat; do not Ken Burns the entire speech. Match pan/tilt to where the subject is. Never element_setParams for motion (that clears camera keys). To take a move off a clip without undoing other edits, element_clearCameraMove.

Do not: a move on every keep-range; filmstrip the whole tape; animate captions/stickers.

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.