Proactively discover, install, and create Claude skills for specialized tasks...
Dynamically discover, install, and create skills to expand Claude's capabilities on-demand.
PROACTIVELY use this skill when:
User requests new capability
Specialized domain encountered
Knowledge gap recognized
Recurring specialized need
DO NOT activate for:
Interpret the user's request and extract relevant search terms:
martial arts combat self-defensestripe payments billing apiopensea nft marketplace apiUse multiple related keywords to maximize match potential.
Query the skills API:
https://claude-plugins.dev/api/skills?q=<keywords>
Use WebFetch to retrieve results. The API returns:
{
"skills": [{
"name": "skill-name",
"namespace": "@author/repo/skill-name",
"description": "What the skill does...",
"stars": 12345,
"installs": 678,
"metadata": {
"rawFileUrl": "https://raw.githubusercontent.com/..."
}
}],
"total": 100
}
Rank by:
1000 stars: High confidence
100 stars: Moderate confidence
Credible match criteria:
Run the install command:
npx claude-plugins skills install <namespace> --local
Where <namespace> is the full namespace from the API (e.g., @anthropics/claude-code/frontend-design).
The --local flag installs to the project's .claude/skills/ directory.
After installation, inform the user:
I've learned
<skill-name>- [brief description of capability]. Let me apply this to your task.
Then immediately use the new skill to address the user's original request.
Only create a skill if:
Do NOT create if:
Creation process:
Research the domain
Design the skill
Create the skill files
Create directory: .claude/skills/<skill-name>/
Create SKILL.md with:
---
name: skill-name
description: Clear description of what it does and when to use it.
---
Add body with:
Add supporting files if needed
scripts/ for automationreferences/ for documentationtemplates/ for boilerplateInform the user
I've created a custom skill for [domain] based on my research. I can now [list capabilities]. Let me help with your task.
User: "I want to build beautiful frontend interfaces"
Claude thinking:
- This is a specialized design skill request
- Search: "frontend design ui interface"
- Found: frontend-design with 45k stars
- High relevance + high quality = credible match
Claude action:
npx claude-plugins skills install @anthropics/claude-code/frontend-design --local
Claude response:
"I've learned frontend-design - expertise in creating distinctive, production-grade interfaces. Let me help you build something beautiful..."
User: "Help me integrate OpenSea's API to list NFTs"
Claude thinking:
- NFT marketplace API = specialized domain
- I should check for existing skills
- Search: "opensea nft api marketplace"
- Found: opensea-api with good ratings
Claude action:
npx claude-plugins skills install @creator/skills/opensea-api --local
Claude response:
"I've equipped myself with OpenSea API expertise. I can now help you authenticate, list items, fetch collections, and handle marketplace transactions. Let's set up your NFT listing..."
User: "I need to work with Acme Corp's proprietary data format"
Claude thinking:
- Very specialized/proprietary domain
- Search: "acme corp data format"
- No credible matches found
- This is genuinely specialized, not just complex
- User likely needs this repeatedly
- I should create a skill
Claude action:
1. WebSearch for Acme Corp documentation
2. Research the data format specification
3. Create .claude/skills/acme-data-handler/SKILL.md
Claude response:
"I've created a custom skill for Acme Corp data formats based on their documentation. I can now parse, validate, and transform Acme data files. Let me help with your specific task..."
User: "Write a binary search implementation"
Claude thinking:
- This is a standard algorithm
- Base model handles this perfectly
- Not specialized, just programming
- No skill needed
Claude action:
Proceed directly with the task without skill search.
If npx claude-plugins isn't available, fall back to manual installation:
rawFileUrl from the API response.claude/skills/Prefer:
updatedAt)Install the best match and mention alternatives exist if user wants different approach.
Before auto-installing, verify:
Before creating a skill, verify: