agentleFS
svenkatreddysvenkatreddy/universal-video-skills/skills/story-and-shots/SKILL.md

story-and-shots

Skill8 starsChanged 30 days agoMITView on GitHub

Plan AI video like a production: beats, shot lists, storyboards, review gates, and a fast-track for simple jobs. Use when a video needs more than one shot, or when generations keep drifting off-story.

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. Very specific:

    Gate it: Run the quality gates (references/quality-gates.md): style proof first, asset lock before generation, beat cards that each carry …

    line 23
  2. Distinctive:

    Every shot earns its place: If removing a shot changes nothing, remove it.

    line 34

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

Story and Shots

A single good prompt makes a good clip. A good video needs something else: structure. AI generators make shots; they don't make sequences. The sequence is your job, and it gets planned before anyone touches a prompt.

The workflow

  1. Beat it out. Break the story into beats: one line each, each a change in the story (references/beats-and-shot-lists.md). If you can't list the beats, you don't have a story yet.
  2. Shot-list every beat. One beat is usually one to three shots. Each shot gets a shot-brief (../video-prompt-craft/). No shot exists without a brief; no brief exists without a beat.
  3. Board it (for anything complex). Sketch the sequence visually (references/storyboard.md). Storyboards catch screen-direction flips and pacing problems that text hides.
  4. Gate it. Run the quality gates (references/quality-gates.md): style proof first, asset lock before generation, beat cards that each carry one clear visual change. Max two revision rounds per gate, then move on.
  5. Fast-track the simple stuff. One product shot, one establishing clip? Skip the ceremony (quality-gates.md has the short path). Process should scale down, not just up.

Rules that don't bend

  • Story first, prompts second. A shot list written before any generation beats ten brilliant prompts generated in random order.
  • Every shot earns its place. If removing a shot changes nothing, remove it. AI video tempts you to keep generating; editing is the skill.
  • Plan the joins. Shots don't just sit next to each other. They cut. Note the transition or match cut per join in the shot list, or the assembly stage inherits a mess.
  • Budget the seconds. Total runtime divided by shot count is your per-shot budget. A 60-second video at 8 seconds a clip is eight shots max. Plan eight, not fifteen.
  • Lock assets before generating. Characters, products, key props get registered (../character-consistency/) before the first generation, not after the third reshoot.

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.