fff

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 purpose (finding and installing other skills) matches its instructions, but there are metadata inconsistencies and the instructions encourage using npx to fetch and globally install arbitrary packages with a -y/skip-confirm flag — a combination that can install and execute unreviewed code without clear safeguards.

Purpose & Capability

The SKILL.md describes a find/install helper and the suggested commands (npx skills find/add) are consistent with that purpose. However, the registry metadata shown to you (owner, slug, version) does not match the _meta.json embedded in the package (different ownerId, slug, version). That discrepancy could indicate a copy/paste, republishing under a different identity, or packaging mistake and warrants verification before trust.

Instruction Scope

Instructions are narrowly scoped to searching and installing skills using the Skills CLI (npx skills). They do not request unrelated files or environment variables. Concern: the README explicitly recommends running installs with -g and -y (global + skip confirmations), which encourages non-interactive global installation of third-party code — this expands the impact of any mistaken or malicious install.

Install Mechanism

No install spec in the package itself (instruction-only). The runtime instructions rely on 'npx skills' which will download and run packages from npm/GitHub. That is an expected mechanism for a skills-discovery helper, but it inherently allows arbitrary remote code execution when used. Users should treat 'npx skills add' as privileged and review sources before running.

Credentials

The skill does not request environment variables, credentials, or config paths. That is proportionate to its described role. Still, the recommended global installations affect user environment and should be treated cautiously.

Persistence & Privilege

always:false (good), but model invocation is allowed (default). Combined with instructions that recommend non-interactive, global installs, an agent that invokes this skill autonomously could install and execute other skills without explicit human confirmation. If you allow autonomous installs, this increases blast radius.

What to consider before installing

This skill is coherent for finding skills, but take precautions before using it: 1) Verify the source/author — the embedded _meta.json owner/slug/version differ from the registry metadata shown; confirm you trust the publisher. 2) Never run 'npx skills add ... -g -y' as-is — avoid global installs and skip-confirm flags; require that installs be confirmed and inspected first. 3) Prefer installing locally or in a sandbox, and inspect the package/repo before running. 4) If you allow the agent to act autonomously, disable non-interactive installs or require explicit user confirmation for every install. 5) If in doubt, ask the skill to show the exact repo URL and a link to its source on GitHub/skills.sh and review the code manually before proceeding.

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