
story-analysis
Systematically evaluate completed short stories or novel chapters to identify strengths, weaknesses, and improvement opportunities. Use after drafting to assess whether the piece achieves its narrative goals.
- Installs
- 686
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/jwynia/agent-skills --skill story-analysis- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads story-analysis automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Story Analysis Diagnostic
Purpose
Systematically evaluate completed short stories or novel chapters to identify strengths, weaknesses, and improvement opportunities. Use after drafting to assess whether the piece achieves its narrative goals.
Quick Reference
| Mode | Use For | Key Focus |
|---|---|---|
| Short Story | Complete standalone pieces | Unity, shattering moment, resolution |
| Chapter | Sections within larger work | Continuity, momentum, arc contribution |
Short Story Analysis
SA1: Narrative Foundation
Evaluate:
- Single clear premise or conflict driving the story
- Scope appropriate for length
- Premise integrated with plot and character
- Clear implications that matter to the story
Questions:
- Can you state the core conflict in one sentence?
- Is the scope right for the word count?
- Does the premise connect to character stakes?
- Are the implications explored within the story?
SA2: Character Construction
Evaluate:
- One or two main characters with clear stakes
- Efficient characterization through actions/choices
- Character arcs intersecting with premise
- Limited but purposeful supporting cast
- Distinct voice and perspective
Questions:
- Who is the story about and what do they want?
- Is character revealed through action, not description?
- Does the character change in response to events?
- Does every character serve a purpose?
Red Flags:
- Character described but never demonstrated
- Supporting characters who don't affect anything
- Stakes unclear or abstract
SA3: Story Environment
Evaluate:
- Details woven into action, not exposition
- Each element serves multiple purposes (setting/plot/theme)
- Clear rules and limitations
- Environment revealed through character interaction
- Effective atmosphere and tone
Questions:
- Is worldbuilding shown through action or told in blocks?
- Does each setting detail do double duty?
- Are the story's rules clear and consistent?
- Does the environment affect character choices?
Red Flags:
- Info-dump paragraphs
- Details that never matter again
- Setting that doesn't influence events
SA4: The Shattering Moment
Definition: The pivotal point that transforms everything—a moment that cannot be undone.
Must function through one approach:
- Personal revelation that transforms understanding
- External event that forces change
- Relationship transformation that shifts dynamics
- Internal realization that cannot be undone
- Cultural/social collision that demands response
For Science Fiction:
- Technology IS the shattering moment
- Technology ENABLES the shattering moment
- Technology PREVENTS recovery
- Shattering moment CHANGES relationship with technology
Questions:
- Is there a clear turning point?
- Is it connected to the core conflict?
- Does it change the character irreversibly?
- Does everything after feel different?
SA5: Scene Structure
Evaluate:
- Scenes maximize both character and premise
- Strategic balance of scene and summary
- Opening hook establishes character, situation, conflict
- Focused conflict from the core premise
- Resolution addresses conflict while suggesting broader implications
Questions:
- Does every scene advance character AND plot?
- Is the opening hook doing its job?
- Is the conflict focused or diffuse?
- Does the resolution satisfy while resonating beyond?
SA6: Technical Execution
Economy of Detail:
- Every element serves multiple purposes
- No extraneous background or world info
- Exposition integrated into action
- Clear connection between details and story purpose
Point of View:
- Consistent and purposeful POV choice
- Viewpoint optimal for revealing character and premise
- Minimal POV shifts
- Clear character perspective on events
- Effective narrative distance
Language and Voice:
- Consistent tone throughout
- Purposeful dialogue
- Effective subtext
- Style serves story purpose
- Distinct narrative voice
SA7: Emotional Architecture
Tension Management:
- Clear emotional throughline
- Strategic building and release
- Effective pacing of reveals
- Balance of explicit and implicit
Reader Engagement:
- Clear emotional stakes
- Strategic use of empathy
- Meaningful emotional payoff
- Effective use of subtext
Questions:
- Is there a clear emotional journey?
- Does tension build appropriately?
- Is the emotional payoff earned?
- What remains unspoken but felt?
SA8: Thematic Resolution
Evaluate:
- Character arc completion
- Premise implications addressed
- Immediate conflict resolved
- Larger questions remain thought-provoking
Questions:
- Is the character arc complete?
- Are the premise implications explored?
- Is the immediate conflict resolved?
- Does the story linger in the mind?
Novel Chapter Analysis
CA1: Position in Narrative Arc
Evaluate:
- Chapter's specific role in overall structure
- Contribution to plot progression
- Advancement of character development arcs
- Thematic development within larger work
Questions:
- What is this chapter's job in the novel?
- What plot progress happens here?
- What character progress happens here?
- How does it develop the theme?
CA2: Narrative Momentum
Evaluate:
- Opening hook's connection to previous chapter
- Tension management across chapter breaks
- Balance of resolution and open questions
- Strength of chapter ending propulsion
- Questions answered vs. questions raised
Questions:
- Does the opening connect to what came before?
- Does the ending make readers want to continue?
- What questions does this chapter answer?
- What new questions does it raise?
Red Flags:
- Chapter ends at natural stopping point (too easy to put down)
- Opening ignores previous chapter's energy
- All questions answered, no forward pull
CA3: Plot Threading
Evaluate:
- Ongoing plot threads advanced
- New plot threads introduced
- Plot elements resolved
- Setup for future chapters
- Connection to primary and secondary arcs
Track:
| Thread | Status This Chapter |
|---|---|
| Main plot | Advanced / Setup / Resolved |
| Subplot A | Advanced / Setup / Resolved |
| Subplot B | Advanced / Setup / Resolved |
CA4: Character Continuity
Evaluate:
- Progress on character arcs from previous chapters
- New character aspects revealed
- Relationship evolution
- Setup for future development
- Consistency with established traits
Questions:
- How has this character changed since chapter 1?
- What new facets are revealed here?
- How do relationships shift?
- Is the character consistent with who they've been?
CA5: POV and Voice
Evaluate:
- Consistency with established POV patterns
- Effective transitions between viewpoints (if multiple)
- Depth of penetration into character perspective
- Balance of internal and external narrative
- Voice and tone alignment with overall narrative
CA6: Information Flow
Evaluate:
- Balance of new and established information
- Strategic revelation of background elements
- Management of reader vs. character knowledge
- Setup of future revelations
- Integration of necessary exposition
CA7: Pacing Elements
Evaluate:
- Chapter's pace relative to surrounding chapters
- Internal pacing structure
- Tension development and release
- Scene length and rhythm
- Strategic use of time
CA8: Connection Tracking
Previous Chapter:
- Immediate continuity elements
- Tension carryover
- Question resolution
- Thread advancement
Next Chapter:
- Setup elements planted
- Tension building toward
- Questions raised
- Threads advanced
Broader Novel:
- Major arc advancement
- Theme development
- Character arc progression
- World development contribution
Evaluation Checklists
Short Story Checklist
- Single clear premise/conflict
- Appropriate scope for length
- Characters with clear stakes
- Characterization through action
- Environment serves multiple purposes
- Clear shattering moment
- Every scene advances character AND plot
- Consistent POV
- Emotional arc present
- Resolution satisfies while resonating
Chapter Checklist
- Clear role in overall novel
- Opening connects to previous chapter
- Ending creates forward pull
- Plot threads advanced
- Character development progresses
- Consistent with established elements
- Sets up future developments
- Appropriate pacing for position in novel
Anti-Patterns
1. The Checklist Tyranny
Pattern: Treating all checklist items as equally important. Flagging every missed item as a problem requiring fix. Why it fails: Not all issues matter equally. A missing shattering moment is critical; a slight POV wobble might be stylistic choice. Checklists identify possibilities, not mandates. Fix: Prioritize by impact. Ask "Does this actually hurt the story?" before recommending changes. Some rules can be broken effectively.
2. The Genre Blindness
Pattern: Applying one genre's standards to all stories. Evaluating literary fiction by thriller pacing standards, or action stories by literary depth requirements. Why it fails: Genres have different contracts with readers. What's a flaw in one genre is a feature in another. Fix: Identify genre expectations first. Evaluate against what the story is trying to be, not a universal standard.
3. The Nitpick Cascade
Pattern: Focusing on micro-issues while missing macro problems. Catching comma splices while the story has no conflict. Why it fails: Sentence-level perfection can't save structural failure. Fixing small things first is procrastination from hard work. Fix: Diagnose at structure level first. Only move to prose-level analysis after structure is sound.
4. The Comparison Trap
Pattern: Evaluating against published bestsellers or classics. "This isn't as good as [famous work]." Why it fails: Drafts aren't finished works. Different stories serve different purposes. Unfair comparison discourages rather than guides. Fix: Evaluate against the story's own goals. What is this trying to do? Does it succeed at that?
5. The Fix-Everything Dump
Pattern: Delivering a comprehensive list of all issues without prioritization or encouragement. Why it fails: Overwhelming. Writers shut down when facing 50 problems. No sense of what matters most. Fix: Identify 3-5 highest-impact issues. Note what's working. Create actionable, prioritized guidance.
Integration Points
Inbound:
- From
drafting: After completing draft - From
revision: As part of revision process
Outbound:
- To
revision: For identified issues - To
scene-sequencing: For pacing problems - To
dialogue: For conversation issues - To
character-arc: For character problems
Complementary:
flash-fiction: For stories under 1500 wordsprose-style: For sentence-level issuesstory-sense: For diagnosing what's wrong
FAQ
What does the story-analysis skill do?
Systematically evaluate completed short stories or novel chapters to identify strengths, weaknesses, and improvement opportunities. Use after drafting to assess whether the piece achieves its narrative goals.
How do I install story-analysis?
Run npx skills add https://github.com/jwynia/agent-skills --skill story-analysis in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/story-analysis/ (personal) or .claude/skills/story-analysis/ (project).
Which AI agents can use story-analysis?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is story-analysis safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains story-analysis?
It is published by jwynia in jwynia/agent-skills. It has 686 recorded installs.
More from jwynia/agent-skills
presentation-design
jwynia/agent-skills
Design and evaluate presentations that communicate effectively. Use when designing a presentation, creating slides, getting presentation feedback, structuring a talk, or reviewing slides. Keywords: presentation, slides, talk, PowerPoint, Keynote, reveal.js.
frontend-design
jwynia/agent-skills
Create distinctive, production-grade frontend interfaces with high design quality. Provides analysis tools for auditing existing designs and generation tools for creating color palettes, typography systems, design tokens, and component templates. Supports React, Vue, Svelte, and vanilla HTML/CSS. Use when building web components, pages, or applications. Keywords: design, UI, frontend, CSS, components, palette, typography, tokens, accessibility.
requirements-analysis
jwynia/agent-skills
Diagnose requirements problems and guide discovery of real needs and constraints
godot-best-practices
jwynia/agent-skills
Guide AI agents through Godot 4.x GDScript coding best practices including scene organization, signals, resources, state machines, and performance optimization. This skill should be used when generating GDScript code, creating Godot scenes, designing game architecture, implementing state machines, object pooling, save/load systems, or when the user asks about Godot patterns, node structure, or GDScript standards. Keywords: godot, gdscript, game development, signals, resources, scenes, nodes, state machine, object pooling, save system, autoload, export, type hints.
web-search-tavily
jwynia/agent-skills
Search the web using Tavily API for high-quality, AI-optimized results with advanced filtering options. Use when you need structured search results, domain filtering, relevance scores, or AI-generated answer summaries. Requires TAVILYAPIKEY. Keywords: tavily, advanced search, filtered search, domain filtering, relevance scoring.
godot-asset-generator
jwynia/agent-skills
Generate game assets using AI image generation APIs (DALL-E, Replicate, fal.ai) and prepare them for Godot. Covers the full art pipeline from concept art and style guides to final sprites, sprite sheets, and import configuration. This skill should be used when creating game art, generating sprites, making tilesets, creating UI elements, or preparing assets for Godot import. Keywords: game assets, AI art, DALL-E, Replicate, fal.ai, sprite sheet, tileset, Godot, pixel art, character sprite, game art, texture, animation frames.
Popular ai & agents skills
google-agents-cli-publish
google/agents-cli
This skill should be used when the user wants to "publish an agent", "publish my ADK agent", "register an agent with Gemini", "publish to Gemini" (formerly Gemini Enterprise), or needs guidance on the agents-cli publish gemini command. Also use when the user wants to "manage agents in Agent Registry", "list/update/delete registered agents", or "register an MCP server". Covers ADK vs A2A registration modes, programmatic and interactive usage, flag reference, auto-detection from deployment metadata, Agent Registry fleet management, and troubleshooting. Part of the agents-cli skills suite. Do NOT use for deployment (use google-agents-cli-deploy).
google-agents-cli-eval
google/agents-cli
This skill should be used when the user wants to "run an evaluation", "evaluate my agent", "evaluate my ADK agent", "write an eval dataset", "analyze eval failures", "compare eval results", "optimize agent", or needs guidance on the Gemini platform eval methodology and the Quality Flywheel. Covers eval metrics, dataset schema, LLM-as-judge scoring, and common failure causes. Applies to any agents-cli project, whatever framework the agent is written in. Do NOT use for agent API code patterns (ADK: use google-agents-cli-adk-code), deployment (use google-agents-cli-deploy), or project scaffolding (use google-agents-cli-scaffold).
skill-creator
anthropics/skills
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.
codex-pet
prime-skills/runcomfy-agent-skills
Codex Pet generator on RunComfy. Build a Codex-compatible Codex Pet spritesheet.webp + pet.json from a single reference image, drop it into ${CODEXHOME:-$HOME/.codex}/pets/ / and Codex picks it up as a custom Codex Pet next to the 8 built-ins. This skill produces the exact Codex Pet atlas Codex expects (1536x1872 PNG/WebP, 8 cols x 9 rows, 192x208 cells, 9 animation states — idle, running-right, running-left, waving, jumping, failed, waiting, running, review). Calls OpenAI GPT Image 2 edit ONCE via the local RunComfy CLI as runcomfy run openai/gpt-image-2/edit to produce a canonical Codex Pet pose, then assembles all 9 animation rows programmatically with ImageMagick micro-transforms — no Codex Pro, no $imagegen, no OPENAIAPIKEY required, only RUNCOMFYTOKEN. Triggers on "codex pet", "create codex pet", "make codex pet", "hatch codex pet", "/hatch image", "desktop pet codex", "codex pets", "spritesheet.webp", or any explicit ask to build a custom pet for OpenAI Codex.
full-output-enforcement
leonxlnx/taste-skill
Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.
executing-plans
obra/superpowers
Use when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available