find skills

AI Community

Skill notes

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

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 owner npx skills add <package> - Install a skill from GitHub or other sources

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: 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

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
AI
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
88 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@vercel-labs · no license declared
Token usage
Lean
Setup complexity
Guided setup
External API key
Not required
Operating systems
Docker
Runtime requirements
Docker
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

01
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

02
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)

03
Step 3: Search for Skills

If the leaderboard doesn't cover the user's need, run the find command: 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`

04
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.

05
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

06
Step 6: Offer to Install

If the user wants to proceed, you can install the skill for them: The `-g` flag installs globally (user-level) and `-y` skips confirmation prompts.

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.