Find Skill

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

Security Scan

The skill's instructions match its stated purpose (finding and installing other skills) but they instruct the agent to run npx installs (including global, unattended installs) without requiring or documenting the npx/npm binary, and that enables the agent to pull and run arbitrary third‑party code — this is coherent with the purpose but raises security concerns the user should understand before proceeding.

Purpose & Capability

The name/description match the SKILL.md: the skill is an instruction-only assistant that uses the 'skills' CLI (npx skills) to find and add skills. However the skill declares no required binaries while the runtime guidance assumes npx/npm is available — a minor mismatch that should be documented or enforced.

Instruction Scope

Instructions ask the agent to run 'npx skills find' and 'npx skills add', and to use 'npx skills add <owner/repo@skill> -g -y' to install globally and skip confirmations. That is within the stated purpose (discover/install skills) but grants the agent the ability to download and execute arbitrary third‑party packages silently; the SKILL.md does not instruct reviewing package source or permissions.

Install Mechanism

This skill is instruction-only (no install spec and no code files) which is low-risk. But the recommended install mechanism (npx skills add) will fetch code from remote sources (GitHub/registry) when used — the skill itself does not restrict or advise vetting those downloads.

Credentials

The skill requests no environment variables, credentials, or special config paths — nothing appears disproportionate in declared env/cred requirements.

Persistence & Privilege

always is false (good) but the platform default allows autonomous invocation. Combined with instructions to install arbitrary skills (including global, unattended installs), this increases the blast radius: an agent that can run commands could install other skills which themselves can run code. The SKILL.md does not recommend safeguards (user confirmation, sandboxing, review).

What to consider before installing

This skill is what it says: a helper that runs the 'skills' CLI via npx to find and add other skills. Before using it, ensure you: (1) have npx/npm and understand what 'npx skills add' will do on your system; (2) do not allow unattended/global installs (-g -y) unless you trust the package source; (3) review the target skill's repository or package before installing (look for code, maintainer, popularity, and permissions); (4) prefer local or sandboxed installs rather than global installs; and (5) consider disabling autonomous agent installation or requiring explicit user confirmation so the agent cannot silently pull and run third‑party code. If you want, I can show how to manually inspect a candidate skill repo before installing it.

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