find-skills

Name: find-skills
Author: vercel-labs

2.6Minstalls2.3kforks

How to install find-skills?

vercel-labs/skills/find-skills

$npx -y skills add vercel-labs/skills --skill find-skills

Installs into the current project.

Summary

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 a

Files · 1

View on GitHub

SKILL.md

1	# Find Skills
2
3	This skill helps you discover and install skills from the open agent skills ecosystem.
4
5	## When to Use This Skill
6
7	Use this skill when the user:
8
9	- Asks "how do I do X" where X might be a common task with an existing skill
10	- Says "find a skill for X" or "is there a skill for X"
11	- Asks "can you do X" where X is a specialized capability
12	- Expresses interest in extending agent capabilities
13	- Wants to search for tools, templates, or workflows
14	- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
15
16	## What is the Skills CLI?
17
18	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.
19
20	Key commands:
21
22	- `npx skills find [query] [--owner <owner>]` - Search for skills interactively or by keyword, optionally scoped to a GitHub owner
23	- `npx skills add <package>` - Install a skill from GitHub or other sources
24	- `npx skills update` - Update all installed skills
25
26	Browse skills at: https://skills.sh/
27
28	## How to Help Users Find Skills
29
30	### Step 1: Understand What They Need
31
32	When a user asks for help with something, identify:
33
34	1. The domain (e.g., React, testing, design, deployment)
35	2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
36	3. Whether this is a common enough task that a skill likely exists
37
38	### Step 2: Check the Leaderboard First
39
40	Before running a CLI search, check the [skills.sh leaderboard](https://skills.sh/) 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.
41
42	For example, top skills for web development include:
43	- `vercel-labs/agent-skills` — React, Next.js, web design (100K+ installs each)
44	- `anthropics/skills` — Frontend design, document processing (100K+ installs)
45
46	### Step 3: Search for Skills
47
48	If the leaderboard doesn't cover the user's need, run the find command:
49
50	```bash
51	npx skills find [query] [--owner <owner>]
52	```
53
54	For example:
55
56	- User asks "how do I make my React app faster?" → `npx skills find react performance`
57	- User asks "can you help me with PR reviews?" → `npx skills find pr review`
58	- User asks "I need to create a changelog" → `npx skills find changelog`
59
60	### Step 4: Verify Quality Before Recommending
61
62	Do not recommend a skill based solely on search results. Always verify:
63
64	1. Install count — Prefer skills with 1K+ installs. Be cautious with anything under 100.
65	2. Source reputation — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors.
66	3. GitHub stars — Check the source repository. A skill from a repo with <100 stars should be treated with skepticism.
67
68	### Step 5: Present Options to the User
69
70	When you find relevant skills, present them to the user with:
71
72	1. The skill name and what it does
73	2. The install count and source
74	3. The install command they can run
75	4. A link to learn more at skills.sh
76
77	Example response:
78
79	```
80	I found a skill that might help! The "react-best-practices" skill provides
81	React and Next.js performance optimization guidelines from Vercel Engineering.
82	(185K installs)
83
84	To install it:
85	npx skills add vercel-labs/agent-skills@react-best-practices
86
87	Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices
88	```
89
90	### Step 6: Offer to Install
91
92	If the user wants to proceed, you can install the skill for them:
93
94	```bash
95	npx skills add <owner/repo@skill> -g -y
96	```
97
98	The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
99
100	## Common Skill Categories
101
102	When searching, consider these common categories:
103
104	\| Category \| Example Queries \|
105	\| --------------- \| ---------------------------------------- \|
106	\| Web Development \| react, nextjs, typescript, css, tailwind \|
107	\| Testing \| testing, jest, playwright, e2e \|
108	\| DevOps \| deploy, docker, kubernetes, ci-cd \|
109	\| Documentation \| docs, readme, changelog, api-docs \|
110	\| Code Quality \| review, lint, refactor, best-practices \|
111	\| Design \| ui, ux, design-system, accessibility \|
112	\| Productivity \| workflow, automation, git \|
113
114	## Tips for Effective Searches
115
116	1. Use specific keywords: "react testing" is better than just "testing"
117	2. Try alternative terms: If "deploy" doesn't work, try "deployment" or "ci-cd"
118	3. Check popular sources: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
119
120	## When No Skills Are Found
121
122	If no relevant skills exist

People who liked this also viewed

6 picks

Type

find-skills

2.6Minstalls2.3kforks

View on GitHub

How to install find-skills?

vercel-labs/skills/find-skills

$npx -y skills add vercel-labs/skills --skill find-skills

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Find Skills
2
3	This skill helps you discover and install skills from the open agent skills ecosystem.
4
5	## When to Use This Skill
6
7	Use this skill when the user:
8
9	- Asks "how do I do X" where X might be a common task with an existing skill
10	- Says "find a skill for X" or "is there a skill for X"
11	- Asks "can you do X" where X is a specialized capability
12	- Expresses interest in extending agent capabilities
13	- Wants to search for tools, templates, or workflows
14	- Mentions they wish they had help with a specific domain (design, testing, deployment, etc.)
15
16	## What is the Skills CLI?
17
18	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.
19
20	Key commands:
21
22	- `npx skills find [query] [--owner <owner>]` - Search for skills interactively or by keyword, optionally scoped to a GitHub owner
23	- `npx skills add <package>` - Install a skill from GitHub or other sources
24	- `npx skills update` - Update all installed skills
25
26	Browse skills at: https://skills.sh/
27
28	## How to Help Users Find Skills
29
30	### Step 1: Understand What They Need
31
32	When a user asks for help with something, identify:
33
34	1. The domain (e.g., React, testing, design, deployment)
35	2. The specific task (e.g., writing tests, creating animations, reviewing PRs)
36	3. Whether this is a common enough task that a skill likely exists
37
38	### Step 2: Check the Leaderboard First
39
40	Before running a CLI search, check the [skills.sh leaderboard](https://skills.sh/) 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.
41
42	For example, top skills for web development include:
43	- `vercel-labs/agent-skills` — React, Next.js, web design (100K+ installs each)
44	- `anthropics/skills` — Frontend design, document processing (100K+ installs)
45
46	### Step 3: Search for Skills
47
48	If the leaderboard doesn't cover the user's need, run the find command:
49
50	```bash
51	npx skills find [query] [--owner <owner>]
52	```
53
54	For example:
55
56	- User asks "how do I make my React app faster?" → `npx skills find react performance`
57	- User asks "can you help me with PR reviews?" → `npx skills find pr review`
58	- User asks "I need to create a changelog" → `npx skills find changelog`
59
60	### Step 4: Verify Quality Before Recommending
61
62	Do not recommend a skill based solely on search results. Always verify:
63
64	1. Install count — Prefer skills with 1K+ installs. Be cautious with anything under 100.
65	2. Source reputation — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors.
66	3. GitHub stars — Check the source repository. A skill from a repo with <100 stars should be treated with skepticism.
67
68	### Step 5: Present Options to the User
69
70	When you find relevant skills, present them to the user with:
71
72	1. The skill name and what it does
73	2. The install count and source
74	3. The install command they can run
75	4. A link to learn more at skills.sh
76
77	Example response:
78
79	```
80	I found a skill that might help! The "react-best-practices" skill provides
81	React and Next.js performance optimization guidelines from Vercel Engineering.
82	(185K installs)
83
84	To install it:
85	npx skills add vercel-labs/agent-skills@react-best-practices
86
87	Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices
88	```
89
90	### Step 6: Offer to Install
91
92	If the user wants to proceed, you can install the skill for them:
93
94	```bash
95	npx skills add <owner/repo@skill> -g -y
96	```
97
98	The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.
99
100	## Common Skill Categories
101
102	When searching, consider these common categories:
103
104	\| Category \| Example Queries \|
105	\| --------------- \| ---------------------------------------- \|
106	\| Web Development \| react, nextjs, typescript, css, tailwind \|
107	\| Testing \| testing, jest, playwright, e2e \|
108	\| DevOps \| deploy, docker, kubernetes, ci-cd \|
109	\| Documentation \| docs, readme, changelog, api-docs \|
110	\| Code Quality \| review, lint, refactor, best-practices \|
111	\| Design \| ui, ux, design-system, accessibility \|
112	\| Productivity \| workflow, automation, git \|
113
114	## Tips for Effective Searches
115
116	1. Use specific keywords: "react testing" is better than just "testing"
117	2. Try alternative terms: If "deploy" doesn't work, try "deployment" or "ci-cd"
118	3. Check popular sources: Many skills come from `vercel-labs/agent-skills` or `ComposioHQ/awesome-claude-skills`
119
120	## When No Skills Are Found
121
122	If no relevant skills exist

People who liked this also viewed

6 picks

Type