scene-writing
Write individual screenplay scenes with proper industry formatting, visual action, and dramatic structure
Best use case
scene-writing is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Write individual screenplay scenes with proper industry formatting, visual action, and dramatic structure
Teams using scene-writing should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/scene-writing/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How scene-writing Compares
| Feature / Agent | scene-writing | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Write individual screenplay scenes with proper industry formatting, visual action, and dramatic structure
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Scene Writing Skill
## Purpose
Write individual screenplay scenes that advance the story, reveal character, and engage the reader. Each scene should be a complete dramatic unit with its own structure, conflict, and resolution.
## Scene Anatomy
### The SCENE Framework
| Element | Description |
|---------|-------------|
| **S**pacing | INT/EXT, Location, Time |
| **C**haracter | Who's in the scene, POV |
| **E**motion | Underlying tension, stakes |
| **N**arrative | Information delivered |
| **E**xit | How we leave, hook to next |
## Screenplay Format (Fountain)
```fountain
INT. POLICE PRECINCT - INTERROGATION ROOM - NIGHT
Harsh fluorescent light. Bare walls. A metal table bolted to the floor.
DETECTIVE SARAH CHEN (40s, tired eyes, sharp mind) sits across from MARCUS WEBB (30s, expensive suit, expensive smile).
A manila folder between them like a dare.
SARAH
You know why you're here.
MARCUS
(leaning back)
Enlighten me.
Sarah opens the folder. Crime scene photos. Blood. Chaos.
SARAH
Your fingerprints. Her blood.
Her dying breath, calling out
your name.
Marcus doesn't flinch. His smile never wavers.
MARCUS
Detective... I have an alibi.
SARAH
So did every guilty man I ever caught.
She slides one photo across the table. Marcus looks at it.
For just a moment—something flickers in his eyes.
MARCUS
I want my lawyer.
Sarah smiles. Finally. A crack.
```
## Formatting Rules
### Slugline (Scene Heading)
```
INT. or EXT.
LOCATION NAME (in caps)
TIME OF DAY (DAY, NIGHT, CONTINUOUS, LATER, SAME)
```
Examples:
- `INT. COFFEE SHOP - DAY`
- `EXT. BROOKLYN BRIDGE - NIGHT`
- `INT./EXT. CAR (MOVING) - CONTINUOUS`
### Action Lines
- Present tense, active voice
- 3-4 lines max per paragraph
- WHITE SPACE for pacing
- CHARACTER NAMES in CAPS on first appearance
- Sounds in CAPS (BANG, CRASH)
- Only describe what we SEE and HEAR
### Dialogue
- Character name centered, ALL CAPS
- Parentheticals (sparingly) for tone/direction
- Dialogue left-aligned under name
- Keep speeches short—film is visual
### Transitions
- Use sparingly: `CUT TO:`, `SMASH CUT TO:`, `DISSOLVE TO:`
- Most scene changes are implied cuts
- `FADE IN:` at start, `FADE OUT.` at end
## Scene Structure
### Mini Three-Act
Every scene has its own structure:
**Beginning (10%)**
- Establish location/time
- Character enters situation
- Scene goal introduced
**Middle (80%)**
- Conflict develops
- Stakes escalate
- Complications arise
- Information delivered
**End (10%)**
- Scene climax
- Value shift
- Hook to next scene
### Value Shift
Every scene should shift a value:
- Hope → Despair
- Trust → Suspicion
- Power → Vulnerability
- Ignorance → Knowledge
## Scene Types
### Dialogue Scene
- Characters talking
- Subtext underneath
- Physical action woven in
- Avoid "talking heads"
### Action Scene
- Visual storytelling
- Minimal dialogue
- Clear geography
- Beat-by-beat choreography
### Montage
- Series of shots
- Passage of time
- Unified by theme or music
- Each shot advances story
### Intercut
- Parallel action
- Multiple locations
- Build tension through comparison
- `> INTERCUT - LOCATION A/LOCATION B`
## Writing Tips
### Pacing
```
Fast pace:
- Short sentences.
- Fragments.
- White space.
- Action verbs.
Slower pace:
The room settles into silence. Dust motes drift through the
shaft of light from the window. Somewhere, a clock ticks.
```
### Visual Writing
**Instead of:** "John is sad about his breakup."
**Write:** "John sits alone at a table for two. An untouched birthday cake. Two candles, unlit."
### Subtext
**On the nose:** "I'm angry at you for lying!"
**Subtext:** "Did you have a nice evening?"
## Scene Checklist
- [ ] Does the scene advance plot?
- [ ] Does it reveal character?
- [ ] Is there conflict?
- [ ] Does a value shift?
- [ ] Could any lines be cut?
- [ ] Is there subtext?
- [ ] Does it end with a hook?
- [ ] Is formatting correct?
## Common Mistakes
1. **Overwriting** - Trust the reader
2. **Camera directions** - Not your job
3. **Internal thoughts** - Can't be filmed
4. **Too much dialogue** - Show, don't tell
5. **No conflict** - Every scene needs tension
6. **Weak endings** - End on strength
## Output Format
```fountain
INT. [LOCATION] - [TIME]
[Opening action/description - 2-3 lines]
[CHARACTER NAME] ([age, brief description]) [action].
[CHARACTER]
[Dialogue]
[Action/response]
[OTHER CHARACTER]
([parenthetical])
[Dialogue]
[Scene climax/turning point]
[Exit action - hook to next scene]
```Related Skills
tech-writing-lint
Automated technical writing style and quality enforcement. Lint documentation with Vale, check for inclusive language, enforce style guides, and analyze readability metrics.
tech-writing-linter
Lint technical documentation for style, consistency, and readability
academic-writing-publication
Prepare manuscripts following APA, ASA, or discipline-specific guidelines with proper reporting standards and peer review navigation
philosophical-writing-argumentation
Compose clear, rigorous philosophical prose with well-structured arguments, anticipation of objections, and proper scholarly engagement with existing literature
grant-narrative-writing
Compose compelling research narratives for NEH, ACLS, and foundation funding proposals with clear significance statements
learning-objectives-writing
Write measurable, SMART learning objectives using Bloom's Taxonomy cognitive levels aligned with desired outcomes and assessment strategies
interpretive-writing
Create accessible interpretive content for diverse audiences including labels, wall text, catalog essays, educational materials, and digital content
grant-proposal-writing
Develop compelling funding proposals for foundations, government agencies, and corporations including narrative development, budget creation, and compliance documentation
lyric-writing
Write complete song lyrics with structural annotations and production notes optimized for AI music generation platforms like Suno and Udio
treatment-writing
Develop narrative synopses that tell the complete story cinematically, serving as sales documents and production blueprints
logline-writing
Craft compelling one-sentence story hooks that capture protagonist, conflict, stakes, and unique appeal for film/TV pitches
academic-writing-assistant
Skill for assisting with academic and scientific writing