Before doing anything else, check if ccpm is available. If not, bootstrap the entire ecosystem with one command:
Works with
AI-first code editor with Composer
Before installing skills in Cursor, ensure your development environment meets these requirements:
node --versionskills-searchExecute the skills CLI command in your project's root directory to begin installation:
Fetches skills-search from daymade/claude-code-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 skills-search. Access via /skills-search 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
784
GitHub stars
0
upvotes
Run in your terminal
0
installs
0
this week
784
stars
Before doing anything else, check if ccpm is available. If not, bootstrap the entire ecosystem with one command:
# Check availability
which ccpm || npx @daymade/ccpm setup
ccpm setup installs this skill + configures Claude Desktop MCP server (if installed). After bootstrap, all commands below work directly.
When this skill is activated, you MUST directly execute the appropriate ccpm command using the Bash tool. Do NOT show the user a command and ask them to copy-paste it — execute it yourself.
If ccpm is not globally installed, use npx @daymade/ccpm as a drop-in replacement for all commands below.
Match the user's intent to the correct action:
| User Intent | Action |
|---|---|
| "find skills for X" / "search X skills" | ccpm search <query> |
| "what skills are popular" / "top skills" | ccpm popular |
| "what's new" / "latest skills" | ccpm recent |
| "install X" / "add X skill" | ccpm install <skill-name> |
| "what does X do" / "tell me about X" | ccpm info <skill-name> |
| "what skills do I have" / "list skills" | ccpm list |
| "remove X" / "uninstall X" | ccpm uninstall <skill-name> |
| "update X" / "update all skills" | ccpm update [name] [--all] |
| "I need help with PDF/Excel/..." | ccpm search <topic>, then offer to install the best match |
ccpm commands via the Bash tool, never ask the user to run them manually.ccpm is not found, fall back to npx @daymade/ccpm. If the registry is unreachable, say so clearly.@org/skill-name format (e.g., ccpm install @daymade/skill-creator).ccpm search <query> [--limit <n>] [--tags <t1,t2>] [--author <name>] [--smart]
ccpm popular [--limit <n>] # Most downloaded
ccpm recent [--limit <n>] # Recently published/updated
ccpm install <skill-name> # Install (user-level, default)
ccpm install <name> --project # Install to current project only
ccpm install <name> --force # Force reinstall
ccpm list # List installed skills
ccpm info <skill-name> # Detailed skill information
ccpm update [name] # Update a skill
ccpm update --all # Update all skills
ccpm uninstall <skill-name> # Remove a skill
After any successful install, always tell the user:
Skill installed successfully. Please restart Claude Code (or start a new conversation) for the skill to become available.
For Claude Desktop users who want native tool integration (no Bash needed), the same functionality is available as an MCP server:
{
"mcpServers": {
"skill-search": {
"command": "npx",
"args": ["-y", "skills-search-mcp"]
}
}
}
Both this skill and the MCP server wrap the same ccpm CLI — they are complementary, not conflicting.
Use npx @daymade/ccpm instead, or install globally: npm install -g @daymade/ccpm.
Restart Claude Code — skills are loaded at startup.
Check write permissions to ~/.claude/skills/. Try installing with --project for project-level scope.
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
Registry listing for skills-search matched our evaluation — installs cleanly and behaves as described in the markdown.
Registry listing for skills-search matched our evaluation — installs cleanly and behaves as described in the markdown.
Keeps context tight: skills-search is the kind of skill you can hand to a new teammate without a long onboarding doc.
skills-search reduced setup friction for our internal harness; good balance of opinion and flexibility.
skills-search is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
Useful defaults in skills-search — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
skills-search fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
skills-search has been reliable in day-to-day use. Documentation quality is above average for community skills.
skills-search is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
We added skills-search from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 64