Find Skills

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 and requirements are consistent with its stated purpose (finding and installing agent skills); it is instruction-only and requests no credentials, though its recommendation to perform global, unattended installs is a practical risk users should be aware of.

Purpose & Capability

Name, description, and runtime instructions all describe searching for and installing skills via the 'npx skills' CLI. No unrelated binaries, env vars, or config paths are requested — the capabilities requested are proportional to the stated purpose.

Instruction Scope

Instructions stay on-topic (search and install via 'npx skills'). However the doc explicitly recommends using 'npx skills add <pkg> -g -y' (global + skip prompts), which would install arbitrary third‑party packages without confirmation. That is coherent with the goal but increases operational risk; the agent should not auto-install packages without explicit user consent and verification of the package source.

Install Mechanism

This skill is instruction-only and has no install spec or bundled code. The only installation mechanism it references is 'npx skills', which executes packages from npm/remote sources — expected for a skill-discovery helper but implies that installing discovered skills will fetch and run third‑party code.

Credentials

No environment variables, credentials, or config paths are requested. The skill does not ask for unrelated secrets. The main proportionality concern is operational (global installs) rather than credential overreach.

Persistence & Privilege

always is false and the skill does not request persistent system changes itself. Be aware: the skill's workflow encourages installing other skills (third‑party code) which can increase the agent's runtime privileges and attack surface if performed automatically.

Assessment

This skill is coherent: it tells the agent how to search for and install other skills using the 'npx skills' CLI. Before proceeding, remember that installing a discovered skill will fetch and execute third‑party code. Do not use global (-g) or unattended (-y) installs unless you trust the package owner and have reviewed the repository. Prefer asking the agent to show the install command and the skill's repo URL, manually inspect the source (or the skill manifest), and run installation commands yourself. The skill itself requests no credentials and contains no bundled code, but installing discovered skills is where you should apply caution.

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