drama-series-writing
Skill7 starsChanged 20 days agoMITView on GitHub
Write a drama series' bible, season arc and episode cliffhangers, from templates or the user's idea.
In this repository69 other files it gives its agents.
- ai-presenterSkill
- animate-designSkill
- app-ui-animationSkill
- asset-auditSkill
- assetsSkill
- background-musicSkill
- caption-decorationsSkill
- character-riggingSkill
- custom-transitionsSkill
- design-layer-importSkill
- edit-footageSkill
- edit-on-your-computerSkill
- edit-pipelineSkill
- face-hidingSkill
- figma-storyboard-animationSkill
- film-animaticSkill
- film-cast-designSkill
- film-cuttingSkill
- film-finishingSkill
- film-shot-generationSkill
- film-story-writingSkill
- footage-analysisSkill
- footage-reframingSkill
- generate-mediaSkill
- get-startedSkill
- large-scene-assemblySkill
- linked-element-motionSkill
- make-cartoonSkill
- make-characterSkill
- make-comicsSkill
- make-screen-videosSkill
- make-short-dramaSkill
- motion-design-craftSkill
- motion-intentSkill
- motion-pattern-librarySkill
- motion-reviewSkill
- motion-scene-continuitySkill
- motion-tracking-from-videoSkill
- movie-producerSkill
- open-picsart-appSkill
- photo-slideshowSkill
- picsart-add-mediaSkill
- picsart-video-rulesSkill
- quality-reviewSkill
- quick-merge-and-exportSkill
- realistic-color-gradeSkill
- recastSkill
- recreate-videoSkill
- reel-structureSkill
- reference-fragment-matchingSkill
- resting-frame-rulesSkill
- retention-hooksSkill
- scene-3d-authoringSkill
- scene-animation-referenceSkill
- scene-building-basicsSkill
- scene-template-remixSkill
- screen-recording-analysisSkill
- screen-recording-layoutsSkill
- screen-recording-zoomSkill
- screen-ui-redesignSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is 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.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 11
Use film-story-writing for scene writing and dialogue.
- Distinctive: line 52
Start with the intended change, then write timed beats.
- Very specific: line 70
Before showing the outline, name the knowledge transfer between tiers, the relationship or power change, and how both the external and …
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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
Drama series writing
A series keeps its promise through changed consequences. Each episode leaves the people in a situation they cannot reset. Write from accepted continuity, never from a discarded draft. Use film-story-writing for scene writing and dialogue. Use retention-hooks for the opening hook.
| File | Read it before you… |
references/templates.md | choose or customize a template, extract a Freeform brief, or research Trending |
references/serialization.md | outline any episode or check its ending against the season |
references/sitcom.md | choose a sitcom or mockumentary incident, or repair its comic turn |
The series bible / Story DNA
Extract the user's choices first. Defaults are suggestions the brief overrides. Preserve a typed profession, setting, language or ending rather than snapping it to a template. Label inferences. Episode count and length are brief decisions; a template's count never settles them.
| Field | Write |
| Brief | Format, audience, episode count and length, language, and whether each episode has a successor |
| Emotional promise | The feeling the viewer returns for; show it at least once in every episode |
| Season question | One question the final episode will answer; its chosen landing and cost |
| Characters | Each person's concrete want, flaw, secret, competence and obsession that causes a bad choice |
| Relationship / power graph | For each principal pair: desire, trust, leverage, debt, shared history and risk |
| Recurring sets | A small reusable set of places, with the work and conflict each makes possible |
| Reveal bank | Hidden facts, their plants, who can learn them, and the reserved midpoint turn |
| Two plots | The external task or deadline and the secret or relationship engine |
| Register | Hook pattern, pacing, romance/comedy/drama levels, visual direction and ending register |
| Theme | Dramatic theme and recurring musical theme: instrumentation, pace and where it returns |
| Caption style | Language, face, weight, contrast, line count and emphasis rule |
Four to six recurring sets and three or four supporting speakers are useful starting budgets. A smaller brief stays smaller. Give the antagonist a want they could state reasonably aloud. Lock the bible before the season arc; customized DNA governs every episode thereafter.
The season arc
Give each episode an incident, want, complication, payoff, continuity delta and ending shape. Reserve major turns rather than spending every secret in the pilot. Track deadlines through their visible expiry or defeat. For 20+ episodes, outline all incidents and script only the next few. Prove the pilot before developing the rest as finished production.
Episode beats
Start with the intended change, then write timed beats. Every beat carries these fields:
| Field | Purpose |
id, start_seconds, end_seconds | Identity and playable time |
action, character_intention | What the viewer sees and what the person tries to get |
resistance | Who or what prevents that intention |
relationship_change | What shifts between people because of the action |
escalation_function | How pressure, knowledge, power or required action increases |
essential_dialogue, silent_reaction | Words that act, and time for the performer to respond |
visual_payload | The fact or action the image must convey |
exit_question | What this beat makes the viewer wait to learn; terminal beats may settle it |
Open conflict or consequential curiosity in the first 3 s. An episode after a cliffhanger opens on its consequence, not its answer or a recap. Answer the prior question no earlier than the second half. Use at most one reveal per serial episode. The protagonist initiates an action nobody asked for; receiving news or asking for explanation does not count.
Before showing the outline, name the knowledge transfer between tiers, the relationship or power
change, and how both the external and secret plots move. Apply the ending rotation and thread
ledger in references/serialization.md. A finale or no-successor episode closes its threads and
ends settled. Do not manufacture a cliffhanger for a standalone, resolved comedy or terminal pilot.
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.

