Use this skill when creating or modifying agent skills in .agents/skills/.
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
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
Submit your Claude Code skill and start earning
epx add vercel/next.js --skill authoring-skillsCompatible with
Supported agents
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionauthoring-skillsExecute the skills CLI command in your project's root directory to begin installation:
epx add vercel/next.js --skill authoring-skillsFetches authoring-skills from vercel/next.js 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:
.cursor/skills/authoring-skills
Restart Cursor to activate authoring-skills. Access via /authoring-skillsin your agent's command palette.
Learn more:View source on GitHubSkills CLI docsAbout CursorWhat are agent skills?
Time estimate: 30-60 minutes to see productivity improvements
Prerequisites
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.
find-skills
vercel-labs/skills · Productivity · tag: skills
write-a-prd
mattpocock/skills · Productivity · same category
vite
uni-helper/skills · Productivity · same category
modly-image-to-3d
aradotso/trending-skills · Productivity · same category
pine-developer
traderspost/pinescript-agents · Productivity · same category
angular-best-practices-primeng
alfredoperez/angular-best-practices · Productivity · same category
authoring-skills fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
Keeps context tight: authoring-skills is the kind of skill you can hand to a new teammate without a long onboarding doc.
We added authoring-skills from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
authoring-skills is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: authoring-skills is focused, and the summary matches what you get after install.
Keeps context tight: authoring-skills is the kind of skill you can hand to a new teammate without a long onboarding doc.
authoring-skills fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
authoring-skills has been reliable in day-to-day use. Documentation quality is above average for community skills.
authoring-skills has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in authoring-skills — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 51