Find Skills 0

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) and it does not request credentials or unusual system access, but it instructs the agent to run npx to fetch and install third‑party packages (including a global, non-interactive install flag) which has inherent risk and deserves user oversight.

Purpose & Capability

Name, description, and runtime instructions are aligned: the skill is a helper that searches for skills and suggests using the Skills CLI (npx skills) and skills.sh. It does not ask for unrelated credentials, binaries, or config paths.

Instruction Scope

Instructions stay within the skill-discovery/install domain (use 'npx skills find' and 'npx skills add'). However, the guidance recommends running 'npx skills add <pkg> -g -y' which performs a global, non-interactive install of third-party packages — this can install and execute arbitrary code from npm/GitHub without further confirmation. The SKILL.md does not instruct the agent to read unrelated files or environment variables.

Install Mechanism

The skill is instruction-only (no install spec). It relies on npx/npm for fetching packages at install time. That is expected for a package-manager-driven workflow, but npx/npm downloads and may execute remote code — a moderate risk inherent to the mechanism (not a contradiction of stated purpose).

Credentials

No environment variables, credentials, or config paths are requested. The lack of extra secrets or unrelated env access is appropriate for the described functionality.

Persistence & Privilege

The skill does not set always:true and does not request persistent system privileges itself. Still, its recommended install command (-g -y) affects the user's environment by installing packages globally and skipping confirmations. Also note the platform default allows autonomous invocation; while that alone is not a fault, autonomous execution combined with auto-install instructions increases the need for user oversight.

Assessment

This skill is coherent with its purpose: it helps find and install other skills. Before letting the agent run the suggested install commands, consider the following: (1) npx installs packages from npm/GitHub and may execute code during install — only install packages from sources you trust; (2) the recommended '-g -y' flags perform global, non-interactive installs (no further confirmation) — avoid automatic installs unless you authorize them; (3) review the target skill's repository (owner, README, recent commits) on skills.sh or GitHub before installing; (4) if you are uncomfortable with the agent running shell commands autonomously, disable autonomous skill invocation or require explicit user confirmation for installations. If you want a stricter assessment, provide an example package name the skill would install so I can examine that package/repo specifically.

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