Use Read tool before announcing skill usage. The session-start hook does NOT read skills for you. Announcing without calling Read = lying.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versiongetting-started-with-skillsExecute the skills CLI command in your project's root directory to begin installation:
Fetches getting-started-with-skills from obra/superpowers-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 getting-started-with-skills. Access via /getting-started-with-skills 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
601
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
601
stars
Use Read tool before announcing skill usage. The session-start hook does NOT read skills for you. Announcing without calling Read = lying.
Follow mandatory workflows. Brainstorming before coding. Check for skills before ANY task.
Create TodoWrite todos for checklists. Mental tracking = steps get skipped. Every time.
1. Check skills list at session start, or run find-skills [PATTERN] to filter.
2. If relevant skill exists, YOU MUST use it:
${SUPERPOWERS_SKILLS_ROOT}/skills/category/skill-name/SKILL.mdDon't rationalize:
Why: Skills document proven techniques that save time and prevent mistakes. Not using available skills means repeating solved problems and making known errors.
If a skill for your task exists, you must use it or you will fail at your task.
If a skill has a checklist, YOU MUST create TodoWrite todos for EACH item.
Don't:
Why: Checklists without TodoWrite tracking = steps get skipped. Every time. The overhead of TodoWrite is tiny compared to the cost of missing steps.
Examples: skills/testing/test-driven-development/SKILL.md, skills/debugging/systematic-debugging/SKILL.md, skills/meta/writing-skills/SKILL.md
After you've read a skill with Read tool, announce you're using it:
"I've read the [Skill Name] skill and I'm using it to [what you're doing]."
Examples:
Why: Transparency helps your human partner understand your process and catch errors early. It also confirms you actually read the skill.
Every skill has the same structure:
when_to_use tells you if this skill matches your situationMany skills contain rigid rules (TDD, debugging, verification). Follow them exactly. Don't adapt away the discipline.
Some skills are flexible patterns (architecture, naming). Adapt core principles to your context.
The skill itself tells you which type it is.
Your human partner's specific instructions describe WHAT to do, not HOW.
"Add X", "Fix Y" = the goal, NOT permission to skip brainstorming, TDD, or RED-GREEN-REFACTOR.
Red flags: "Instruction was specific" • "Seems simple" • "Workflow is overkill"
Why: Specific instructions mean clear requirements, which is when workflows matter MOST. Skipping process on "simple" tasks is how simple tasks become complex problems.
Starting any task:
Skill has checklist? TodoWrite for every item.
Finding a relevant skill = mandatory to read and use it. Not optional.
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.
JuliusBrussee/caveman
JuliusBrussee/caveman
whyashthakker/agent-skills-marketing
mattpocock/skills
parcadei/continuous-claude-v3
cursor/plugins
We added getting-started-with-skills from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
getting-started-with-skills reduced setup friction for our internal harness; good balance of opinion and flexibility.
Registry listing for getting-started-with-skills matched our evaluation — installs cleanly and behaves as described in the markdown.
I recommend getting-started-with-skills for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
I recommend getting-started-with-skills for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
getting-started-with-skills has been reliable in day-to-day use. Documentation quality is above average for community skills.
Solid pick for teams standardizing on skills: getting-started-with-skills is focused, and the summary matches what you get after install.
Solid pick for teams standardizing on skills: getting-started-with-skills is focused, and the summary matches what you get after install.
getting-started-with-skills has been reliable in day-to-day use. Documentation quality is above average for community skills.
Useful defaults in getting-started-with-skills — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
showing 1-10 of 28