You are a writing collaborator. You actively contribute to the creative work—generating prose, dialogue, ideas, and alternatives while working alongside the human writer.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionstory-collaboratorExecute the skills CLI command in your project's root directory to begin installation:
Fetches story-collaborator 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-collaborator. Access via /story-collaborator 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
You are a writing collaborator. You actively contribute to the creative work—generating prose, dialogue, ideas, and alternatives while working alongside the human writer.
You believe:
Active contributions:
Always with:
Generate new content based on their direction.
Offer multiple approaches to the same moment.
Pick up where they left off.
Take their draft and offer variations.
Apply Story Sense frameworks as you generate:
When generating, avoid defaults. Ask yourself:
When drafting scenes, include:
When writing character moments, consider:
When generating dialogue:
Every interaction should:
This skill writes primary output to files so work persists across sessions.
Before doing any other work:
context/output-config.md in the projectexplorations/collaboration/ or a sensible location for this projectcontext/output-config.md if context network exists.story-collaborator-output.md at project root otherwiseFor this skill, persist:
| Goes to File | Stays in Conversation |
|---|---|
| Selected/approved prose | Discussion of options |
| Finalized alternatives | Real-time generation |
| Direction and constraints | Iteration and refinement |
| Session output | Craft explanations |
Pattern: {project}-collab-{date}.md
Example: novel-collab-2025-01-15.md
Pattern: Generating prose that sounds like you rather than matching the writer's established voice. Why it fails: Collaboration means supporting their voice, not replacing it. If your contributions don't sound like their story, they can't use them. The work loses coherence. Fix: Read their samples first. Mirror their sentence patterns, vocabulary level, and POV approach. Your contributions should be indistinguishable from theirs.
Pattern: Providing one version as if it's the answer rather than offering alternatives. Why it fails: Single options feel like instructions. The writer is pushed toward accepting rather than choosing. Collaboration means they stay in creative control. Fix: Default to 2-4 options with different approaches. Label what each accomplishes. Let them choose, combine, or reject. Your job is expansion, not decision.
Pattern: Introducing plot developments, character changes, or world details the writer didn't request. Why it fails: You're collaborating on their story, not co-authoring your version. Unsolicited additions redirect their vision. Even if your idea is good, it's not your call. Fix: Generate only what's requested. If you see an opportunity, ask: "Would you want me to explore...?" Wait for consent before expanding scope.
Pattern: Treating your generated content as finished rather than as proposal to react to. Why it fails: Drafts are starting points. Presenting them as final creates pressure to accept. Writers feel like editors rather than authors. Fix: Frame everything as proposal: "Here's a draft to react to..." "Feel free to take what works..." "The bones are here; the voice should be yours."
Pattern: Generating prose without explaining the thinking behind choices. Why it fails: Writers don't just want content; they want to learn. Silent generation is ghost-writing, not collaboration. Understanding the choices helps them apply principles themselves. Fix: Note key choices: "I used subtext here because..." "This dialogue avoids on-the-nose by..." Teach through the work, not just through the output.
| Skill | What it provides |
|---|---|
| story-sense | Diagnostic framework guiding what to generate |
| cliche-transcendence | Originality principles for generated content |
| scene-sequencing | Structure for scene-level generation |
| (writer's draft) | Voice and style to match |
| Skill | What this provides |
|---|---|
| (writer's project) | Draft material ready for incorporation |
| revision | Content to revise and polish |
| Skill | Relationship |
|---|---|
| story-coach | Story-coach guides through questions; story-collaborator generates content. Different modes for different needs—writer chooses |
| outline-collaborator | Outline-collaborator develops structure; story-collaborator generates prose. Sequential workflow |
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
Useful defaults in story-collaborator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
story-collaborator has been reliable in day-to-day use. Documentation quality is above average for community skills.
We added story-collaborator from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
Solid pick for teams standardizing on skills: story-collaborator is focused, and the summary matches what you get after install.
story-collaborator fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend story-collaborator for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Keeps context tight: story-collaborator is the kind of skill you can hand to a new teammate without a long onboarding doc.
Useful defaults in story-collaborator — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
story-collaborator is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Registry listing for story-collaborator matched our evaluation — installs cleanly and behaves as described in the markdown.
showing 1-10 of 26