expert-driven
Works with
No content available.
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionexpert-drivenExecute the skills CLI command in your project's root directory to begin installation:
Fetches expert-driven from gocallum/nextjs16-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 expert-driven. Access via /expert-driven 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
19
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
19
stars
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.
erichowens/some_claude_skills
sickn33/antigravity-awesome-skills
erichowens/some_claude_skills
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
expert-driven reduced setup friction for our internal harness; good balance of opinion and flexibility.
expert-driven is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Solid pick for teams standardizing on skills: expert-driven is focused, and the summary matches what you get after install.
expert-driven has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: expert-driven is focused, and the summary matches what you get after install.
Useful defaults in expert-driven — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
Keeps context tight: expert-driven is the kind of skill you can hand to a new teammate without a long onboarding doc.
I recommend expert-driven for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for expert-driven matched our evaluation — installs cleanly and behaves as described in the markdown.
Useful defaults in expert-driven — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 62