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.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionstory-senseExecute the skills CLI command in your project's root directory to begin installation:
Fetches story-sense from jwynia/agent-skills and configures it for Cursor.
The CLI shows a list of agents. Use arrow keys and space to select Cursor:
Confirm successful installation by checking the skill directory location:
Restart Cursor to activate story-sense. Access via /story-sense in your agent's command palette.
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 environment. Always review source, verify the publisher, and test in isolation before production.
Submit your Claude Code skill and start earning
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
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
Evaluate features using frameworks (RICE, ICE, Kano) and create prioritized backlogs
Example
Score 20 feature ideas using RICE framework, generate prioritized roadmap with rationale
0
total installs
0
this week
46
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
46
stars
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.
Use this skill when:
Do NOT use this skill when:
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:
Symptoms: Nothing exists yet Interventions: story-idea-generator, elemental genres
Symptoms: Have idea but world/characters/plot feel thin Interventions: cliche-transcendence, systemic-worldbuilding, key-moments
Symptoms: Setting exists but feels like backdrop Interventions: worldbuilding skill suite (belief-systems, economic-systems, governance-systems)
Symptoms: Aliens/fantasy species feel like humans in costume Interventions: conlang, species development frameworks
Symptoms: Characters serve plot rather than driving it Interventions: character-arc, underdog-unit, positional-revelation
Symptoms: Scenes work individually but don't accumulate Interventions: scene-sequencing
Symptoms: Events happen but don't accumulate meaning Interventions: moral-parallax, key-moments
Symptoms: Characters sound alike, conversations lifeless Interventions: dialogue
Symptoms: Story builds well but resolution disappoints Interventions: endings
Symptoms: Planning done but draft isn't happening Interventions: drafting
Symptoms: Story works but sentences are functional not memorable Interventions: prose-style
Symptoms: Draft exists but revision feels overwhelming Interventions: revision
Symptoms: Story exists but quality uncertain Interventions: sensitivity-check, story-analysis
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
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
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
Fix: Always ask clarifying questions before diagnosing.
Fix: Recommend one intervention. Expand after reassessment.
Fix: Balance diagnostic accuracy with what energizes the writer.
Fix: Keep asking "Does this feel right?" alongside structural diagnosis.
Routes to all fiction skills based on diagnosed state.
Make data-driven prioritization decisions faster
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
Prerequisites
Time Estimate
30-60 minutes to see productivity improvements
Steps
Common Pitfalls
✓ Do
✗ Don't
💡 Pro Tips
✓ 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.
jwynia/agent-skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
Keeps context tight: story-sense is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added story-sense from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
story-sense is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
story-sense fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Useful defaults in story-sense — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Registry listing for story-sense matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for story-sense matched our evaluation — installs cleanly and behaves as described in the markdown.
story-sense reduced setup friction for our internal harness; good balance of opinion and flexibility.
story-sense is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
story-sense fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
showing 1-10 of 36