Create and use user-triggered prompts with /command-name syntax.
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionslash-commandsExecute the skills CLI command in your project's root directory to begin installation:
Fetches slash-commands from parcadei/continuous-claude-v3 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 slash-commands. Access via /slash-commands 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
3.7K
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
3.7K
stars
Create and use user-triggered prompts with /command-name syntax.
| Command | Purpose |
|---|---|
/clear |
Clear conversation history |
/compact |
Compact conversation with focus |
/config |
Open settings interface |
/cost |
Show token usage |
/agents |
Manage sub-agents |
/mcp |
Manage MCP servers |
/memory |
Edit CLAUDE.md files |
/model |
Select AI model |
/review |
Request code review |
/resume |
Resume session |
/help |
Get usage help |
mkdir -p .claude/commands
cat > .claude/commands/optimize.md << 'EOF'
---
description: Analyze code for performance issues
---
Review this code for:
- Performance bottlenecks
- Memory leaks
- Caching opportunities
EOF
mkdir -p ~/.claude/commands
cat > ~/.claude/commands/review.md << 'EOF'
---
description: Security-focused code review
---
Check for vulnerabilities:
- Input validation
- SQL injection
- XSS risks
EOF
---
description: Brief description for /help
allowed-tools: [Bash, Read, Write] # Optional
argument-hint: "[file] [type]" # Optional
---
Your markdown instructions here.
Use $1, $2 for arguments or $ARGUMENTS for all.
Run bash before loading prompt with ! prefix:
---
allowed-tools: Bash(git:*), Bash(grep:*)
description: Git commit helper
---
Current status: !`git status`
Staged changes: !`git diff --staged`
Recent commits: !`git log --oneline -5`
Based on these changes, suggest a commit message.
Rules:
allowed-tools: Bash(...) in frontmatter!`command`Include files with @ prefix:
Review against @.claude/STYLE_GUIDE.md
Compare:
- @src/old.js
- @src/new.js
Refactor files matching @src/**/*.util.ts
---
argument-hint: "[pr-number] [priority]"
---
Review PR #$1 with priority: $2
# Or use all arguments:
Fix issue #$ARGUMENTS
Usage:
/review-pr 456 high
# $1 = "456", $2 = "high"
Organize with subdirectories:
.claude/commands/
├── frontend/
│ └── component.md → /component (project:frontend)
└── backend/
└── endpoint.md → /endpoint (project:backend)
MCP servers expose prompts as commands:
/mcp__github__list_prs
/mcp__github__pr_review 456
/mcp__jira__create_issue "Bug" high
| Aspect | Slash Commands | Skills |
|---|---|---|
| Invocation | Explicit: /command |
Auto-discovered |
| Files | Single .md file | Directory with SKILL.md |
| Use Case | Quick prompts | Complex workflows |
Use slash commands for: Frequently typed prompts, simple templates Use skills for: Complex workflows, multiple files, auto-discovery
---
description: Generate semantic commit message
allowed-tools: Bash(git:*), Read
argument-hint: "[type]"
---
# Semantic Commit Generator
Staged files: !`git diff --name-only --cached`
Diff preview:
!`git diff --cached | head -100`
Generate a conventional commit message.
Type: $1 (feat/fix/docs/style/refactor/perf/test/chore)
Format: `<type>(<scope>): <subject>`
Usage: /commit feat
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.
parcadei/continuous-claude-v3
mattpocock/skills
cursor/plugins
ailabs-393/ai-labs-claude-skills
pproenca/dot-skills
mattpocock/skills
I recommend slash-commands for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
Registry listing for slash-commands matched our evaluation — installs cleanly and behaves as described in the markdown.
slash-commands reduced setup friction for our internal harness; good balance of opinion and flexibility.
Solid pick for teams standardizing on skills: slash-commands is focused, and the summary matches what you get after install.
slash-commands reduced setup friction for our internal harness; good balance of opinion and flexibility.
Keeps context tight: slash-commands is the kind of skill you can hand to a new teammate without a long onboarding doc.
Registry listing for slash-commands matched our evaluation — installs cleanly and behaves as described in the markdown.
slash-commands fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
I recommend slash-commands for anyone iterating fast on agent tooling; clear intent and a small, reviewable surface area.
slash-commands has been reliable in day-to-day use. Documentation quality is above average for community skills.
showing 1-10 of 66