Index of every page on this site: llms.txt
All skills
brianlovin avatar

/find-skills

@1a9819e official
by Brian Lovinbrianlovin/agent-config377 stars
33
Run it yourself

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. This skill should be used when the user is looking for functionality that might exist as an installable skill.

Use this Skill: https://skilld.dev/gh/brianlovin/agent-config/find-skills

Nothing lands on disk. Nothing to clean up.

Fork this Skill

Edit a local copy. It keeps the author and licence.

SKILL.md

≈79 tokens for metadata: the name and description. ≈1.1k when used: this file.

Description uses 4.0% of example budget

Before choosing a Skill, your Agent reads its name and description. All available Skills share that space.

  • A shorter description leaves more room for other Skills. This entry exceeds our 1% size suggestion.

In our Claude Code example, all Skill names and descriptions share 8,000 characters. This Skill uses ≈317 characters, or 4.0%.

The 1% threshold is a size suggestion. Longer descriptions can still fit.

Your model, settings, and other Skills decide how much text your Agent can read.

Example settings and source

The example uses a 200k-token context and default Claude Code settings. The count includes the name, description, separators, and when_to_use when present. Codex also counts local file paths.

Skit's source and limits: Codex 0.160.1, Claude Code 2.1.292.

Find Skills

This skill helps you discover and install skills from the open agent skills ecosystem.

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 the Skills CLI?

The Skills CLI (npx skills) is the package manager for the open agent skills ecosystem. Skills are modular packages that extend agent capabilities with specialized knowledge, workflows, and tools.

Key commands:

  • npx skills find [query] - Search for skills interactively or by keyword
  • npx skills add <package> - Install a skill from GitHub or other sources
  • npx skills check - Check for skill updates
  • npx skills update - Update all installed skills

Browse skills at: https://skills.sh/

How to Help Users Find Skills

Step 1: Understand What They Need

When a user asks for help with something, identify:

  1. The domain (e.g., React, testing, design, deployment)
  2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
  3. Whether this is a common enough task that a skill likely exists

Step 2: Search for Skills

Run the find command with a relevant query:

npx skills find [query]

For example:

  • User asks "how do I make my React app faster?" → npx skills find react performance
  • User asks "can you help me with PR reviews?" → npx skills find pr review
  • User asks "I need to create a changelog" → npx skills find changelog

The command will return results like:

Install with npx skills add <owner/repo@skill>

vercel-labs/agent-skills@vercel-react-best-practices
└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices

Step 3: Present Options to the User

When you find relevant skills, present them to the user with:

  1. The skill name and what it does
  2. The install command they can run
  3. A link to learn more at skills.sh

Example response:

I found a skill that might help! The "vercel-react-best-practices" skill provides
React and Next.js performance optimization guidelines from Vercel Engineering.

To install it:
npx skills add vercel-labs/agent-skills@vercel-react-best-practices

Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices

Step 4: Offer to Install

If the user wants to proceed, you can install the skill for them:

npx skills add <owner/repo@skill> -g -y

The -g flag installs globally (user-level) and -y skips confirmation prompts.

Common Skill Categories

When searching, consider these common categories:

Category Example Queries
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
Productivity workflow, automation, git

Tips for Effective Searches

  1. Use specific keywords: "react testing" is better than just "testing"
  2. Try alternative terms: If "deploy" doesn't work, try "deployment" or "ci-cd"
  3. Check popular sources: Many skills come from vercel-labs/agent-skills or ComposioHQ/awesome-claude-skills

When No Skills Are Found

If no relevant skills exist:

  1. Acknowledge that no existing skill was found
  2. Offer to help with the task directly using your general capabilities
  3. Suggest the user could create their own skill with npx skills init

Example:

I searched for skills related to "xyz" but didn't find any matches.
I can still help you with this task directly! Would you like me to proceed?

If this is something you do often, you could create your own skill:
npx skills init my-xyz-skill

Source: SKILL.md on GitHub

Skill behaviors

skilld matched fixed text patterns in SKILL.md and file names. Patterns miss obfuscated code.

skilld run checks every file with the same patterns. It asks for approval before it loads a Skill with a behavior marked Needs approval.

Third-party checks

2 warnings1mo4 checks · Risk SAFE
  • Gen Agent Trust Hub1mo

    This skill provides the agent with tools to discover, search for, and install extensions from the open agent skills ecosystem using the Skills CLI tool. It facilitates the installation of third-party code from external sources like GitHub, often bypassing confirmation prompts. It also introduces a surface for indirect prompt injection via the results of skill searches.

  • Socket1mo

    1 alert: gptSecurity

  • Snyk1mo

    Risk: MEDIUM · 1 issue

  • Runlayer7mo

    1 file scanned · No issues

Provenance

Signed by skilld at 1a9819e. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub last week.

Dormantupdated 9 months ago

Topics

  • CLI
  • skills
  • discovery
  • package-manager
  • agent-skills
  • installation
  • workflow
  • ecosystem

README badge

README badge for brianlovin/agent-config/find-skills

What it does

Instructs Claude to search and install skills from the open agent skills ecosystem when users ask for help with specific tasks or capabilities. Uses the Skills CLI (`npx skills find`) to discover relevant skills and guide installation. Most useful when a user asks "how do I do X" or "is there a skill for X" where X is a common domain like testing, deployment, or React optimization.

Generated from the current SKILL.md.

Frequently asked

What is the Skills CLI and how do I use it?
The Skills CLI (`npx skills`) is a package manager for agent skills. Use `npx skills find [query]` to search for skills, `npx skills add <owner/repo@skill>` to install one, and `npx skills check` or `npx skills update` to manage installed skills.
When should I use this skill?
Use this skill when a user asks how to do something, requests help with a specialized task, or expresses interest in extending agent capabilities—like 'find a skill for X' or 'can you help with Y domain'.
Can I install skills globally?
Yes. Use `npx skills add <owner/repo@skill> -g -y` to install globally at the user level; the `-g` flag installs globally and `-y` skips confirmation prompts.
What should I do if no skill exists for what the user needs?
Acknowledge that no matching skill was found, offer to help with the task directly using general capabilities, and optionally suggest the user create their own skill with `npx skills init`.

Generated from the current SKILL.md. These answers refresh after source changes.