agentleFS
Sign inStart free
badgidsbadgids/Story-Film-Skills/skills/edit-plan/SKILL.md

edit-plan

Skill4 starsChanged 3 months agoApache-2.0View on GitHub

Create a post-production edit plan and cue sheet from screenplay, shot list, generated clip durations, dialogue, music, and SFX, including transitions, pickups, and continuity risks.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Read core contract, screenplay, scene manifest, shot list, continuity, music cues, SFX cues, and known generated durations.

    line 13
  2. Very specific:

    Write 05_post/edit_plan.md scene by scene with intended cut order, pacing, transitions, audio bridges, and pickup alternatives.

    line 14
  3. Very specific:

    Write 05_post/cue_sheet.csv mapping shot, dialogue, voice, music, SFX, and ambience IDs to timeline intent.

    line 15
  4. Distinctive:

    Keep a pickup list for missing inserts, reactions, establishing material, or clean audio.

    line 17

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

Edit Plan

Workflow

  1. Read core contract, screenplay, scene manifest, shot list, continuity, music cues, SFX cues, and known generated durations.
  2. Write 05_post/edit_plan.md scene by scene with intended cut order, pacing, transitions, audio bridges, and pickup alternatives.
  3. Write 05_post/cue_sheet.csv mapping shot, dialogue, voice, music, SFX, and ambience IDs to timeline intent.
  4. Flag duration mismatches instead of hiding them with arbitrary slow motion or repeated footage.
  5. Keep a pickup list for missing inserts, reactions, establishing material, or clean audio.

Done

The planned cut can be assembled from named assets or clearly listed pickups, with no unidentified clip or cue dependency.

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