scene-breakdown
Skill0 starsChanged 41 days agoMITView on GitHub
Break a script or scene into a production breakdown (location, time of day, cast, props, sound, VFX, lighting needs, risks) and suggest an efficient shooting order. Use when the user is preparing a shoot, scheduling, budgeting or doing a script breakdown.
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 repository4 other files it gives its agents.
- color-scriptSkill
- cut-listSkill
- export-checklistSkill
- shot-listSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
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 16
If not provided, ask once (max 3 questions in one message):
- Distinctive: line 22
If the user says "just do it", state assumptions in one line and continue.
- Distinctive: line 51
Keep it scannable. This is a working document, not prose.
≈ “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
Scene Breakdown
Turn script pages into a breakdown sheet a small crew can plan a shoot from.
Inputs to collect
If not provided, ask once (max 3 questions in one message):
- The script or scene text (required)
- Practical limits: number of shoot days, locations available, crew size, gear
- Delivery format and target runtime
If the user says "just do it", state assumptions in one line and continue.
Process
- Split the material into scenes (one per location/time change).
- For each scene extract only what is in the text: never invent props, characters or locations.
- Flag hidden costs: night shoots, exteriors that depend on weather, crowds, minors, animals, stunts, VFX, copyrighted music or logos visible on screen, permits.
- Group scenes by location and lighting to propose an efficient shooting order (not story order).
- Give each scene a complexity rating (Low / Medium / High) with a one-line reason.
Output format
Scene table
| Sc. | Slug (INT/EXT. LOCATION - TIME) | Cast | Props / wardrobe | Sound / music | VFX / special | Lighting needs | Complexity |
Risks and unknowns
A short list of items that could break the schedule, each with a cheaper alternative if one exists.
Suggested shooting order
Group by location/light. Show the grouping logic in one line per group, not a long essay.
Shopping / prep list
Props, permits, releases and gear to confirm before day one.
Rules
- Extract from the text only. If something is ambiguous, list it under "Unknowns" instead of deciding for the user.
- Keep it scannable. This is a working document, not prose.
- Mention legal checkpoints (location permits, actor releases, music rights) as reminders, not as legal advice.
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.