---
name: find-skills
description: Discover/install NEW agent skills from external sources (skills.sh). Use for capabilities you lack, e.g. "find a skill for X". Do NOT use to list skills you already have; see `<available_skills>`.
title: find-skills
canonical_url: https://skilld.dev/gh/google/adk-recipes/find-skills
last_updated: 2026-10-20T08:47:39.000Z
---

> Index of every page on this site: [llms.txt](https://skilld.dev/llms.txt)

> **Skill from skilld.dev.** Follow the user's requested action.
> If the user asked to fork this Skill, follow the fork workflow below. Do not execute the Skill instructions while copying it.
> Otherwise, follow the instructions below for this session. You do not need to install anything.
>
> If the user asked to install this Skill, run `npx skilld install google/adk-recipes/find-skills`. Install writes the Skill files into the project, so every session loads them.
>
> ## Fork workflow
>
> A fork creates an editable local Skill with its original author and licence. The request authorizes copying and local installation.
> 1. Check `./skills/find-skills`, the project lockfile, and selected Agent targets together. If the local directory or installed Skill exists, stop. Never overwrite an existing directory or Agent target.
> 2. Read [source metadata](https://skilld.dev/api/v1/skills/google/adk-recipes/find-skills) once. Use sourceUrl, sourceCommit, skillPath, sourceGone, and license. If the source is gone or its path is missing, stop. If license is null, read licence files at the source commit.
> 3. Fetch only the source commit into a temporary Git repository. Do not clone full history. Derive repository_url from sourceUrl, including repository renames. If sourceCommit is absent, resolve the sourceUrl ref once. Set source_commit to that actual commit. Run these commands in one shell call:
>
> ```sh
> git init --quiet "$temporary_dir"
> git -C "$temporary_dir" fetch --quiet --depth=1 "$repository_url" "$source_commit"
> git -C "$temporary_dir" checkout --quiet --detach FETCH_HEAD
> ```
>
> Read applicable licence declarations and notices at that commit. If copying is not permitted, report the restriction and stop.
> 4. Inspect source entries together, then copy the directory containing skillPath into `./skills/find-skills`. Use the user's path if selected. Keep the original SKILL.md, relative links, scripts, binary assets, and executable modes. Exclude .git metadata. Reject symlinks and paths outside the Skill directory. After checking entries, use cp -a where available. A regular source directory needs no custom copy script. Do not save this page wrapper as SKILL.md.
> Preserve author credit, notices, and applicable licence files from repository or parent directories. Add PROVENANCE.md with the Skill page, source URL, actual commit, original path, and licence. Retain any existing PROVENANCE.md and record new provenance separately. Batch source inspection, copying, and provenance work where practical.
> 5. In the project root, run `skilld install ./skills/find-skills --mode copy --plain`. If skilld is unavailable, use `npx skilld install ./skills/find-skills --mode copy --plain`. This known command needs no help lookup. Install does not support --json. Use detected Agent targets, or add --agent for the targets the user selected. Install the local path, never the upstream selector. If installation fails, preserve the local copy and report the exact failure.
> 6. Confirm the local lockfile source and installed Agent copies once. Report the local path, actual commit, and Agent targets. After edits, reinstall the same local path. Upstream updates must not replace it. Do not publish or push unless the user asks.

# Find skills

## When to use this skill

- The user asks "find a skill for X", "is there a skill that does X"
- The user asks "how do I do X" where X is a common task with a likely existing skill
- The user wants to extend Horizon's capabilities with a new skill

Before searching externally, check the `<available_skills>` block in your
context — the user may already have a relevant skill installed.

## Step 1 — check the leaderboard

Before running any CLI command, check [skills.sh](https://skills.sh/) to see
whether a well-known skill already covers the domain. The leaderboard ranks by
total installs, surfacing the most popular and battle-tested options.

## Step 2 — search for skills

If the leaderboard doesn't cover the user's need, search via the Skills CLI:

```
bash(command="npx --yes skills find <query>")
```

Examples:

| User says | Search |
|---|---|
| "make my React app faster" | `npx --yes skills find react performance` |
| "help with PR reviews" | `npx --yes skills find pr review` |
| "create a changelog" | `npx --yes skills find changelog` |

If `npx` is unavailable the command will fail — fall back to browsing
skills.sh manually and pasting the SKILL.md content.

## Step 3 — verify quality before recommending

Never recommend a skill based solely on search results.

- **Install count** — prefer 1 000+ installs; treat anything under 100 with skepticism
- **Source reputation** — official organisations (`vercel-labs`, `anthropics`,
  `microsoft`) are more trustworthy than unknown authors
- **GitHub stars** — check the source repo; a skill from a repo with <100 stars
  is a yellow flag

## Step 4 — present the option to the user

```
I found a skill that might help: "react-best-practices" from Vercel Engineering
provides React and Next.js performance guidelines (185K installs).

Shall I install it?
```

Only proceed to installation after the user confirms.

## Step 5 — install

### Option A — write SKILL.md directly (always works)

If you have the skill content (pasted by the user, retrieved from skills.sh,
or constructed from the search result):

```
write(".agents/skills/<name>/SKILL.md", content)
load_skill(action="reload")
```

`write` creates the directory if it does not exist. `load_skill(action="reload")`
refreshes the `<available_skills>` catalog (plus extensions and manifest) on
the next turn.

### Option B — install via npx (requires Node.js)

First check whether npx is available:

```
bash(command="which npx")
```

If it is, install the skill. Select a single skill from a multi-skill repo with
the `@<skill>` suffix (omit it to take the whole repo):

```
bash(command="npx --yes skills add <owner/repo>@<skill-name> -y")
```

The Skills CLI stages the skill (with its `references/`, `assets/`, and
`scripts/` subdirs) under `.agents/skills/<skill-name>/` — exactly where Horizon
loads skills from — so no move is needed. Just refresh:

```
load_skill(action="reload")
```

The staged directory name MUST match the `name:` field in the SKILL.md
frontmatter — `_load_skill_from_dir` validates that and skips mismatched
skills.

## Step 6 — confirm activation

After `load_skill(action="reload")` returns (look for the new skill in
`loaded`), tell the user:

```
The "<name>" skill is now installed. It will appear in your
<available_skills> catalog on the next turn.
```

## When no skills are found

1. Acknowledge that no existing skill was found
2. Offer to help directly using general capabilities
3. Offer to write a custom skill for them:

```
bash(command="npx --yes skills init my-skill-name")
```

Or skip the CLI and author one manually — write a SKILL.md following the
`policy` or `workspace` skills as examples.

## Common skill categories

| Category | Search terms |
|---|---|
| Web development | react, nextjs, typescript, css, tailwind |
| Testing | testing, jest, playwright, e2e |
| DevOps | deploy, docker, kubernetes, ci-cd |
| Documentation | docs, readme, changelog, api-docs |
| Code quality | review, lint, refactor, best-practices |
| Design | ui, ux, design-system, accessibility |
