Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
39 changes: 24 additions & 15 deletions .agents/skills/find-skills/SKILL.md
Original file line number Diff line number Diff line change
Expand Up @@ -41,9 +41,17 @@ When a user asks for help with something, identify:
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
### Step 2: Check the Leaderboard First

Run the find command with a relevant query:
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.

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:

```bash
npx skills find [query]
Expand All @@ -55,36 +63,37 @@ For example:
- 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:
### Step 4: Verify Quality Before Recommending

```
Install with npx skills add <owner/repo@skill>
**Do not recommend a skill based solely on search results.** Always verify:

vercel-labs/agent-skills@vercel-react-best-practices
└ https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
```
1. **Install count** — Prefer skills with 1K+ installs. Be cautious with anything under 100.
2. **Source reputation** — Official sources (`vercel-labs`, `anthropics`, `microsoft`) are more trustworthy than unknown authors.
3. **GitHub stars** — Check the source repository. A skill from a repo with <100 stars should be treated with skepticism.

### Step 3: Present Options to the User
### Step 5: 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
2. The install count and source
3. The install command they can run
4. A link to learn more at skills.sh

Example response:

```
I found a skill that might help! The "vercel-react-best-practices" skill provides
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@vercel-react-best-practices
npx skills add vercel-labs/agent-skills@react-best-practices

Learn more: https://skills.sh/vercel-labs/agent-skills/vercel-react-best-practices
Learn more: https://skills.sh/vercel-labs/agent-skills/react-best-practices
```

### Step 4: Offer to Install
### Step 6: Offer to Install

If the user wants to proceed, you can install the skill for them:

Expand Down
8 changes: 0 additions & 8 deletions .agents/skills/grill-me/SKILL.md

This file was deleted.

7 changes: 1 addition & 6 deletions skills-lock.json
Original file line number Diff line number Diff line change
Expand Up @@ -9,12 +9,7 @@
"find-skills": {
"source": "vercel-labs/skills",
"sourceType": "github",
"computedHash": "6412eb4eb3b91595ebab937f0c69501240e7ba761b3d82510b5cf506ec5c7adc"
},
"grill-me": {
"source": "mattpocock/skills",
"sourceType": "github",
"computedHash": "e02446c0912decc73472ab3392af040fac223fb93b46fd101bce27686d717136"
"computedHash": "9e1c8b3103f92fa8092568a44fe64858de7c5c9dc65ce4bea8f168080e889cfd"
},
"resolve-reviews": {
"source": "pbakaus/agent-reviews",
Expand Down
Loading