Find Skills

Find Skills

Search query: $ARGUMENTS

If $ARGUMENTS is empty, ask the user what skill they need.

Step 1: Pick the Registry

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:

1. Check the error message from the install command output.
2. Run the install command again with verbose output.
3. Check write permissions: ls -la ~/.claude/skills/
4. If the skill still does not appear, consult the Troubleshooting section below.

When No Skills Are Found

1. Tell the user no matching skill exists in either registry.
2. Attempt the task directly using built-in capabilities.
3. If the user wants a reusable solution, offer to create a custom skill:
   • Open Ecosystem: npx skills init my-skill
   • CCPM: invoke /create-skill

1. Registry: Open Ecosystem (general coding topic).
2. Search: npx skills find react performance
3. Results show vercel-labs/agent-skills@vercel-react-best-practices.
4. Install: npx skills add vercel-labs/agent-skills@vercel-react-best-practices -g -y
5. Verify: npx skills check -- confirm skill appears in list.
6. Run the installed skill to help with the React performance task.

1. Registry: CCPM (document processing topic).
2. Search: ccpm search pdf
3. Check details: ccpm info pdf
4. Install: ccpm install pdf
5. Verify: ccpm list -- confirm pdf appears.
6. Remind user to restart Claude Code for CCPM skills to load.

1. Run both: ccpm list and npx skills check
2. Combine results into a single list grouped by registry.
3. Report total count and highlight any skills with available updates.

1. Registry unclear -- run both searches.
2. Search: npx skills find testing and ccpm search testing
3. Present combined results:
   • Open Ecosystem: playwright-testing, jest-helpers, vitest-runner
   • CCPM: (no results)
4. Recommend the best match based on the user's project context.
5. Install the chosen skill from the matching registry.

1. Registry: Open Ecosystem (DevOps topic).
2. Search: npx skills find kubernetes autoscaling -- no results.
3. Broaden search: npx skills find kubernetes -- still no results.
4. Search CCPM as fallback: ccpm search kubernetes -- no results.
5. Tell the user: "No matching skill found in either registry."
6. Offer to help directly with Kubernetes autoscaling using built-in knowledge.
7. Offer to create a custom skill: npx skills init kubernetes-autoscaling

Troubleshooting

References

Converted and distributed by TomeVault — claim your Tome and manage your conversions.