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.
npx skills add https://github.com/jwynia/agent-skills --skill 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.
| Mode | Use For | Key Focus |
|------|---------|-----------|
| Short Story | Complete standalone pieces | Unity, shattering moment, resolution |
| Chapter | Sections within larger work | Continuity, momentum, arc contribution |
Evaluate:
Questions:
Evaluate:
Questions:
Red Flags:
Evaluate:
Questions:
Red Flags:
Definition: The pivotal point that transforms everything—a moment that cannot be undone.
Must function through one approach:
For Science Fiction:
Questions:
Evaluate:
Questions:
Economy of Detail:
Point of View:
Language and Voice:
Tension Management:
Reader Engagement:
Questions:
Evaluate:
Questions:
Evaluate:
Questions:
Evaluate:
Questions:
Red Flags:
Evaluate:
Track:
| Thread | Status This Chapter |
|--------|---------------------|
| Main plot | Advanced / Setup / Resolved |
| Subplot A | Advanced / Setup / Resolved |
| Subplot B | Advanced / Setup / Resolved |
Evaluate:
Questions:
Evaluate:
Evaluate:
Evaluate:
Previous Chapter:
Next Chapter:
Broader Novel:
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.
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.
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.
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?
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.
Inbound:
drafting: After completing draftrevision: As part of revision processOutbound:
revision: For identified issuesscene-sequencing: For pacing problemsdialogue: For conversation issuescharacter-arc: For character problemsComplementary:
flash-fiction: For stories under 1500 wordsprose-style: For sentence-level issuesstory-sense: For diagnosing what's wrongIntegration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take jwynia/story-analysis from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.