agentleFS
Sign inStart free
BenitoowBenitoow/cinema-skills/skills/shot-list/SKILL.md

shot-list

Skill0 starsChanged 41 days agoMITView on GitHub

Turn a scene, synopsis or script excerpt into a practical shot list (shot size, angle, movement, lens, action, duration). Use when the user is planning how to film or storyboard a scene, or asks for coverage, shot breakdowns or a shooting plan.

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. badgids/Story-Film-Skills★ 4same name
    2. shutckin/aivfx-content-kit★ 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 repository4 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

7 rules. About 0 are common, 7 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Ask for whatever is missing.

    line 16
  2. Distinctive:

    If the user already gave some of these, do not ask again.

    line 23
  3. Distinctive:

    Read the scene and mark its beats (setup, turn, reveal, payoff).

    line 27
  4. Distinctive:

    Add coverage for dialogue and action: singles, overs, inserts, reactions.

    line 29
  5. Distinctive:

    Start with two lines: assumptions made, and the one-sentence visual idea of the scene.

    line 36
  6. Distinctive:

    Never invent plot, dialogue or characters.

    line 55
  7. Distinctive:

    Do not pad. A 20-second scene does not need 25 shots.

    line 56

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

Shot List

Build a shot list a crew could actually shoot from the next morning.

Before you write anything

Ask for whatever is missing. Do not guess these:

  1. Format: aspect ratio and delivery (vertical 9:16, 16:9, 2.39:1, etc.)
  2. Tone / references: genre, mood, any films or looks to evoke
  3. Constraints: location, number of actors, available gear, time budget, daylight
  4. Scene text: the scene itself, not just the title

If the user already gave some of these, do not ask again. If they say "just do it", state your assumptions in one line and proceed.

Process

  1. Read the scene and mark its beats (setup, turn, reveal, payoff). Each beat should earn at least one shot.
  2. Pick a master / establishing shot first so geography is clear.
  3. Add coverage for dialogue and action: singles, overs, inserts, reactions.
  4. Vary shot size and movement with intent. A change of size should mean something (tension, intimacy, reveal), never just variety.
  5. Flag shots that are expensive or risky (crane, stunt, night exterior, VFX) and offer a cheaper alternative.
  6. Estimate durations only as rough screen-time targets, not shooting time.

Output format

Start with two lines: assumptions made, and the one-sentence visual idea of the scene.

Then a table:

#BeatSizeAngleMovementLens (approx.)Action / subjectEst. screen timeNotes
  • Size: ECU, CU, MCU, MS, MWS, WS, EWS
  • Angle: eye-level, low, high, Dutch, OTS, POV
  • Movement: static, pan, tilt, dolly in/out, track, handheld, gimbal, crane
  • Lens: focal length range (e.g. 24-35mm wide, 50mm normal, 85mm+ portrait). Say "approx."; this is guidance, not a spec.

End with:

  • Must-get shots (the 3 shots without which the scene fails)
  • If time runs out (what to cut first)
  • Questions (max 3) only if something genuinely changes the plan

Rules

  • Never invent plot, dialogue or characters. Work only from the scene given.
  • Do not pad. A 20-second scene does not need 25 shots.
  • Respect the stated aspect ratio: vertical framing changes composition (headroom, lateral space, subtitle safe zones).
  • Plain filmmaking vocabulary. No jargon the user did not use first, unless you define it once.

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.

Check your setup, free