Setting the issue. One moment.
Contents
Repo No. 80Vercel Labs · Updated 6 November 2026 · In print
Skills Docs · No. 80
4 skills2,848 words
Inside this issue
1 — Install
npx skills add vercel-labs/skillsMIT39k stars2,848 wordsUpdated 6 November 2026
2 — Skills
4 skills · 14 minutes- PR LabelingClassify a skills CLI pull request from its description and patch, while respecting existing labels.1 min
- TriageIdentify focused, evidence-backed skills CLI bug fixes worth quuu’s attention.5 min
- TriageIdentify focused, evidence-backed skills CLI bug fixes worth quuu’s attention.5 min
- Find SkillsHelps users discover and install agent skills when they ask questions like “how do I do X”, “find a skill for…3 min
Skills Docs · Repo No. 80Whole repo as markdown
Provenance
- Owner
- vercel-labs · Organization
- Licence
- MIT
- Last updated
- Published from
- github.com/
vercel-labs/ skills
| Week | Installs |
|---|---|
| Week 1 | 105,144 |
| Week 2 | 103,601 |
| Week 3 | 107,199 |
| Week 4 | 110,524 |
| Week 5 | 121,189 |
| Week 6 | 121,665 |
| Week 7 | 115,285 |
| Week 8 | 110,096 |
Typeset in this issue’s own colours, resolved from the awesome-design-md registry.
Front matter
From the READMEThe CLI for the open agent skills ecosystem.
Agent skills are reusable instructions that teach coding agents how to perform tasks, from reviewing code to working with a library. Discover skills at skills.sh (opens in a new tab).
Supports OpenCode, Claude Code, Codex, Cursor, and 75 more (opens in a new tab).
Install a Skill
Requires Node.js 22.20 or later. Run this from your project:
npx skills add vercel-labs/agent-skillsChoose the skills and coding agents to install to. Skills are installed to the current
project by default; add -g to make them available across projects.
# Choose one skill and agent
npx skills add vercel-labs/agent-skills --skill web-design-guidelines -a claude-code
# Browse available skills
npx skills findSee the installation reference (opens in a new tab) for source formats, private repositories, and all options.
Other Commands
| Command | Description |
|---|---|
npx skills find [query] | Search for skills |
npx skills list | List installed skills |
npx skills use <source>@<skill> | Use one skill without installing |
npx skills check | Check for available updates |
npx skills update [skills...] | Update installed skills |
npx skills remove [skills...] | Remove installed skills |
npx skills init [name] | Create a skill template |
Read the CLI reference (opens in a new tab) or run npx skills --help for examples and options. Experimental commands are listed below.
Use a Skill Without Installing
Generate a prompt for a skill, or launch a supported coding agent with it:
npx skills use vercel-labs/agent-skills@web-design-guidelines --agent claude-codeOmit --agent to print the prompt instead. See skills use (opens in a new tab).
Experimental Features
| Command | Description |
|---|---|
npx skills experimental_sync | Sync skills shipped by npm dependencies into your project |
npx skills experimental_install | Restore project skills recorded in skills-lock.json |
Some npm packages bundle instructions for your agent alongside their code. Sync links them into your project so they update with the dependency, and also installs skill packs declared in package.json:
npm install -D skills agent-browser
npx skills experimental_sync -ySee the experimental commands reference (opens in a new tab) for options, the skills field, and the RFC (opens in a new tab) behind it.
Supported Agents
The CLI detects installed agents and lets you choose where skills are installed. See all supported agents, installation paths, and compatibility (opens in a new tab).
Creating Skills
npx skills init my-skillEdit the generated SKILL.md with instructions for your agent.
See creating and sharing skills (opens in a new tab) for the format and discovery rules.
Documentation
- CLI reference (opens in a new tab): installation, command examples, and experimental features
- Supported agents (opens in a new tab): agent names, skill directories, and compatibility
- Creating skills (opens in a new tab): frontmatter, repository layouts, and plugins
- Troubleshooting and configuration (opens in a new tab): common problems, environment variables, and telemetry
- Programmatic API (opens in a new tab): install and manage skills from your own tools with
import { installSkills } from 'skills'
Telemetry
The CLI collects anonymous usage data. Set DISABLE_TELEMETRY=1 or DO_NOT_TRACK=1
to disable telemetry and security-audit requests.
See what is collected (opens in a new tab).
Related Links
- Skills Directory (opens in a new tab)
- Agent Skills Specification (opens in a new tab)
- Vercel Agent Skills (opens in a new tab)
License
This project is licensed under the MIT License (opens in a new tab).
Colophon
How this issue was made- Source
- github.com/vercel-labs/skills, branch
main, last pushed 6 November 2026. - Licence
- MIT — the text of every skill is reproduced unmodified, frontmatter included, under the upstream licence.
- Discovery
- 4 skills found by walking the repository tree for
SKILL.md, not by matching a directory convention. 4 distinct layouts observed:.automations/pr-labeling/skills/*/SKILL.md,.automations/triage/skills/*/SKILL.md,.vc/automations/workflows/triage/skills/*/SKILL.md,skills/*/SKILL.md. - Duplicates collapsed
- 1 mirror copy folded into their canonical skill — republished for Vc. Copies match on content hash and on position once a leading per-agent prefix is stripped, because the same skill is routinely shipped under a dozen agent directories with a dozen different hashes.
- Issue colours
- Resolved from the awesome-design-md registry — hue 2°, chroma 0.190. Two accent tones are generated per issue and each is proven against its own ground before it ships: a single accent that passes AA on both light and dark paper is arithmetically impossible.
- Heading repairs
- 1 repair applied to the front matter so the document has one
h1and no skipped levels:- Removed “skills”, a leading h1 that duplicated the skill title.
- Spec compliance
- Every skill satisfies the Agent Skills specification’s frontmatter rules.
- Images
- Images inside a skill come from the upstream repository. Where the author gave no alternative text we mark the image decorative rather than inventing a description — a plausible caption we made up is worse than none for the reader who depends on it.
- Signal
- Install counts come from skills.sh. They measure downloads, not quality, and an unranked repository is not an unread one.
- Agent surfaces
- The whole issue is available as one markdown document at
/vercel-labs/skills.md, and each skill at its own.mdURL. - Publication
- Set by Skills Docs from the source repository. Body text is Literata at the reader’s chosen size and measure; code is Geist Mono. Nothing on this page was written by us except this paragraph.