t

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 skills) but they explicitly instruct installing arbitrary third‑party packages (via npx) and even recommend skipping prompts and installing globally — behavior that could lead to unwanted code being installed if the agent acts autonomously.

Purpose & Capability

The name/description and the runtime instructions consistently describe a 'find and install skills' helper that uses the Skills CLI (npx skills). There are no unrelated required env vars, binaries, or config paths.

Instruction Scope

The SKILL.md directs the agent to run npx skills find/add commands and to install skills with 'npx skills add <owner/repo@skill> -g -y'. That instructs fetching and executing third‑party code and explicitly recommends skipping user confirmation (-y) and installing globally (-g). While these steps are functionally required for installing skills, recommending bypassing prompts and global installs broadens the scope and risk of actions the agent will take.

Install Mechanism

This is an instruction-only skill (no install spec). It relies on npx to fetch packages from public registries/GitHub, which is a common but moderate-risk mechanism because it executes remote code. The SKILL.md points to skills.sh (a central index) — that is expected and preferable to arbitrary personal URLs.

Credentials

The skill requests no environment variables, credentials, or config paths. However, the recommended global installs (-g) will modify the user's environment, which is an expected but impactful side effect of the skill's purpose.

Persistence & Privilege

The skill is not marked 'always: true', but platform defaults allow autonomous invocation (disable-model-invocation: false). Combined with explicit instructions to run 'npx skills add ... -g -y', an autonomously invoked agent could install arbitrary third‑party code without additional user confirmation. That increases blast radius and warrants caution.

What to consider before installing

This skill is coherent — it helps find and install other skills — but it instructs the agent to fetch and install third‑party code (via npx) and even recommends skipping confirmations and installing globally. Before enabling or letting the agent run this skill autonomously: 1) Prefer manual review of search results and the target skill's GitHub page on skills.sh before installing. 2) Avoid using the '-y' flag or global installs; require explicit user confirmation for any 'npx skills add' operation. 3) If you must allow automated installs, restrict the agent's permission to run shell commands or require a second explicit user approval. 4) Verify the publisher and repository of any skill you install to reduce supply‑chain risk.

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