costa-marcello Find Skills
Search query: $ARGUMENTS
If $ARGUMENTS is empty, ask the user what skill they need.
Step 1: Pick the Registry
| User Request | Registry | CLI |
|---|---|---|
| General coding (React, testing, DevOps, linting) | Open Ecosystem | npx skills |
| Claude Code features, document processing (PDF, DOCX, XLSX, PPTX) | CCPM | ccpm |
| "installed skills", "my skills", "what do I have" | Both | ccpm list + npx skills check |
Tiebreaker: When the request could match either registry, run both searches and present combined results. Let the user pick.
Step 2: Search
Open Ecosystem:
npx skills find $ARGUMENTS
CCPM:
ccpm search $ARGUMENTS
If one registry returns no results, search the other before reporting "not found".
Step 3: Present Results
Show matching skills with name, description, and install command. When both registries return results, group them by registry with clear labels.
Step 4: Install
Open Ecosystem:
npx skills add <owner/repo@skill> -g -y
CCPM:
ccpm install <skill-name>
Step 5: Verify Installation
Open Ecosystem:
npx skills check
Confirm the skill appears in the installed list.
CCPM:
ccpm list
Confirm the skill appears. Remind the user to restart Claude Code -- CCPM skills load at startup.
If verification fails:
- Check the error message from the install command output.
- Run the install command again with verbose output.
- Check write permissions:
ls -la ~/.claude/skills/ - If the skill still does not appear, consult the Troubleshooting section below.
When No Skills Are Found
- Tell the user no matching skill exists in either registry.
- Attempt the task directly using built-in capabilities.
- If the user wants a reusable solution, offer to create a custom skill:
- Open Ecosystem:
npx skills init my-skill - CCPM: invoke
/create-skill
- Open Ecosystem:
- Registry: Open Ecosystem (general coding topic).
- Search:
npx skills find react performance - Results show
vercel-labs/agent-skills@vercel-react-best-practices. - Install:
npx skills add vercel-labs/agent-skills@vercel-react-best-practices -g -y - Verify:
npx skills check-- confirm skill appears in list. - Run the installed skill to help with the React performance task.
- Registry: CCPM (document processing topic).
- Search:
ccpm search pdf - Check details:
ccpm info pdf - Install:
ccpm install pdf - Verify:
ccpm list-- confirmpdfappears. - Remind user to restart Claude Code for CCPM skills to load.
- Run both:
ccpm listandnpx skills check - Combine results into a single list grouped by registry.
- Report total count and highlight any skills with available updates.
- Registry unclear -- run both searches.
- Search:
npx skills find testingandccpm search testing - Present combined results:
- Open Ecosystem:
playwright-testing,jest-helpers,vitest-runner - CCPM: (no results)
- Open Ecosystem:
- Recommend the best match based on the user's project context.
- Install the chosen skill from the matching registry.
- Registry: Open Ecosystem (DevOps topic).
- Search:
npx skills find kubernetes autoscaling-- no results. - Broaden search:
npx skills find kubernetes-- still no results. - Search CCPM as fallback:
ccpm search kubernetes-- no results. - Tell the user: "No matching skill found in either registry."
- Offer to help directly with Kubernetes autoscaling using built-in knowledge.
- Offer to create a custom skill:
npx skills init kubernetes-autoscaling
Troubleshooting
| Problem | Fix |
|---|---|
ccpm: command not found |
Run npm install -g @daymade/ccpm |
npx skills hangs or fails |
Check Node.js version is 18+: node --version |
| Skill not available after CCPM install | Restart Claude Code -- skills load at startup |
| Permission errors on install | Check write permissions: ls -la ~/.claude/skills/ and fix with chmod -R u+rw ~/.claude/skills/ |
| Install succeeds but skill not in list | Run npx skills check or ccpm list again. If still missing, reinstall with --force flag |
| Search returns too many results | Add more specific keywords to narrow the query |
References
| File | Purpose |
|---|---|
references/registry-commands.md |
Full CLI command reference for both registries and common search categories |