Skills vs. chat: staying inside the draft
Most AI writing tools bolt a chat window onto the side of a document. You describe what you want, the model writes back a wall of text, and you copy the parts you like into your draft. It works, sort of. It is also the wrong shape for writing, and after building both we are convinced the difference matters more than the model underneath.
Chat-style AI
Inkwell skill pass
Every suggestion is tied to a line in your draft — it lands exactly where it belongs.
Chat puts the AI outside the work
A chat sidebar is a conversation about your screenplay. The AI never touches the actual document — it produces prose in a separate panel that you then have to transcribe, reformat, and reconcile by hand. Every useful suggestion becomes a copy-paste-cleanup chore. Worse, the AI is reasoning about a snapshot it was pasted, not the living structure of your scene. It does not know that EXT. ROOFTOP — NIGHT is a scene heading and ALEX is a character cue; it sees undifferentiated text. So its suggestions arrive as undifferentiated text, and the burden of turning them back into a properly-formatted screenplay falls on you.
This is fine for a one-off question. It is exhausting as a writing workflow, because the tool that is supposed to reduce friction has added a translation layer between the AI and your draft.
A skill operates on the document itself
An Inkwell skill is an agentic pass that reads the structured screenplay — scenes, dialogue, action, character cues — and proposes edits in place, as a reviewable diff. A dialogue pass rewrites lines and shows you exactly what changed, line by line. A continuity check flags the prop that appears in scene 14 but was destroyed in scene 9. A character runner traces an arc across the whole script. The output is not a paragraph to transcribe; it is a set of structured changes you accept or reject like any other edit.
- Scoped to structure — a skill understands what a scene heading, a parenthetical, and a transition are, so it edits the right things and leaves your formatting intact.
- Reviewable — every change lands as a diff against a save point. You see precisely what moved before anything is committed.
- Reversible — accept all, reject all, or take three of seven suggestions. Nothing is applied without your say-so, and a save point is always one click behind you.
Why "inside the draft" is harder — and worth it
Building skills is meaningfully more work than embedding a chat box. The AI has to operate on a real document model, its proposals have to round-trip through the editor as valid screenplay structure, and every change has to be diffable and reversible. A chat sidebar sidesteps all of that by never touching the document — which is exactly why it never has to understand it.
We took the harder path because the easier one quietly offloads the integration work onto the writer. Every "just paste this in" is a small tax, and across a feature draft those taxes compound into a workflow that feels like fighting your tools. Keeping the AI inside the draft moves that cost back to where it belongs: into the software.
So where do open-ended questions go?
This is not an argument against ever thinking out loud with an AI. Open-ended questions — "what genres lean into this structure?", "is this midpoint earning its turn?" — are genuinely conversational, and you can take them to any general-purpose assistant you already use. What Inkwell deliberately does not do is bolt a chat sidebar onto the editor and call it a writing feature. Inkwell's AI surface is skills: agentic passes that read the structured screenplay and return changes you review in place. That is the whole bet — the AI earns its keep by editing the draft, not by talking beside it.
The draft is where the work is. That is where the AI should be too — inside the document, proposing changes you can see, accept, and reverse. A conversation about your screenplay is easy to build and easy to ignore. A pass that lands its suggestions on the exact lines they belong to is harder to build, and much harder to put down.