Writes editorial script notes for screenwriting drafts, identifying structural, character, and scene-level issues in a professional development executive format. Useful for writers, producers, and script editors needing structured feedback.
How this skill is triggered — by the user, by Claude, or both
Slash command
/autopunk-media-skills:script-notes-writerThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Writes a detailed set of editorial script notes for a specific draft, identifying structural problems, character issues, and scene-level fixes in the format used by development executives and experienced script editors.
Writes a detailed set of editorial script notes for a specific draft, identifying structural problems, character issues, and scene-level fixes in the format used by development executives and experienced script editors.
Required: Detailed act-by-act story breakdown including character arcs; title, format, draft number; the specific problems the writer or editor is most concerned about (even if vague — "Act 2 drags" is useful context) Optional: The draft's stated goals ("this draft was supposed to fix the protagonist's passivity"); what the previous draft's problems were; whether the writer is early in development (broad structural notes) or late (fine-tuning notes); any scenes or elements the writer considers fixed and does not want notes on
Four sections: Root Issue (1 short paragraph stating the central problem plainly), Structural Notes (3–6 numbered notes on acts and turning points), Character Notes (one short paragraph per major character, noting arc status and any consistency issues), Scene Notes (numbered, each citing the specific scene or sequence, the problem, and a suggested direction), Priority List (numbered, 3–5 items, ordered by impact). Total length: 700–1,000 words. Tone: collegial, direct, specific. Notes are addressed to the writer ("you" or "the writer") and assume the writer is capable and wants to improve the draft.
Title: FALLBACK POSITION Format: Feature film, 104 pages Draft: Second draft Genre: Workplace drama / dark comedy Writer concern: "Act 2 loses momentum and the protagonist, Bex, goes passive. Also not sure the ending works." Story breakdown:
SCRIPT NOTES — FALLBACK POSITION (Second Draft)
Root Issue
The draft's central problem is that Bex's agency has been structurally removed in an attempt to solve an earlier draft's over-resolution. In the first draft, the big speech gave her too much power; in this draft, the three dead-ending investigation routes in Act 2 leave her with none. The result is a second act in which a capable, principled character tries three things and fails three times without any sense of escalation or learning — and arrives at the film's climax by running out of options rather than making a choice. The ending doesn't feel deflating because it's quiet; it feels deflating because it doesn't feel earned. The fix is not to restore the speech. It's to give Bex one real decision to make in Act 2 that costs her something — and let the leaked white paper be the consequence of that decision, not a last resort.
Structural Notes
Act One end (approximately p. 25): The committee date being moved works as a first disturbance but it is too passive as an Act One break. Bex reacts to the delay rather than making a choice in response to it. Consider giving her one moment at the end of Act One where she decides to investigate rather than accept the explanation — this makes the Act Two inquiry her initiative, not her reaction.
Midpoint (approximately p. 55): Currently, the Midpoint is Rhys telling Bex she has no actionable evidence. This is a closed door, not a pivot. A Midpoint should reframe the question, not shut the investigation down. Consider rewriting the Rhys conversation so that he tells her something she didn't know — something that changes what she's looking for, even if it doesn't give her what she needs.
Act Two investigation sequence (pp. 40–75): The three dead-ends are structurally equivalent in shape (Bex tries, hits wall, sits at desk). They don't escalate. Each attempt should cost something incrementally — a relationship strained, a professional risk taken, something personal revealed — so that by the time Bex is out of official routes, the audience understands what she has already sacrificed.
Act Three decision (p. 85): Bex sending the annotated white paper is the right ending. The problem is the framing: it currently reads as a surrender (she sends it and goes home, exhausted) rather than a decision. The same action can read as a deliberate, costly choice if what precedes it is a scene in which she explicitly weighs what she's about to lose. Let the audience be inside the decision, not just witness the result.
Title card ending: The director's resignation revealed by title card is a common choice for procedural dramas and it works as a device, but at present it arrives before the audience has time to sit with what Bex's decision cost her personally. Consider whether there is a final scene — brief, one location — before the title card that shows where Bex is, not where the institution is.
Character Notes
Bex: Her intelligence and commitment are well-established in Act One and her dry internal monologue (rendered through her glances and timing) is the best thing in the script. Her passivity in Act Two is not a character problem — it's a structural one. She has been written into a position where all her options are closed before she can exercise judgment. The fix is structural, not character-based.
Rhys: Sympathetic-but-useless colleagues are a well-worn type and Rhys is currently filling the slot without adding to it. He is most interesting in the single moment where he hesitates before giving Bex the official line — suggest expanding that hesitation into a scene that earns his presence in the story. Does he know more than he says? If so, why doesn't he say it? If not, what is he protecting?
The Director: Offscreen for most of the film, which is an interesting choice that works if the audience understands what kind of person is making these decisions. At the moment the Director is functional (we understand what he's doing) but not legible (we don't understand how he sleeps). One scene — even a brief one in which he performs normalcy around the climate initiative in front of Bex — would give the film a sharper antagonist without needing to make him a villain.
Scene Notes
The FOI sequence (pp. 60–64): This scene is currently the weakest of the three dead-ends because it resolves entirely off-page. Bex applies, we cut, she receives the heavily redacted response. The comedy of the redactions is good but underdeveloped. If this scene is going to be in the film, commit to it — let it breathe, let Bex read it in real time, let us watch her figure out what the redactions confirm rather than what they reveal.
The journalist meeting (p. 68): This scene is doing two jobs — Bex tests the journalist's trustworthiness AND decides not to hand anything over — and the second decision is currently implicit. It should be explicit. We need to see Bex make the calculation about why she holds back, not just observe that she does.
The evening before the leak (pp. 87–89): Currently three pages of Bex at home, restless, at her laptop. This is the most important scene in the film — the moment she crosses from deliberating to deciding — and it needs a clearer dramatic beat. Consider introducing a specific interruption or trigger: a notification, a call, something from outside that tips the balance. Not to make the decision feel reactive, but to mark the moment it becomes irreversible.
Priority List
npx claudepluginhub ur-grue/autopunk-media-skills --plugin autopunk-media-skillsProduces a script coverage report with logline, synopsis, scored breakdown, and evaluation of premise, structure, character, dialogue, and marketability. Useful for producers, execs, readers, and screenwriters who need standardized industry-format coverage.
Guides building three-act screenplay structure with inciting incident, midpoint, and character arc. Useful for film/TV writing projects.
Reviews scriptwriting for story completeness, pacing, character consistency, and ending execution. Used by a Director agent to check scripts and provide revision notes.