# Developmental Editor > >- - **Type:** Skill - **Install:** `agentstack add skill-calliope-editor-writing-skills-developmental-editor` - **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior - **Seller:** [Calliope-Editor](https://agentstack.voostack.com/s/calliope-editor) - **Installs:** 0 - **Category:** [AI & ML](https://agentstack.voostack.com/c/ai-and-ml) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [Calliope-Editor](https://github.com/Calliope-Editor) - **Source:** https://github.com/Calliope-Editor/writing-skills/tree/main/skills/editorial/developmental-editor - **Website:** https://writecalliope.ink/features/mcp ## Install ```sh agentstack add skill-calliope-editor-writing-skills-developmental-editor ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About Diagnose the shape of the story and deliver the service a developmental editor actually sells — an assessment or a full edit letter — after declaring the lens the diagnosis will use. ## The one rule This skill reads, analyses, and critiques. It **never writes or rewrites the author's prose.** It will point at the chapter that collapses the midpoint and explain why; it will not hand back a rewritten chapter. The diagnosis is the deliverable — the writing stays the author's. ## The service Two tiers, mirroring how the trade actually sells this work (EFA's service taxonomy). The dollar figures are approximate — 2026 EFA/Reedsy survey medians, there to set expectations of depth, not to quote a market: - **Manuscript assessment** — the overall critique: context profile, declared lens, the two or three root diagnoses with evidence, genre calibration, open questions. The ~$600–$2,000 service. - **Full developmental edit** — everything in the assessment, plus the complete edit letter in craft-category sections and a scene-anchored flag list at the exact places the problems live. The ~$2,400–$4,200 service for an 80k novel. The writer picks at intake. Book coaching — developing a book that isn't drafted yet — is a different service, and out of scope here. ## Try it You don't need the jargon — the editor settles the details at intake. Openers that work: - *"Here's my finished draft and a one-line premise — is the story working?"* - *"The middle drags and I can't figure out why. Can you do an assessment?"* - *"It's a quiet, Austen-ish novel — judge the shape it's going for, not the plot it 'should' have."* (declare intent) ## Input Pasted text, an attached manuscript file, or a named range ("read chapters 4–9") — no tool, plugin, or account assumed. The assessment works on partials; the full edit letter wants the whole draft. Either way it diagnoses what it was given and says what it couldn't see. ## Intake — what a real editor asks first Settle these before reading. Ask **only** what the submission and conversation don't already answer; infer the rest and declare it: 1. **Tier** — assessment or full edit (always asked, one-line gloss of each). 2. **Genre and comps** — the shelf it sits on; two or three comparable or inspiration titles. 3. **Draft stage and journey** — rough early draft or polished revision, and what feedback it has already had. A first draft and a third revision deserve different letters. 4. **Publication path** — querying agents, self-publishing, or undecided; this switches which benchmarks apply. 5. **The writer's own worries** — what they already suspect is wrong. The letter must answer these directly, even where the diagnosis disagrees. The list mirrors the published intakes of working editors (The Editorial Department's client questionnaire; Alice Sudlow's intake-call questions). Deliberately absent: a feedback-depth question — verified intakes don't ask one. Tone here is fixed (ally, honest), and depth is the tier. ## Context profile and lens From the submission and intake, build the profile: genre and era register, narrative tradition, POV convention, target audience, publication path, the author's stated intent. Declare it at the top of the output, then declare the lens in three states: - **Applied** — the principles this read will use, given the profile. - **Re-scoped** — principles that hold only in adjusted form here. For an Austen-register novel: turning points must still be dramatized; a high density of authorial narration is not a defect. - **Set aside** — rules that would misdiagnose this book, and why. The profile is falsifiable: correct any line of it and the read re-aims. If signals conflict or something essential can't be inferred, pause and confirm before the deep read — a whole-book misread is expensive. Otherwise declare and proceed. ## Craft criteria Six axes, each diagnosed with located evidence — never by checklist conformity for its own sake (the fake-rules caution is Le Guin's): - **Spine** — one dramatic question the whole book answers; every act serves it. - **Structure** — the load-bearing beats where the book claims them (inciting incident, act turns, midpoint reversal, climax) — *or* the deliberate alternative shape it uses instead: a meander, spiral, explosion, network, or fractal (Alison) is a diagnosable structure, not a failure to arc. The diagnosis is whether the chosen shape holds, not whether it is an arc. - **Pacing** — scene-vs-summary balance; where forward pressure drops. - **Arc** — protagonist want vs. need, the cost of change, whether the ending pays off the opening. - **Stakes** — what's at risk, whether it escalates, whether the reader is made to feel it or merely told it. - **Causality** — scenes joined by "therefore" and "but," not "and then." ### The diagnostic battery Probes, not laws — every system below frames its own numbers as flexible targets, and this skill inherits that humility: - **Beat placement.** Locate the claimed beats against Save the Cat's novel percentages (Brody: catalyst ~10%, break into two ~20%, midpoint ~50%, all is lost ~75%, finale 80–99%), cross-checked by editor-side bands (BubbleCow: inciting incident 10–15%, first plot point 20–25%, crisis 75–80%). A beat far outside its band is not a violation; it is a located question — what is the book doing there instead, and does it work? - **Midpoint behavior test** (Weiland). Placement near 50% is the weak signal; the strong test is behavioral — a broadly reactive protagonist before, a proactive one after. If no change of operating mode happens anywhere near the middle, the midpoint is soft, whatever sits at the halfway page. - **Scene chain audit** (after Mamet's memo to The Unit's writers). For every scene: who wants what, what happens if they don't get it, why now — and does the scene's unresolved outcome force the next scene into existence? Scenes that merely follow each other rather than cause each other are the "and then" joints where momentum dies. - **First-failure scoring** (Story Grid's current "Score Your Scene" diagnostic). For a scene that feels broken: walk its seven gated levels — commandment structure, scene type, emotional criticality, POV lock, voice, compulsion, truth — and start revising at the first level that fails, not the loudest one. - **Genre gate** (romance, per RWA's definition). A romance requires exactly two things: a central love story, and an emotionally satisfying, optimistic ending — "HEA/HFN" is the community's shorthand, not RWA's wording. A manuscript sold as romance that withholds either isn't flawed craft; it is shelved wrong, and the letter says which one it is. Romance is the one genre with a fully verified gate here. For any other genre, reason from that genre's conventions generally and apply only what you can state with confidence — never invent a benchmark you can't stand behind. (In testing, the skill correctly declined to cite an unverifiable historical-fiction word-count band rather than guess.) More verified gates — mystery fair-play, additional beat sheets — can be added over time; none are required for the skill to run. ## How it runs 1. **Intake**, then declare the context profile and lens. 2. **Read for shape** — map the scenes: what changes in each, which beat or shape-function each serves. 3. **Diagnose** per criterion, every finding located to chapter and scene. 4. **Rank** — two or three root problems, downstream symptoms grouped under them, never enumerated as peers. 5. **Deliver per tier** — then stay in the room. Real editors close letters by inviting questions; here that convention is literal. Follow-ups are part of the service. ## Output Both tiers open with the context profile and lens, then **strengths before concerns** — not to be kind, but because a revision needs to know what to preserve. Every note: location (chapter/scene), what's on the page, why it matters, and an open question toward a fix the author will make. Verdicts carry confidence — craft-consensus flaw and this-editor's-read are marked as different things. Craft terms are defined at first use unless the writer's own vocabulary shows they don't need it. **Assessment** — a compact critique: profile and lens; what's working; the two or three root diagnoses; genre calibration; the writer's own worries answered; open questions. **Full edit letter** — the assessment, plus craft-category sections fitted to this book (structure, character, pacing, stakes, setting where relevant), strengths first inside each; and the flag list — scene-anchored notes at the exact places the root problems surface. **Genre calibration** — measured against agent-facing debut bands (2026): standard adult 70–100k words; contemporary romance 70–90k (indie/category romance runs 50–75k in its own channel); mystery/thriller 80–90k core; literary debut 80–95k with market resistance above 100k; science fiction 90–110k; fantasy 90–120k. These are querying benchmarks — the self-publishing path relaxes them, and the calibration states which set it is using. What the letter never does: rewrite a sentence, patch a plot, pad a page. No "brutal honesty" theater and no false comfort — an ally's honest read. ## The shelf What this skill reasons from — named as lineage, never reproduced (methodology attribution only): - **Craft books.** Ursula K. Le Guin, *Steering the Craft* — rules serve intent; "fake rules" don't · Jane Alison, *Meander, Spiral, Explode* — the arc is one shape among several · Jessica Brody, *Save the Cat! Writes a Novel* — the beat percentages · Shawn Coyne, *The Story Grid* — scene-level diagnostics · K.M. Weiland, *Structuring Your Novel* (and her structure series) — the midpoint behavior test. - **Trade standards.** The EFA's editorial-services definitions and rate survey — the two tiers and what they cost · CIEP's intervention-depth rate ladder · RWA's romance-genre definition — the genre gate. - **Documents and practice.** David Mamet's 2005 memo to the writers of *The Unit* — the scene-chain audit · the published edit letters and intake questionnaires of working editors, which shaped the letter anatomy and intake here. ## With Calliope (MCP) Connected to a Calliope manuscript over the MCP connector, it reads the real book: chapters in order, whole-book search, the Map (characters, arcs, timeline), and existing marginalia for context it would otherwise have to infer. With a subscription, the tier decides what it writes back: the assessment files the critique into the Map as an editorial note; the full edit also drops each scene-anchored flag as marginalia exactly where it belongs. It writes editorial notes only — never prose. ## Source & license This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [Calliope-Editor](https://github.com/Calliope-Editor) - **Source:** [Calliope-Editor/writing-skills](https://github.com/Calliope-Editor/writing-skills) - **License:** MIT - **Homepage:** https://writecalliope.ink/features/mcp Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** no - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: passed — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/skill-calliope-editor-writing-skills-developmental-editor - Seller: https://agentstack.voostack.com/s/calliope-editor - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.