find-skills
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. Uses reskill as the package manager.
reskill · Static checks on file
Installation
Read the source and dependencies before running a command. Copying does not install or execute anything.
npx skills add kanyun-inc/reskill --skill find-skillsAbout this skill
name: find-skills description: Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. Uses reskill as the package manager. version: 0.2.0 author: reskill tags:
- discovery
- search
- skills
- package-manager
Find Skills (reskill)
This skill helps you discover and install skills from the reskill ecosystem.
Key Principles:
- Search → Present → Ask → Install — always show results first, ask the user before installing.
- Be registry-aware — check if the project has a configured registry (private or public) and tell the user which registry you're searching. If results are empty, suggest the user may need to configure a private registry.
When to Use This Skill
Use this skill when the user:
- Asks "how do I do X" where X might be a common task with an existing skill
- Says "find a skill for X" or "is there a skill for X"
- Asks "can you do X" where X is a specialized capability
- Expresses interest in extending agent capabilities
- Wants to search for tools, templates, or workflows
- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
What is reskill?
reskill is a Git-based package manager for AI agent skills. It provides declarative configuration, version locking, and seamless synchronization for managing skills across projects and teams.
CLI usage:
If reskill is installed globally, use it directly. Otherwise use npx reskill@latest:
# Global install
reskill <command>
# Or via npx (no install needed)
npx reskill@latest <command>
Registry configuration:
The find command automatically resolves the registry in this order:
--registry <url>CLI option (highest priority)RESKILL_REGISTRYenvironment variabledefaults.publishRegistryinskills.json- Public registry
https://reskill.info/(fallback)
To configure a custom registry for the project, add it to skills.json:
{
"defaults": {
"publishRegistry": "https://your-registry.example.com/"
}
}
Once configured, all find / install commands will use it automatically — no need to pass --registry every time.
Key commands for skill discovery:
reskill find <query>— Search for skills by keywordreskill find <query> --json— Search with machine-readable JSON outputreskill install <ref>— Install a skillreskill list— List installed skillsreskill info <skill>— Show skill details
How to Help Users Find Skills
Step 0: Check Registry Context
Before searching, determine which registry to use (see "Registry configuration" above for the full priority order).
Check these sources:
RESKILL_REGISTRYenvironment variabledefaults.publishRegistryinskills.json
If either is configured → use it, and tell the user which registry you're searching.
If neither is configured → ask the user before proceeding:
No private registry is configured for this project.
Do you want to search a private registry? If so, provide the URL
(e.g. --registry https://your-registry.example.com/).
Otherwise, I'll search the public registry (reskill.info).
Once the user responds:
- User provides a URL → use it with
--registry <url> - User says no / skip → proceed with the public registry (
https://reskill.info/)
Step 1: Understand What They Need
When a user asks for help with something, identify:
- The domain (e.g., React, testing, design, deployment)
- The specific task (e.g., writing tests, creating animations, reviewing PRs)
- Whether this is a common enough task that a skill likely exists
Step 2: Search for Skills (Progressive Strategy)
Use --json for structured results:
npx reskill@latest find "<query>" --json
The JSON output has this structure:
{
"total": 2,
"items": [
{
"name": "@scope/skill-name",
"description": "What this skill does",
"latest_version": "1.0.0",
"keywords": ["keyword1", "keyword2"],
"publisher": { "handle": "author" },
"updated_at": "2025-01-01T00:00:00Z"
}
]
}
IMPORTANT: Use progressive search to maximize results. The registry may not support multi-word fuzzy matching, so follow this strategy:
Round 1: Try the natural query first
npx reskill@latest find "frontend design" --json
If total > 0, proceed to Step 3 (present results).
Round 2: Try hyphenated version
Skill names often use hyphens. If Round 1 returns 0 results, try connecting keywords with a hyphen:
npx reskill@latest find "frontend-design" --json
Round 3: Broaden to the most relevant single keyword
If still 0 results, pick the most specific keyword from the user's query and search with that alone:
npx reskill@latest find "frontend" --json
Choose the keyword that best narrows the domain (e.g., prefer "frontend" over "design" because "design" is too broad).
Round 4 (optional): Try alternative/synonym keywords
If still no results, try synonyms or related terms:
- "frontend" → "ui", "web", "react"
- "deploy" → "deployment", "ci-cd", "devops"
- "test" → "testing", "jest", "playwright"
Agent-side filtering
When broader searches return multiple results, read each item's description field and filter by relevance to the user's original request. Only present skills whose description genuinely matches what the user needs. Do not present all results blindly.
Example flow — user asks "help me with frontend design":
1. find "frontend design" → 0 results
2. find "frontend-design" → 0 results
3. find "frontend" → 3 results
4. Read descriptions → filter → 1 result is relevant to UI design
5. Present that 1 result to user
Search query examples:
| User says | Round 1 | Round 2 (hyphen
Read the complete source ↗