Find Skills

---
name: find-skills
description: Search and discover skills for the agent. Use when the user expresses intent to find a skill, search for a skill, or needs a skill to solve a specific problem. Triggers on phrases like "find skill", "search skill", "look for skill", or when the user describes a problem and asks for a skill recommendation. Also triggers when the user asks about available skills or skill discovery.
---

# Find Skills

Search and discover skills across multiple sources to help users find the right capability for their needs.

> **Ported note.** This package arrived branded for a different agent runtime: it named that
> runtime's sandboxed skill directories and its own tool names, none of which exist on Claude Code
> or opencode, so the skill could only ever report "nothing found". Those names are deliberately not
> repeated here — **the paths and tools listed below are the only ones to use.**

## Where skills actually live

Check the host you are running on; both may be present.

**Claude Code**

| Scope | Path |
| --- | --- |
| Personal | `~/.claude/skills/` |
| Project | `<project>/.claude/skills/` |
| Plugin-provided | `~/.claude/plugins/cache/<marketplace>/<plugin>/<version>/skills/` |

**opencode**

| Scope | Path |
| --- | --- |
| Personal | `~/.config/opencode/skills/` |
| Project | `<project>/.opencode/skills/` |
| Extra roots | every entry in `skills.paths` in `~/.config/opencode/opencode.json` |

**Tools:** list and read with `Bash` (`ls`, `cat`) and `Read`; search the web with `WebSearch`;
fetch a page with `WebFetch`. On opencode the equivalents are `bash`, `read`, `websearch`, `webfetch`.

## Workflow

### Step 1: Check the skills already installed

Before searching anywhere else, enumerate the directories above and read the `SKILL.md` frontmatter
(`name` + `description`) of anything that looks close:

```bash
ls ~/.claude/skills/ 2>/dev/null
ls ~/.config/opencode/skills/ 2>/dev/null
ls .claude/skills/ .opencode/skills/ 2>/dev/null
```

**Prefer an installed skill over a remote one every time** — it needs no install step, no network,
and its provenance is already whatever the user accepted when they installed it.

If a match is found, present its name and description and confirm it meets the need.

### Step 2: Ask before searching outside

If nothing installed matches:

> No installed skill matches. Would you like me to search further — public skill repositories on
> GitHub, and skill marketplaces?

Wait for confirmation. Do not search the web unasked.

### Step 3: Search externally (only after confirmation)

Stop and present as soon as a suitable match is found.

**3.1 GitHub** — `WebSearch`:
- `agent skill <keywords>` · `claude skill <keywords>` · `site:github.com SKILL.md <keywords>`

Evaluate by:
1. **Description relevance** — does the README/SKILL.md actually solve the user's problem?
2. **Recent activity** — prefer maintained repositories.
3. **Stars** — weak community signal, never a substitute for reading the skill.

**3.2 Skill marketplaces** — fetch with `WebFetch` and search by keyword.

Present the top one or two with: name and link, a one-line description, why it matches, and how to
install it.

### Step 4: Summarize

- **Found**: present the skill and how to use it.
- **Not found**: say so plainly, then offer to write a purpose-built skill, or to do the task with
  ordinary agent capabilities and no skill at all.

## Before recommending a third-party skill

A skill is **instructions the agent will follow** and may carry payload scripts. Say so:

- Name the source (repo/marketplace) and let the user decide.
- Note if it ships executable payload, and that installing is not the same as running it.
- Never install one without being asked to.

## Search strategy tips

- **Keyword extraction**: reduce the request to 1–3 concrete keywords.
- **Fuzzy matching**: try synonyms — "PDF editor" → "PDF modify", "PDF manipulation".
- **Problem-to-skill mapping**: when the user describes a problem rather than naming a skill, infer
  the capability first, then search for that. "I need to merge PDFs" → search PDF skills.