story-sense▌
jwynia/agent-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Identify what state a story is in and what it needs to move forward. This is not a linear process but a diagnostic model: Assess → Diagnose → Intervene → Reassess.
Story Sense: Diagnostic Skill
Identify what state a story is in and what it needs to move forward. This is not a linear process but a diagnostic model: Assess → Diagnose → Intervene → Reassess.
When to Use This Skill
Use this skill when:
- Writer is stuck and doesn't know why
- Story feels broken but root cause unclear
- Need to evaluate story problems systematically
- Someone asks "what's wrong with my story?"
Do NOT use this skill when:
- Writer wants you to write the story (use story-collaborator)
- Writer wants coaching questions only (use story-coach)
- Publishing/marketing questions (use book-marketing)
Core Principle
Story Sense is the ability to know what any story needs, regardless of its current state or intended medium.
There's no such thing as "stuck." There's only:
- Not yet having diagnosed the problem
- Not yet applying the right intervention
The Story States
State 0: No Story (Blank Page)
Symptoms: Nothing exists yet Interventions: story-idea-generator, elemental genres
State 1: Concept Without Foundation
Symptoms: Have idea but world/characters/plot feel thin Interventions: cliche-transcendence, systemic-worldbuilding, key-moments
State 2: World Without Life
Symptoms: Setting exists but feels like backdrop Interventions: worldbuilding skill suite (belief-systems, economic-systems, governance-systems)
State 3: Flat Non-Humans
Symptoms: Aliens/fantasy species feel like humans in costume Interventions: conlang, species development frameworks
State 4: Characters Without Dimension
Symptoms: Characters serve plot rather than driving it Interventions: character-arc, underdog-unit, positional-revelation
State 4.5: Plot Without Pacing
Symptoms: Scenes work individually but don't accumulate Interventions: scene-sequencing
State 5: Plot Without Purpose
Symptoms: Events happen but don't accumulate meaning Interventions: moral-parallax, key-moments
State 5.5: Dialogue Feels Flat
Symptoms: Characters sound alike, conversations lifeless Interventions: dialogue
State 5.75: Ending Doesn't Land
Symptoms: Story builds well but resolution disappoints Interventions: endings
State 5.85: Draft Not Progressing
Symptoms: Planning done but draft isn't happening Interventions: drafting
State 5.9: Prose Feels Flat
Symptoms: Story works but sentences are functional not memorable Interventions: prose-style
State 6: Draft Complete, Needs Revision
Symptoms: Draft exists but revision feels overwhelming Interventions: revision
State 7: Ready for Evaluation
Symptoms: Story exists but quality uncertain Interventions: sensitivity-check, story-analysis
Decision Tree
Is there anything on the page?
├── NO → story-idea-generator
└── YES → What's the problem?
├── Feels generic → cliche-transcendence
├── World feels thin → worldbuilding
├── Non-humans feel fake → conlang
├── Characters flat → character-arc
├── Pacing off → scene-sequencing
├── Dialogue wooden → dialogue
├── Ending weak → endings
├── Meaning unclear → moral-parallax
├── Draft not progressing → drafting
├── Prose flat → prose-style
└── Draft needs revision → revision
Diagnostic Process
- Listen for symptoms - What are they describing as the problem?
- Ask clarifying questions - Get specific about where they're stuck
- Identify the state - Match symptoms to state list
- Name the diagnosis - Explain what you're seeing
- Recommend intervention - Point to specific skill
- Offer next steps - What should they try first?
Available Scripts
entropy.ts
Injects creative randomness from curated lists.
deno run --allow-read scripts/entropy.ts lies
deno run --allow-read scripts/entropy.ts disasters --count 3
deno run --allow-read scripts/entropy.ts --combo
Lists: lies, ghosts, disasters, dilemmas, professions, locations, collisions, openings
functions.ts
Generates characters from abstract story functions.
deno run --allow-read scripts/functions.ts
deno run --allow-read scripts/functions.ts --setting scifi
deno run --allow-read scripts/functions.ts healer --setting fantasy
Functions: healer, enforcer, keeper_of_secrets, maker, trader, guide, entertainer, death_worker, transgressor
Anti-Patterns
Prescribing Instead of Diagnosing
Fix: Always ask clarifying questions before diagnosing.
Framework Overload
Fix: Recommend one intervention. Expand after reassessment.
Ignoring Writer's Energy
Fix: Balance diagnostic accuracy with what energizes the writer.
Treating Structure as Story
Fix: Keep asking "Does this feel right?" alongside structural diagnosis.
Related Skills
Routes to all fiction skills based on diagnosed state.
How to use story-sense on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add story-sense
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches story-sense from GitHub repository jwynia/agent-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate story-sense. Access the skill through slash commands (e.g., /story-sense) or your agent's skill management interface.
Security & Verification Notice
We perform automated surface-level scans (Gen AI Scanner, Socket, Snyk) during installation. These checks detect common vulnerabilities but do not guarantee complete security. Always review skill source code and verify the publisher's reputation before production use.
Skills execute code in your development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
Create detailed user stories, acceptance criteria, and feature specs
Example
Generate user stories for 'password reset feature' with acceptance criteria, edge cases, and test scenarios
Reduce spec writing time by 50%, ensure comprehensive coverage
Competitive Analysis
Research competitors, compare features, identify gaps
Example
Analyze 5 competitor products, create feature comparison matrix, suggest differentiation opportunities
Complete competitive research in 2 hours instead of 2 days
Roadmap Prioritization
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
Make data-driven prioritization decisions faster
Stakeholder Communication
Draft PRDs, status updates, and stakeholder presentations
Example
Create executive summary of Q3 roadmap, monthly progress report, feature launch announcement
Save 3-5 hours/week on communication overhead
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ Use When
Use for user story writing, competitive research, roadmap prioritization, stakeholder communication, and PRD drafting. Best for reducing repetitive documentation and research work.
✗ Avoid When
Avoid for strategic product vision (requires deep customer empathy), pricing decisions (needs market and financial expertise), or when face-to-face customer discovery is more valuable than speed.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.5★★★★★36 reviews- ★★★★★Sofia Patel· Dec 28, 2024
Keeps context tight: story-sense is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Ganesh Mohane· Dec 24, 2024
We added story-sense from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
- ★★★★★Kiara Rao· Nov 19, 2024
story-sense is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Sakshi Patil· Nov 15, 2024
story-sense fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kaira Johnson· Oct 10, 2024
Useful defaults in story-sense — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Chaitanya Patil· Oct 6, 2024
Registry listing for story-sense matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Alexander Reddy· Sep 17, 2024
Registry listing for story-sense matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Piyush G· Sep 13, 2024
story-sense reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Anika Okafor· Sep 13, 2024
story-sense is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Kiara Shah· Sep 1, 2024
story-sense fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 36