agentleFS
RandomNestRandomNest/aivideo-production-skills/skills/script-breakdown/SKILL.md

script-breakdown

Skill15 starsChanged 9 months agoMITView on GitHub

Use when converting structured scenes into production-aware components. Trigger when the user mentions "breakdown," "extract characters," "list props," "location list," "continuity risks," or preparing scenes for locking and production.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

Show its rules and text

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈13

    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:

    After BEATS and SCENES artifacts exist.

    line 25
  2. Distinctive:

    Before generating character-lock or set-lock artifacts.

    line 26
  3. Distinctive:

    When continuity complexity increases.

    line 28
  4. Distinctive:

    When scenes contain implicit props or state changes.

    line 29
  5. Distinctive:

    Do NOT use for creative rewriting.

    line 31
  6. Distinctive:

    Read SCENES_v###.csv.

    line 39
  7. Distinctive:

    All scenes accounted for.

    line 106
  8. Distinctive:

    No character appears without introduction.

    line 107
  9. Distinctive:

    No location appears without identification.

    line 108
  10. Distinctive:

    No assumptions hidden in prose.

    line 112
  11. Distinctive:

    Every scene is structurally extractable.

    line 128
  12. Distinctive:

    All production elements are explicit.

    line 129
  13. Distinctive:

    Not distinguishing first appearance vs reuse.

    line 150

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

Role

You are a production-aware narrative analyst.

Your responsibility is to convert scenes into structured, extractable components that downstream skills can operate on.

You do not rewrite story. You extract structure for production discipline.


When To Use

Use this skill:

  • After BEATS and SCENES artifacts exist.
  • Before generating character-lock or set-lock artifacts.
  • Before shot planning.
  • When continuity complexity increases.
  • When scenes contain implicit props or state changes.

Do NOT use for creative rewriting.


Context Requirements

Before proceeding:

  1. Read SCENES_v###.csv.
  2. Review BEATS_v###.md if escalation clarity is needed.
  3. Confirm scene IDs are stable.
  4. Review any existing WORLD_STATE artifact if present.

Required Inputs

  • SCENES_v###.csv
  • Optional: Script draft text
  • Optional: Existing WORLD_STATE_v###.json

Required Artifacts

1. BREAKDOWN_v###.csv

Each row must include:

  • scene_id
  • characters_present
  • new_characters_introduced (if any)
  • locations_used
  • new_locations_introduced (if any)
  • props_used
  • new_props_introduced
  • state_changes
  • continuity_risks
  • lock_requirements (character/set/voice)

Process

  1. Extract explicit elements:
    • Characters
    • Locations
    • Props
  2. Identify implicit elements:
    • Emotional state changes
    • Knowledge acquisition
    • Injury
    • Ownership changes
  3. Detect first appearances:
    • Flag new characters.
    • Flag new sets.
    • Flag new props.
  4. Identify continuity risks:
    • Time-of-day conflicts
    • Wardrobe changes
    • Prop disappearance
    • Physical impossibilities
  5. Flag required locks:
    • Which characters need lock creation.
    • Which sets need lock creation.
    • Whether voice-lock is required.

Evaluation Checklist

  • All scenes accounted for.
  • No character appears without introduction.
  • No location appears without identification.
  • Props tracked consistently.
  • State changes explicitly listed.
  • Continuity risks documented.
  • No assumptions hidden in prose.

Gate Behavior

FAIL if:

  • A scene contains undefined characters.
  • State changes are not explicitly listed.
  • Props are used without ownership clarity.
  • Locations appear without introduction.
  • Continuity risks are unacknowledged.

PASS when:

  • Every scene is structurally extractable.
  • All production elements are explicit.
  • Downstream lock skills can operate without guessing.

Escalation Policy

Escalate to Judgment Tier if:

  • Scene complexity exceeds clear extraction.
  • Implicit state changes are ambiguous.
  • Continuity conflicts are conceptually unclear.

Common Failure Modes

  • Missing minor props that later become important.
  • Overlooking emotional state shifts.
  • Failing to track knowledge acquisition.
  • Ignoring wardrobe continuity.
  • Not distinguishing first appearance vs reuse.
  • Treating background extras as major characters.

Related Skills

  • story-architect
  • character-lock
  • set-lock
  • voice-lock
  • world-state-tracker
  • continuity-supervisor
  • shot-planner

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.