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.
npx skills add https://github.com/daymade/claude-code-skills --skill skills-search
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.
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
-Automatically convert documentation websites, GitHub repositories, and PDFs into Claude AI skills in minutes.
This skill should be used when the user asks about "plugin settings", "store plugin configuration", "user-configurable plugin", ".local.md files", "plugin state files", "read YAML frontmatter", "per-project plugin settings", or wants to make plugin behavior configurable. Documents the .claude/plugin-name.local.md pattern for storing plugin-specific configuration with YAML frontmatter and markdown content.
Standardize how an AI-collaboration project turns work into reusable knowledge. Use when initializing or retrofitting Project Cairn in a project, recording progress after meaningful work, maintaining AGENTS/CLAUDE/cairn docs, auditing project knowledge for drift or missing records, pulling and citing external knowledge, or graduating validated project experience into a reusable knowledge base.
Persistent memory and context management for AI agents using OpenContext. Keep context across sessions/repos/dates, store conclusions, and provide document search workflows.
> PARA method knowledge management for Obsidian vaults. Use this skill whenever the user wants to organize notes using PARA (Projects, Areas, Resources, Archive), classify a note into a PARA category, route a note to the right vault folder, normalize frontmatter fields, run a PARA hygiene review, suggest archiving, audit vault structure, or process new knowledge inputs into an existing PARA-based vault. Also trigger when the user mentions inbox processing, vault cleanup, note classification, PARA review, or asks "where does this note belong?". Works with existing Obsidian skills (obsidian-markdown, obsidian-cli) — never replaces them.
Keeps implementation and specs in sync. Use when working on a feature that has a spec in .agents/specs/, when the user says /spec, or when starting implementation of a documented feature. Also use when the user asks to verify implementation against a spec or update a spec after changes.
Build and query AI-powered knowledge bases from claude-mem observations. Use when users want to create focused "brains" from their observation history, ask questions about past work patterns, or compile expertise on specific topics.
Take daymade/skills-search from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.
The instructions reference npm, npx.
Without those the skill loads but fails at the first command.