Find Skills Tianjin

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, requirements, and behavior are coherent with its stated purpose (finding and installing other skills); the main risks are the usual ones when installing third‑party packages (network fetches and executing remote code).

Purpose & Capability

Name/description match the instructions: the SKILL.md guides the agent to search for and install skills using the 'skills' CLI (invoked via 'npx skills') and links to skills.sh. There are no unrelated env vars, binaries, or config paths requested.

Instruction Scope

Instructions stay on‑task (searching, reporting results, offering to install). They do not request reading files or unrelated credentials. However, the guide recommends using 'npx skills add' (and shows 'npx skills add <...> -g -y'), which installs/executes third‑party packages and the '-y' flag bypasses confirmation prompts — this can cause installations to proceed without explicit interactive consent. The agent should confirm with the user before executing install commands.

Install Mechanism

No install spec is bundled with the skill (instruction‑only). Runtime behavior relies on npx, which will fetch and run code from npm/git repositories. This is expected for a skill manager but is a moderate risk because it executes remote code from external package sources.

Credentials

The skill declares no required environment variables, credentials, or config paths. The SKILL.md does not reference secret/env access. Requested privileges are proportional to the stated purpose.

Persistence & Privilege

The skill itself does not request permanent inclusion or special agent privileges (always: false). The instructions suggest global installs ('-g'), which create persistent packages on the user's system if executed — that is a user action and not intrinsic to the skill, but users should be aware installing other skills can persist code on disk.

Assessment

This skill is coherent: it helps find and install other skills via the 'skills' CLI. The primary risk is installing or running arbitrary third‑party packages: 'npx' will fetch and run code from npm/GitHub, and the example '-y' flag skips confirmations. Before installing anything, review the linked skill repository (skills.sh link), confirm you trust the author, avoid using '-g -y' without explicit consent, and consider running installs in a controlled environment or sandbox. If you want the agent to install something, instruct it to ask you first and show the install command and source 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