AI-Powered Story Diagnostics

Literary agents don't tell you
why they said no.

StoryGecko does.

Every rejection from a literary agent says the same thing. "Not right for my list." "Doesn't align with what I'm looking for." Nothing useful. Nothing actionable. Just silence where feedback should be.

And for self-published authors? Strong plots and compelling characters still struggle on Amazon — because structure shapes whether readers stay immersed, keep turning pages, and leave five-star reviews.

StoryGecko runs a chapter through 9 diagnostic agents — checking tension, escalation, stakes, causality, dialogue, pacing, voice, and theme — and tells writers exactly what a professional reader would flag.

StoryGecko
Beta

StoryGecko is currently in private beta. Writers with access can sign in below — or email mark@storygecko.com to request access.

Sign In to StoryGecko →

One tool. Comprehensive insight.

A diagnostic that tells you exactly what's wrong — chapter by chapter, issue by issue.

StoryGecko 1 — Chapter Diagnostic

Find out what a professional reader would flag

Nine specialized agents check your chapter for tension, stakes, pacing, dialogue, voice, cause-and-effect logic, and more. A synthesis agent compiles every finding into one structured report with severity tiers and specific, actionable guidance grounded in your actual text.

  • 9 diagnostic agents run in parallel
  • Critical / High / Moderate / Polish severity tiers
  • Grounded observations — no generic advice
  • Genre-aware across 12 fiction categories
Access StoryGecko 1

The rejection letter that tells you nothing

From: Literary AgentRe: Your Submission

"Thank you for submitting your manuscript. Unfortunately, this project isn't quite right for my list at this time. I wish you the best of luck placing it elsewhere."

No reason given. Was it the premise? The pacing? The dialogue? The stakes? You'll never know.
No direction forward. Writers revise in the dark, fix the wrong things, and resubmit to the same result.
No craft feedback. The first chapter signals everything to a literary agent — and most writers don't know which signals they're sending.
No second chance. Most agents won't look at a revised manuscript. The first submission is the only submission.

Strong characters. Compelling plot. Struggling on Amazon.

Self-published authors with genuinely good stories sometimes can't gain traction — not because readers don't exist, but because story structure shapes whether readers stay immersed, finish the book, and come back for the next one.

Structure drives reader immersion

Research on narrative transportation theory shows that readers become immersed — and stay immersed — when a story flows logically, events follow causally, and emotional stakes are clear. Structure is the engine beneath immersion.

Clarity keeps readers turning pages

Studies on readability and cognition show that poor structure creates friction — even when the prose is good. Readers who feel confused or unstuck quietly stop reading. Strong structure removes that friction.

Engagement leads to satisfaction

A 2024 study on narrative structure found it improves comprehension, increases motivation to keep reading, and enhances emotional impact. Readers who finish a book satisfied leave reviews. Readers who drift away don't.

The research is direct

Studies on structured storytelling systems show 10–50% improvements in story quality and measurable increases in reader engagement. StoryGecko applies the same structural principles — chapter by chapter, issue by issue.

"Improving story structure increases reader engagement and emotional impact. Clear narrative structure improves comprehension and reduces reader friction. Well-structured stories are more immersive — and more satisfying — to read."
— Supported by research in narrative transportation theory, readability cognition, and structured storytelling systems

The first chapter tells a literary agent everything

Within the first chapter, an experienced agent is reading for dozens of structural signals. Most writers know these rules exist. Almost none can hold all of them in their head while writing. StoryGecko holds them for you.

01
Tension & Escalation
Does pressure build? Does each scene leave the protagonist worse off than when it started?
02
Stakes & Consequences
What does the protagonist stand to lose? Are the consequences real and personal?
03
Cause & Effect Logic
Do character choices drive outcomes, or do things just happen?
04
Scene Purpose
Does every scene change the situation? Or does the story pause while things are described?
05
Internal Conflict
Is there friction between what the character wants and what they fear?
06
Dialogue & Subtext
Do characters talk past each other with competing wants, or just exchange information?
07
Voice & Theme
Does the narrative voice feel specific and alive? Is the thematic argument operating in action?
08
Genre Conventions
Is the chapter meeting the specific structural promises of its genre?
09
Reader Momentum
Is there a question pulling the reader forward, or does the chapter close without pressure?

Nine agents. One comprehensive diagnostic.

StoryGecko runs nine specialized diagnostic agents in parallel — each focused on a different craft dimension — then synthesizes their findings into a single, actionable report.

01

Author submits a chapter

The writer pastes or uploads their chapter, selects their genre, and optionally notes any intentional choices they want StoryGecko to skip.

02

Nine agents run in parallel

Each agent is specialized: one reads for stakes, one for scene purpose, one for cause and effect, one for dialogue, one for theme. All nine run simultaneously in 15–30 seconds.

03

A synthesis agent compiles the report

A tenth agent reviews all nine findings and produces a structured diagnostic report: Critical issues, High Impact risks, Moderate observations, and Polish items — with specific, actionable guidance for each.

What a StoryGecko report looks like

Every report is specific to the chapter — not generic advice, but grounded observations tied to actual moments in the text. This is a real diagnostic run on Chapter 1 of The Hunger Games.

StoryGecko Chapter Diagnostic
Chapter 1 of 27 · Early Setup · Young Adult · 9 diagnostics run
0
Critical
2
High Impact
3
Moderate
3
Polish
What's Working Well
Premise Detonation With Earned Force
You establish Katniss's love for Prim through action (the cheese, the protective gestures) before using it as the chapter's emotional bomb, which makes the final line land with genuine devastation rather than manipulation.
World Texture Before World Explanation
You give us coal dust, illegal hunting, and the tessera system through lived detail rather than exposition dumps, so readers experience District 12's oppression in their bodies before they understand it intellectually.
Subtext-Rich Conflict In The Madge Exchange
The conversation about the dress and pin lets Gale, Madge, and Katniss all argue about class injustice without anyone stating it directly, which creates the kind of dangerous social tension where every word has weight.
Identity Constraint As Survival Tool
Katniss's learned ability to hold her tongue and mask her thoughts isn't just characterization — it's the skill that keeps her alive, which makes emotional suppression feel like genre-appropriate stakes rather than withholding.
The Cat Memory As Moral Complexity
The Buttercup drowning attempt demonstrates that Katniss is willing to kill to reduce mouths to feed, then positions her current truce with the cat as the closest she gets to love — a genuinely dark relationship calculus that establishes her survival pragmatism without apologizing for it.
Critical Risks — Fix Before Moving On
No critical issues here — you're in good shape for this stage of the story.
High-Impact Risks — Address in This Draft
Energy Plateau
Woods interlude releases reaping pressure
The issue:
You open with "This is the day of the reaping" to establish governing dread, but the hunting/trading sequence feels like comfortable routine rather than mounting terror, which might make readers uncertain whether they should be relaxing or tightening.
One thing to try:
Consider letting Katniss's reaping fear infiltrate the woods moments — maybe she misjudges a shot because her hands are shaking, or she catches herself calculating Prim's odds while skinning a squirrel.
Internal Conflict Not Visible
Emotional suppression might read as emotional absence
The issue:
You show Katniss performing control ("I force myself to stay calm") rather than rendering what it costs her to maintain that mask, which might make readers see the strategy but not feel the internal war.
One thing to try:
Think about giving us a physical tell when she's suppressing something unbearable — a sensation in her chest, a taste in her mouth, something that leaks through even when her face stays blank.
Worth a Closer Look — Consider in Revision
Scene Has No Purpose
The "leave the district" conversation starts and stops
The issue:
Gale proposes escape, Katniss calls it preposterous, and within seconds Gale himself dismisses it, which might make the exchange feel like a false choice designed to reveal character attitude rather than force a decision with consequence.
One thing to try:
Consider letting this disagreement leave visible residue — maybe Katniss spends the rest of the day wondering whether Gale was serious, or whether she dismissed something she secretly wants.
Protagonist Too Passive
Katniss has no agency in the reaping mechanism
The issue:
The reaping functions as pure lottery — Katniss can't act to reduce her risk or Prim's once the chapter's present timeline begins, which might make her feel structurally passive in the face of the chapter's central threat.
One thing to try:
It might help to let her make one small choice under constraint during the ceremony itself — where she stands, whether she looks at Prim, something that won't change the outcome but shows her trying to exert control over the uncontrollable.
Character Motivation Unclear
Gale's escape proposal feels unmotivated
The issue:
The conversation about running away arrives without visible buildup or triggering event in the scene, which might make readers wonder whether this is something Gale has been thinking about for months or something the chapter needed to happen.
One thing to try:
Consider planting earlier behavioral signals that Gale is unusually rattled today — maybe he's more reckless in the woods, or he keeps checking the sun's position like he's dreading going back.
Small Polish Items — Polish Pass at the End
The phrase "his rages seem pointless to me, although I never say so" tells us about unspoken conflict between Katniss and Gale but doesn't let us see a moment where she bites her tongue — consider showing her suppress the urge to tell him to shut up during one of his rants.
When Katniss describes Gale's attractiveness to other girls, it might clarify whether she's genuinely oblivious to romantic implications or actively choosing not to engage with them — right now it could read either way.
The line "Are you sure?" when her mother offers the dress could be strengthened by showing what Katniss is afraid of — is she worried her mother will regret the offer, or worried she'll accept help and then her mother will disappear again?
StoryGecko diagnostic · storygecko.com · Sample output — The Hunger Games, Chapter 1

License StoryGecko for your platform

StoryGecko is built for platform licensing. Writing platforms, publishing tools, and literary communities can offer StoryGecko's diagnostic engine to their users — under their brand, on their infrastructure.

Genre-calibrated frameworks

12 genre frameworks — each one a proprietary diagnostic lens that calibrates agent behavior to the specific structural expectations of that genre and story position. No other tool does this.

White-label ready

The diagnostic engine runs on your API key. Your brand, your interface, your users — StoryGecko provides the IP: the agent architecture, the genre frameworks, and the synthesis logic.

Extensible platform architecture

The diagnostic engine is the foundation. The agent architecture and genre frameworks are designed to support additional tools and workflows as the platform grows.

Built for writers who take their craft seriously

Querying Authors

Writers preparing manuscripts for literary agent submission who need to know what a professional reader would flag — before the rejection arrives.

Self-Published Authors

Independent authors who want their books to perform on Amazon — and understand that structure is what separates immersive reads from books readers abandon at chapter three.

Writing Platform Users

Writers on platforms like Scrivener, NovelAI, or Reedsy who want professional-grade diagnostics built into their existing workflow — without switching tools.

Serious Craft Practitioners

Writers who've read the craft books, taken the workshops, and know the rules — but need an outside eye to tell them where their chapter is and isn't executing.

Let's talk about what StoryGecko can do for your platform.

We're currently exploring partnership opportunities with writing platforms, publishing tools, and literary communities. If your users are writers, we'd like to talk.

mark@storygecko.com

We respond to every inquiry personally.