Find Skills Pro

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 purpose align (it helps find and install skills), but it encourages installing arbitrary packages via npx (including using global -g and -y flags) and there's a small metadata mismatch — these are proportionate to the task but carry non-trivial risk and deserve caution.

Purpose & Capability

The name/description match the instructions: the skill is an instruction-only helper that uses the Skills CLI (npx skills) to find and install other skills. One minor incoherence: the _meta.json ownerId differs from the registry ownerId in the provided metadata, which could indicate packaging or provenance confusion.

Instruction Scope

The SKILL.md tells the agent to run npx commands to search and install arbitrary skill packages. That stays within the stated purpose (finding/installing skills) but the examples recommend installing with '-g -y' (global + skip prompts). Skipping prompts and installing globally increases the chance the agent could install code without clear user consent or create system-wide side effects.

Install Mechanism

The skill is instruction-only (no install spec), but it instructs use of npx to fetch packages from npm/GitHub. Using npx to pull and run packages is a common pattern for this ecosystem, but it is inherently higher-risk than purely local operations because it executes remote code. The SKILL.md lacks guidance to vet packages before installing.

Credentials

The skill does not request environment variables, credentials, or config paths. No secret access is required by the skill itself.

Persistence & Privilege

The skill itself requests no persistent privileges (always:false). However, its recommended actions (global installs of third-party skills) could install persistent code into the user's environment; consider this when giving permission to proceed.

What to consider before installing

This skill is coherent for finding agent skills, but be careful before letting it install packages for you. npx installs run code fetched from remote sources — verify the package owner and repository before installing. Avoid using '-g -y' unless you explicitly trust the package (global installs and skipping confirmations increase risk). If you want to proceed safely: 1) ask the assistant to show the exact package URL and README first, 2) inspect the repo before installing, 3) prefer local or sandboxed installs, and 4) do not grant broad automated install permission. Also note the small ownerId mismatch in the metadata — if provenance matters, ask the publisher for clarification.

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