Skills Search
Search the CCPM registry, install skills, and list what is already on your machine without leaving the agent session.
Overview
Skills-search is an agent skill most often used in Build (also Idea discover) that searches, installs, and manages Claude Code skills from the CCPM registry by running `ccpm` for you.
Install
npx skills add https://github.com/daymade/claude-code-skills --skill skills-searchWhat is this skill?
- Auto-bootstraps with `ccpm setup` or `npx @daymade/ccpm` when the CLI is missing
- Maps natural-language intents (find, install, list, explain) to concrete `ccpm` subcommands
- Runs Bash itself instead of handing copy-paste commands to the user
- Covers registry search, installs, and installed-skill inventory in one workflow
- Uses Read for local skill metadata when users ask what a skill does
- Intent-mapping table ties find, install, list, and explain flows to discrete `ccpm` actions
- Bootstrap path uses a single `npx @daymade/ccpm setup` when `ccpm` is not on PATH
Adoption & trust: 542 installs on skills.sh; 1.2k GitHub stars; 2/3 security scanners passed (skills.sh audits).
What problem does it solve?
You know you need a skill from the registry but waste time copying CLI commands or guessing package names instead of letting the agent run discovery and install.
Who is it for?
Claude Code users who want hands-off CCPM search, install, and inventory from chat triggers like “find skills for PDF” or “what does skill-creator do”.
Skip if: Teams that forbid shell execution in the agent, or builders who only use skills.sh/Prism browse and never install via CCPM.
When should I use this skill?
Users want to search, discover, install, or manage Claude Code skills from the CCPM registry—including phrases like find skills for PDF, install a named skill, or list installed skills.
What do I get? / Deliverables
The agent returns matching registry skills, installs the one you pick, or lists installed plugins—with CCPM bootstrapped if it was missing.
- Registry search results for the requested capability
- Installed or updated skill/plugin on the local Claude Code setup
- Inventory of currently installed skills when listing is requested
Recommended Skills
Journey fit
Spans multiple journey phases - primary shelf plus alternate fits below.
Installing and curating Claude Code capabilities is core agent-tooling work during the build phase. CCPM search/install is the operational layer on top of the agent stack—not generic app coding.
Where it fits
Scan CCPM for PDF or doc skills before choosing a document pipeline for the product.
Install a named skill from the registry mid-sprint without leaving the coding session.
List installed skills to audit overlap before adding another review or DevOps plugin.
Search for code-review skills to tighten pre-release checks once features are frozen.
How it compares
Registry CLI orchestration for Claude Code plugins—not a generic web search skill or an MCP server catalog.
Common Questions / FAQ
Who is skills-search for?
Solo and indie builders on Claude Code who manage skills through CCPM and want the agent to run registry commands instead of surfacing manual steps.
When should I use skills-search?
During build when extending agent-tooling (install cloudflare-troubleshooting, list installed skills), or in idea/discover when exploring what plugins exist before you commit to a stack.
Is skills-search safe to install?
It is allowed to run Bash and Read; review the Security Audits panel on this Prism page and treat `ccpm`/npx installs like any third-party CLI before running in production repos.
SKILL.md
READMESKILL.md - Skills Search
Security scan passed Scanned at: 2025-11-30T03:26:12.206682 Tool: gitleaks + pattern-based validation Content hash: 493826cb21eefb61a82bf0a81dbccec44888e7b68b21bfdd02a2dd301805a695 --- name: skills-search description: This skill should be used when users want to search, discover, install, or manage Claude Code skills from the CCPM registry. Triggers include requests like "find skills for PDF", "search for code review skills", "install cloudflare-troubleshooting", "list my installed skills", "what does skill-creator do", or any mention of finding/installing/managing Claude Code skills or plugins. allowed-tools: Bash, Read --- # 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: ```bash # 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 1. **Always execute directly** — run `ccpm` commands via the Bash tool, never ask the user to run them manually. 2. **Summarize results** — after executing, present the output in a clear, readable format. 3. **Suggest next steps** — after search results, offer to install. After install, remind the user to restart Claude Code. 4. **Handle errors gracefully** — if `ccpm` is not found, fall back to `npx @daymade/ccpm`. If the registry is unreachable, say so clearly. 5. **Namespaced skills** — support `@org/skill-name` format (e.g., `ccpm install @daymade/skill-creator`). ## Command Reference ### Search ```bash ccpm search <query> [--limit <n>] [--tags <t1,t2>] [--author <name>] [--smart] ``` ### Discovery ```bash ccpm popular [--limit <n>] # Most downloaded ccpm recent [--limit <n>] # Recently published/updated ``` ### Install & Manage ```bash 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: ```json { "mcpServers": { "skill-search": { "command": "npx", "args": ["-y", "skills-search-mcp"] } } } ``` Both this skill and the MCP server wrap the same `ccpm` CLI — they are compl