Meta description: Vercel released an open CLI that lets you install reusable "skills" into any AI coding agent — Claude Code, Cursor, Copilot, and 40+ more. Here's why it matters and how to use it.
The Problem: Every Agent Starts From Zero
If you've used more than one AI coding agent — Claude Code, Cursor, Copilot, Windsurf, Codex — you've probably noticed something annoying: each one needs its own setup. Your carefully crafted instructions, tool configurations, and workflow rules don't transfer. Switch agents, start over.
And if you're a team? Multiply that pain. Every developer configures their own agent differently. Consistency is a pipe dream.
This is the problem Vercel's skills CLI was built to solve.
What Is Vercel Skills?
Vercel Labs released an open-source CLI (15.5k ⭐ and climbing) that does for AI agents what npm did for JavaScript packages:
npx skills add vercel-labs/agent-skills
One command. That's it. The CLI pulls skill definitions from any GitHub repo and installs them into your coding agent's config directory.
A "skill" is just a SKILL.md file with YAML frontmatter — a name, a description, and instructions the agent follows when that skill is relevant. Think of it as a reusable prompt template that any supported agent can understand.
Why This Actually Matters
1. Cross-Agent Portability
The CLI supports 43+ coding agents out of the box — Claude Code, Cursor, GitHub Copilot, OpenClaw, Gemini CLI, Windsurf, Codex, Cline, Amp, and dozens more. Each agent stores skills in a different directory (.claude/skills/, .cursor/skills/, .copilot/skills/, etc.). The CLI handles the mapping automatically.
Install once, use everywhere. Your team can standardize on specific skills regardless of which agent each developer prefers.
2. The Shared Specification
Skills follow the Agent Skills specification — a standardized format that any agent can adopt. This isn't a Vercel-only thing. It's an open ecosystem where:
- Anyone can create skills (just a SKILL.md in a repo)
- Anyone can publish skills (push to GitHub)
- Anyone can discover skills (via skills.sh)
The spec is deliberately simple: YAML frontmatter for metadata, Markdown for instructions. No build step, no compilation, no vendor lock-in.
3. Discovery and Distribution
The skills.sh directory already lists skills from Microsoft Azure (4.4M+ installs), marketing skill packs, Convex integration skills, and hundreds of community contributions. It's early, but the growth curve looks familiar — much like npm's early days.
How It Works In Practice
Installing Skills
# From a GitHub repo
npx skills add vercel-labs/agent-skills
# A specific skill from a repo
npx skills add vercel-labs/agent-skills --skill frontend-design
# Install globally (available across all projects)
npx skills add vercel-labs/agent-skills -g
# Target specific agents
npx skills add vercel-labs/agent-skills -a claude-code -a cursor
Managing Skills
# List what's installed
npx skills list
# Search for skills
npx skills find typescript
# Update to latest
npx skills update
# Create your own
npx skills init my-skill
Creating a Skill
A skill is just a directory with a SKILL.md:
---
name: deploy-to-vercel
description: Deploys the current project to Vercel with proper env vars and preview URLs
---
# Deploy to Vercel
## When to Use
When the user asks to deploy or preview the project.
## Steps
1. Check for vercel.json or next.config
2. Run `vercel --prod` for production or `vercel` for preview
3. Share the deployment URL with the user
Push it to GitHub, and anyone can install it with npx skills add your-username/your-repo.
The Bigger Picture: Agent Infrastructure Is Maturing
Vercel Skills isn't happening in isolation. It's part of a broader shift:
- MCP (Model Context Protocol) standardized how agents connect to external tools
- Agent Skills standardizes how agents acquire procedural knowledge
- Skills directories (like skills.sh) create a distribution layer
Together, these form the infrastructure layer that turns AI coding agents from "smart autocomplete" into "extensible development platforms."
The analogy to npm is intentional and instructive. npm didn't just make it easy to install packages — it created an ecosystem where small, composable modules could be shared, versioned, and combined. Agent skills are heading in the same direction.
What This Means for Developers
If you're a solo developer: Stop rewriting the same agent instructions across projects. Package them as skills and install them everywhere.
If you're on a team: Create org-level skill repos. Standardize how your agents handle code review, deployment, testing, and documentation. New team members get consistent agent behavior from day one.
If you're building agent-powered tools: Adopt the Agent Skills spec. Your users can leverage the entire ecosystem instead of starting from scratch.
If you're a startup founder: Pay attention to how agent infrastructure is standardizing. The skills ecosystem is where the "plugin marketplaces" for AI agents will emerge. Being early means shaping the standards.
Getting Started
# Browse available skills
npx skills find
# Install Vercel's official skill pack
npx skills add vercel-labs/agent-skills --all
# Create your first skill
npx skills init
The CLI is open source (MIT license), lightweight, and works with zero config. If you're already using an AI coding agent, there's no reason not to try it.
FAQ
Q: What's the difference between a skill and a system prompt? A: A system prompt is global and static — it applies to every interaction. A skill is modular, activatable based on context, and can be shared across agents and teams. Think of system prompts as your bash profile, and skills as npm packages you install as needed.
Q: Do skills work with all AI coding agents?
A: The CLI supports 43+ agents including Claude Code, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Codex, Cline, OpenClaw, and more. Basic skills (SKILL.md with instructions) work universally across all of them. Advanced features like allowed-tools and hooks are agent-specific.
Q: Can I create private skills for my team?
A: Yes. You can install skills from private GitHub repos (if you have access), local paths, or any Git URL. Use npx skills add ./my-team-skills for local-only skills, or point to your private repo.
Q: Is this only for coding agents? A: Right now, yes — the ecosystem is focused on coding agents. But the SKILL.md format is general-purpose. As AI agents expand beyond coding (research agents, data agents, creative agents), the same specification could apply. The infrastructure is agent-agnostic; the current adoption is dev-tool-centric.
About the Author
Arkin Julijanto is a startup founder and developer building Orbits Studio. He writes about AI tools, developer productivity, and the evolving agent ecosystem at arkin-dev.com.