skills-search▌
daymade/claude-code-skills · updated Apr 8, 2026
MDX-style export adds YAML metadata + attribution linking explainx.ai and this canonical listing URL.
Before doing anything else, check if ccpm is available. If not, bootstrap the entire ecosystem with one command:
Skills Search — Agent Behavioral Directives
Auto-Bootstrap (Run First)
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.
Core Behavior
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.
Intent Mapping
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 |
Execution Rules
- Always execute directly — run
ccpmcommands via the Bash tool, never ask the user to run them manually. - Summarize results — after executing, present the output in a clear, readable format.
- Suggest next steps — after search results, offer to install. After install, remind the user to restart Claude Code.
- Handle errors gracefully — if
ccpmis not found, fall back tonpx @daymade/ccpm. If the registry is unreachable, say so clearly. - Namespaced skills — support
@org/skill-nameformat (e.g.,ccpm install @daymade/skill-creator).
Command Reference
Search
ccpm search <query> [--limit <n>] [--tags <t1,t2>] [--author <name>] [--smart]
Discovery
ccpm popular [--limit <n>] # Most downloaded
ccpm recent [--limit <n>] # Recently published/updated
Install & Manage
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
Post-Install Reminder
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.
MCP Server Alternative
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.
Troubleshooting
"ccpm: command not found"
Use npx @daymade/ccpm instead, or install globally: npm install -g @daymade/ccpm.
Skill not available after install
Restart Claude Code — skills are loaded at startup.
Permission errors
Check write permissions to ~/.claude/skills/. Try installing with --project for project-level scope.
How to use skills-search on Cursor
AI-first code editor with Composer
Prerequisites
Before installing skills in Cursor, ensure your development environment meets these requirements:
- ›Cursor installed and configured on your development machine
- ›Node.js version 16.0+ with npm package manager (verify with
node --version) - ›Active project directory or workspace where you want to add skills-search
Execute installation command
Execute the skills CLI command in your project's root directory to begin installation:
The skills CLI fetches skills-search from GitHub repository daymade/claude-code-skills and configures it for Cursor.
Select Cursor when prompted
The CLI will show a list of available agents. Use arrow keys to navigate and space to select Cursor:
Verify installation
Confirm successful installation by checking the skill directory location:
Reload or restart Cursor to activate skills-search. Access the skill through slash commands (e.g., /skills-search) or your agent's skill management interface.
Security & Verification Notice
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 development environment. Always verify the publisher's identity, review recent commits, and test in isolated environments before production deployment.
List & Monetize Your Skill
Submit your Claude Code skill and start earning
Use Cases▌
User Story & Requirements Generation
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
Competitive Analysis
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
Roadmap Prioritization
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
Stakeholder Communication
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
Implementation Guide▌
Prerequisites
- ›Claude Desktop or compatible AI client
- ›Access to product documentation and roadmap tools (Jira, Notion, etc.)
- ›Understanding of product management frameworks (RICE, Jobs-to-be-Done, etc.)
- ›Stakeholder contact information and communication channels
Time Estimate
30-60 minutes to see productivity improvements
Installation Steps
- 1.Install product management skill
- 2.Start with user story generation for known feature
- 3.Progress to competitive analysis: research 2-3 competitors
- 4.Use for roadmap prioritization: apply RICE/ICE scoring
- 5.Draft stakeholder communications and refine based on feedback
- 6.Build template library for recurring PM tasks
- 7.Share effective prompts with product team
Common Pitfalls
- ⚠Not validating competitive research—verify facts before sharing
- ⚠Accepting user stories without involving engineering team
- ⚠Over-relying on frameworks without qualitative judgment
- ⚠Not customizing outputs to company culture and communication style
- ⚠Skipping stakeholder validation of generated requirements
Best Practices▌
✓ Do
- +Validate research and competitive analysis with real data
- +Collaborate with engineering when generating technical requirements
- +Customize frameworks and templates to your company context
- +Use skill for first drafts, refine with stakeholder input
- +Document successful prompt patterns for PM tasks
- +Combine AI efficiency with human judgment and intuition
✗ Don't
- −Don't publish competitive analysis without fact-checking
- −Don't finalize user stories without engineering review
- −Don't make prioritization decisions solely on AI scoring
- −Don't skip customer validation of generated requirements
- −Don't ignore company-specific context and culture
💡 Pro Tips
- ★Provide context: company goals, constraints, customer feedback
- ★Ask for alternatives: 'Show 3 ways to prioritize this roadmap'
- ★Request stakeholder-specific formatting: 'Executive summary vs. engineering spec'
- ★Use skill for 70% generation + 30% customization to company needs
When to Use This▌
✓ 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.
Learning Path▌
- 1Basic: user stories, feature specs, status updates
- 2Intermediate: competitive analysis, prioritization frameworks, PRDs
- 3Advanced: product strategy, go-to-market planning, OKR setting
- 4Expert: product vision, market positioning, business model innovation
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
Ratings
4.7★★★★★64 reviews- ★★★★★Kwame Harris· Dec 28, 2024
Registry listing for skills-search matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Olivia Gonzalez· Dec 24, 2024
Registry listing for skills-search matched our evaluation — installs cleanly and behaves as described in the markdown.
- ★★★★★Advait Flores· Dec 16, 2024
Keeps context tight: skills-search is the kind of skill you can hand to a new teammate without a long onboarding doc.
- ★★★★★Kwame Martin· Dec 12, 2024
skills-search reduced setup friction for our internal harness; good balance of opinion and flexibility.
- ★★★★★Meera Kapoor· Dec 12, 2024
skills-search is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Isabella Singh· Dec 8, 2024
Useful defaults in skills-search — fewer surprises than typical one-off scripts, and it plays nicely with `npx skills` flows.
- ★★★★★Naina Smith· Dec 4, 2024
skills-search fits our agent workflows well — practical, well scoped, and easy to wire into existing repos.
- ★★★★★Kiara Khanna· Nov 27, 2024
skills-search has been reliable in day-to-day use. Documentation quality is above average for community skills.
- ★★★★★Kwame Sharma· Nov 23, 2024
skills-search is among the better-maintained entries we tried; worth keeping pinned for repeat workflows.
- ★★★★★Advait Dixit· Nov 7, 2024
We added skills-search from the explainx registry; install was straightforward and the SKILL.md answered most questions upfront.
showing 1-10 of 64