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
- jpcastel88/Script-Breakdown-Skillstheir own version, first seen Aug 4, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- jpcastel88/Script-Breakdown-Skills★ 5same 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 repository23 other files it gives its agents.
- AGENTS.mdAGENTS.md
- audience-simulatorSkill
- budget-gatesSkill
- character-lockSkill
- character-psychologySkill
- continuity-supervisorSkill
- cost-optimizerSkill
- cultural-checkSkill
- dialogue-consistency-checkSkill
- model-routerSkill
- narrative-red-teamSkill
- plausibility-auditorSkill
- prompt-packagerSkill
- qc-graderSkill
- regen-analyzerSkill
- research-agentSkill
- run-loggerSkill
- set-lockSkill
- shot-plannerSkill
- story-architectSkill
- storyboard-generatorSkill
- voice-lockSkill
- world-state-trackerSkill
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
- Distinctive: line 25
After BEATS and SCENES artifacts exist.
- Distinctive: line 26
Before generating character-lock or set-lock artifacts.
- Distinctive: line 28
When continuity complexity increases.
- Distinctive: line 29
When scenes contain implicit props or state changes.
- Distinctive: line 31
Do NOT use for creative rewriting.
- Distinctive: line 39
Read SCENES_v###.csv.
- Distinctive: line 106
All scenes accounted for.
- Distinctive: line 107
No character appears without introduction.
- Distinctive: line 108
No location appears without identification.
- Distinctive: line 112
No assumptions hidden in prose.
- Distinctive: line 128
Every scene is structurally extractable.
- Distinctive: line 129
All production elements are explicit.
- Distinctive: line 150
Not distinguishing first appearance vs reuse.
≈ “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.
Files
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:
- Read SCENES_v###.csv.
- Review BEATS_v###.md if escalation clarity is needed.
- Confirm scene IDs are stable.
- 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
- Extract explicit elements:
- Characters
- Locations
- Props
- Identify implicit elements:
- Emotional state changes
- Knowledge acquisition
- Injury
- Ownership changes
- Detect first appearances:
- Flag new characters.
- Flag new sets.
- Flag new props.
- Identify continuity risks:
- Time-of-day conflicts
- Wardrobe changes
- Prop disappearance
- Physical impossibilities
- 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
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
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.

