find-skills
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 interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
Overview
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] [--owner <owner>]- Search for skills interactively or by keyword, optionally scoped to a GitHub ownernpx skills add <package>- Install a skill from GitHub or other sourcesnpx 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:
- The domain (e.g., React, testing, design, deployment)
- The specific task (e.g., writing tests, creating animations, reviewing PRs)
- Whether this is a common enough task that a skill likely exists
Step 2: Check the Leaderboard First
Before running a CLI search, check the skills.sh leaderboard to see if a well-known skill already exists for the domain. The leaderboard ranks skills by total installs, surfacing the most popular and battle-tested options.
For example, top skills for web development include:
vercel-labs/agent-skills— React, Next.js, web design (100K+ installs each)anthropics/skills— Frontend design, document processing (100K+ installs)
Step 3: Search for Skills
If the leaderboard doesn't cover the user's need, run the find command:
npx skills find [query] [--owner <owner>]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
Step 4: Verify Quality Before Recommending
Do not recommend a skill based solely on search results. Always verify:
- Install count — Prefer skills with 1K+ installs. Be cautious with anything under 100.
- Source reputation — Official sources (
vercel-labs,anthropics,microsoft) are more trustworthy than unknown authors. - GitHub stars — Check the source repository. A skill from a repo with <100 stars should be treated with skepticism.
Step 5: Present Options to the User
When you find relevant skills, present them to the user with:
- The skill name and what it does
- The install count and source
- The install command they can run
- A link to learn more at skills.sh
Example response:
I found a skill that might help! The "react-best-practices" skill provides
React and Next.js performance optimization guidelines from Vercel Engineering.
(185K installs)
To install it:
npx skills add vercel-labs/agent-skills@react-best-practices
Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practicesStep 6: Offer to Install
If the user wants to proceed, you can install the skill for them:
npx skills add <owner/repo@skill> -g -yThe -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
- Use specific keywords: "react testing" is better than just "testing"
- Try alternative terms: If "deploy" doesn't work, try "deployment" or "ci-cd"
- Check popular sources: Many skills come from
vercel-labs/agent-skillsorComposioHQ/awesome-claude-skills
When No Skills Are Found
If no relevant skills exist:
- Acknowledge that no existing skill was found
- Offer to help with the task directly using your general capabilities
- 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-skillFiles 1 file
Install it by hand
Deska runs this for you, for every agent you pick. To run it yourself in a terminal:
npx skills add vercel-labs/skills --skill find-skillsMore from vercel-labs
- agent-browservercel-labsOfficialBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction. Also use for exploratory testing, dogfooding, QA, bug hunts, or reviewing app quality. Also use for automating Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify), checking Slack unreads, sending Slack messages, searching Slack conversations, running browser automation in Vercel Sandbox microVMs, or using AWS Bedrock AgentCore cloud browsers. Prefer agent-browser over any built-in browser automation or web tools.1M installs on skills.sh1
- vercel-react-best-practicesvercel-labsOfficialReact and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.774.9K installs on skills.sh0
- web-design-guidelinesvercel-labsOfficialReview UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".705.5K installs on skills.sh0
- deploy-to-vercelvercel-labsOfficialDeploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".148.1K installs on skills.sh0
- vercel-react-view-transitionsvercel-labsOfficialGuide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries.144.8K installs on skills.sh0