Screenplay / Script is a Claude AI skill — produces dramatised scenes with proper format, character-driven subtext, and structure calibrated to your genre, format, and stage of development.
There's a test every screenplay reader applies without naming it. They read the first page of action and ask: is this dramatised or described? Described means the writer is telling us what happens — the character does this, then that, then the other thing. Dramatised means we're inside the scene, watching behaviour that reveals something about the character without the writer explaining it. One is a summary. The other is a script.
Generic AI produces the first. Reliably. Ask it to write a screenplay scene and it produces correctly formatted text — slug lines, action blocks, dialogue indented at the right margins — that reads as a description of what a scene might look like rather than the scene itself. The action lines explain emotion rather than showing behaviour. The dialogue says what characters mean rather than what they'd actually say. The formatting is correct. The craft isn't there.
This isn't a failure of effort. It's a structural limitation. Good screenplay writing requires knowing several things that a generic prompt doesn't capture: what the scene needs to accomplish within the larger structure, what the characters want and what they're hiding, which genre conventions are currently active in the market versus which ones are exhausted, and how professional action writing works — what it includes, what it leaves out, how much white space a page should have. Without all of those inputs, generic AI defaults to the descriptive mode, because description is what it knows how to produce.
What Description Sounds Like on the Page
The descriptive mode has a specific texture. Action lines that report emotion: "Sarah feels nervous as she walks into the room." Dialogue that states the subtext directly: "I don't know if I can trust you anymore." Characters who do exactly what the scene needs them to do, in the order the plot requires, without the friction and misdirection that makes behaviour feel real. Scene endings that resolve rather than turn — wrapping up what just happened instead of twisting toward what happens next.
None of this is wrong, exactly. A scene written this way conveys the information. A reader who finishes it knows what happened. But knowing what happened and experiencing what happened are different things, and only the second one keeps a reader turning pages or a viewer in their seat. The gap between them is the gap between a competent scene and a compelling one — and it's the gap that most AI-generated screenwriting falls into without noticing.
Generic AI knows what screenplay format looks like. It doesn't know how to use behaviour to reveal character, how to write subtext into dialogue, or how to end a scene on a turn rather than a resolution. The output is a script-shaped document, not a script.
There's a second layer: format conventions shift. What professional feature scripts looked like five years ago is not what they look like now. Scene length, action line density, the use of white space, how much description is acceptable versus what reads as overwriting — these norms evolve continuously as the industry reads more, produces more, and develops collective taste about what signals a professional page. Generic AI reaches for the average of everything it was trained on, which includes a lot of outdated convention. Live research on current spec script norms is what separates a page that reads as contemporary from one that reads as five years behind.
What Structure and Subtext Research Changes
Before the NovaKit Screenplay skill writes an action line, it establishes the scene's dramatic context: what the scene needs to accomplish structurally, what each character wants and what they're concealing, and where the scene needs to turn rather than resolve. That context changes everything that follows — because a scene written with a clear dramatic question produces different dialogue, different behaviour, and a different ending than a scene written as a plot delivery mechanism.
The skill also researches current format conventions for the genre and format being written — feature film, TV pilot, short, or web series each have distinct contemporary norms around page density, scene length, and action writing style. A contemporary drama script reads differently from a contemporary thriller, which reads differently from a prestige TV pilot. These aren't arbitrary preferences — they're professional signals that tell a reader immediately whether the writer knows the current landscape of the form they're working in.
A screenplay scene is not a description of what happens. It is behaviour under pressure — and the pressure, the behaviour, and what they reveal about character is what makes a page worth reading.
The skill's calibration to stage of development matters specifically for writers using it in their process. A first-draft scene needs different things than a polish pass — in the first draft, the goal is establishing the dramatic logic and character behaviour; in a polish, the goal is finding the subtext in lines that currently say too much and the economy in action blocks that currently overexplain. The skill adjusts to which of those problems it's being asked to solve.
What the Screenplay Skill Produces
The skill's interview covers five inputs: the premise and genre, the characters in the scene and what each one wants and is hiding, the scene's position in the larger structure, the format (feature, TV, short, web), and the development stage. From those:
Descriptive Script vs Dramatised Scene
Same setup — two colleagues, one of whom has just discovered the other has been taking credit for her work, meeting in a hallway before a presentation — written two ways. The scene information is identical. The craft is not.
SARAH walks quickly toward the conference room. She feels angry and betrayed after what she discovered. MARCUS spots her and approaches, looking nervous.
MARCUS
Sarah, wait. I need to talk to you.
SARAH
(angry)
I know what you did, Marcus. You took credit for my work. How could you do that?
MARCUS
I can explain. It wasn't supposed to happen that way.
Sarah shakes her head, feeling hurt and disappointed. She walks away, leaving Marcus standing alone in the hallway, feeling guilty.
The presentation boards are visible through the glass. Sarah's name is not on them.
SARAH moves fast, laptop under one arm, coffee untouched in her hand. Marcus steps out of the men's room, sees her, stops.
A beat. She doesn't slow down.
MARCUS
Hey — five minutes before we—
SARAH
I saw the deck.
She keeps walking. He falls in beside her.
MARCUS
The Hendricks notes — I meant to add your name, it just—
SARAH
(still moving)
Don't.
She pushes through the conference room door. Marcus stands in the hallway.
Through the glass: Sarah sets her laptop on the table, smiles at the clients, says something that makes them laugh.
Marcus watches her work.
The descriptive version reports what's happening and labels the emotions explicitly. The dramatised version removes every label — "angry," "guilty," "nervous" — and replaces them with behaviour: the untouched coffee, the pace that doesn't slow, the one-word line that shuts down the conversation. The scene's emotional content is identical. The reader's experience of it is completely different. In the first version, we're told Sarah is angry. In the second, we watch her not slow down — and that's worse for Marcus than anything she could have said.
Who Gets the Most from This Skill
Screenwriters who know their story but find individual scenes hard to crack — the skill gives them a dramatised starting point with the structure and subtext already established, which is faster to edit than to build from nothing. Writers new to the form who need to learn professional format and craft simultaneously — the scene notes explain the choices so the output is educational as well as useful. Novelists and playwrights adapting their own work into screenplay format, where the challenge is translating interiority into observable behaviour.
The skill is not a replacement for the writer's voice — the output is a starting point, and the best use of it is as a structural scaffold that the writer then inhabits, rewrites, and makes their own. What it removes is the blank-page problem and the format uncertainty: you have a correctly structured, properly formatted, dramatised scene to react to rather than a blinking cursor and a plot point you need to turn into pages.
The Output You Walk Away With
A complete formatted scene — slug line through button — with behaviour-driven action writing, subtextual dialogue, a clear dramatic turn, and contemporary format conventions applied throughout. Scene notes identifying the structural choices, the subtext mechanics, and the points in the scene designed for the writer to take in a different direction. Ready to paste into any screenwriting application, use as a structural reference, or rewrite as the starting point for the scene you actually want.
Most writers use the skill when a scene has been sitting unwritten for days because the dramatic logic isn't clear — when they know what needs to happen but not how to make it happen dramatically. Five inputs and one run later, they have a scene that works structurally, which gives them something concrete to agree with, argue with, and improve. That's a faster path to the scene they want than staring at the scene heading.
A script is not a story with formatting. It's a set of instructions for producing an experience — and every word on the page is either producing that experience or getting in its way. The skill writes pages that do the first.
The next piece most people tackle from here is a book cover brief that works before the title is read.