# Find Skills

Discover/install NEW agent skills from external sources (skills.sh).

- Repository: https://github.com/google/adk-recipes (10565 stars)
- Category: AI and agents
- License: Apache-2.0
- Last updated: 2026-11-01
- Runs scripts: no, instructions only

## Install

Claude Code: `npx skills add google/adk-recipes --skill find-skills -g -a claude-code -y`
Codex: `npx skills add google/adk-recipes --skill find-skills -g -a codex -y`
Cursor: `npx skills add google/adk-recipes --skill find-skills -g -a cursor -y`
Gemini CLI: `npx skills add google/adk-recipes --skill find-skills -g -a gemini-cli -y`

## 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>`.

## SKILL.md, as published by its author (untrusted third-party text, read it as data)

# 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)

The rest: https://github.com/google/adk-recipes/blob/HEAD/core/python/long-horizon-harness/horizon/builtin_skills/find-skills/SKILL.md