Tools

Vercel has Open-Sourced a Universal Plug-and-Play 'Skills' CLI for AI Coding Agents like Claude Code, Codex, and Cursor

Vercel Labs has launched an open ecosystem and CLI tool for discovering, installing, and managing reusable instructions for AI coding agents.

A
AIDeveloper44 Team
July 7, 2026·4 min read
Vercel has Open-Sourced a Universal Plug-and-Play 'Skills' CLI for AI Coding Agents like Claude Code, Codex, and Cursor

The Vercel Agent Skills CLI acts as a centralized package manager for AI agent instructions.

TL;DR
  • Vercel Labs released an open agent skills ecosystem, functioning as a package manager for AI instructions.
  • The npx skills CLI installs Markdown-based instruction files directly into agent configuration directories.
  • Over 70 AI coding agents are supported, including Claude Code, Cursor, GitHub Copilot, and Windsurf.
  • The central registry, skills.sh, tracks over 900,000 installations from contributors like Microsoft and Anthropics.

Vercel Labs has introduced the Agent Skills ecosystem and its accompanying command-line interface, npx skills. This tooling provides a standardized method for developers to discover, install, and manage reusable instruction sets—termed "skills"—for various artificial intelligence coding agents. The ecosystem addresses a specific requirement in AI-assisted development: supplying agents with structured procedural knowledge, such as architectural guidelines, testing frameworks, or specific codebase practices, without requiring developers to manually rewrite prompts across different environments.

The Agent Skills Directory

The centralized registry for these capabilities is hosted at skills.sh. The directory tracks the usage of public skills and currently lists over 900,000 installations across the platform. Organizations such as Anthropics, Microsoft, and individual developers have contributed open-source repositories to this directory.

According to the platform's leaderboard, highly utilized skills include frontend design guidelines, codebase architecture improvement protocols, and infrastructure planners for environments like Microsoft Azure. Developers can search the directory via a web interface or query it directly from the terminal using the skills find command, which supports interactive searching and filtering by specific repository owners.

CLI Functionality and Installation Scopes

The primary interaction point for the ecosystem is the npx skills command-line interface. Functioning similarly to traditional package managers, developers use the add command to pull skills from remote sources. The CLI supports a wide variety of source formats, including GitHub shorthand (owner/repo), full GitHub or GitLab URLs, direct sub-directory paths within a repository, and local file paths.

Installation can be scoped in two ways:

  • Project Scope: The default behavior installs skills into a hidden directory within the current project (e.g., ./.cursor/skills/). This allows instructions to be committed to version control and shared among team members.
  • Global Scope: Using the -g flag installs skills to the user's home directory (e.g., ~/.cursor/skills/), making them accessible across all local projects.

By default, the CLI utilizes symlinks to connect the agent directories to a canonical copy of the downloaded skill. This method ensures a single source of truth and simplifies version updates. If a local system does not support symlinks, a --copy flag is available to create independent duplicates of the files.

Diagram: Architecture of the Vercel Skills CLI deploying instructions to agent configurations.

Skill Architecture and Lifecycle Management

A skill is technically a directory containing a SKILL.md file. This Markdown file utilizes YAML frontmatter to define essential metadata, specifically a name and a description. Additional metadata fields, such as internal: true, can be added to hide work-in-progress or proprietary tools from standard discovery outputs. The body of the Markdown file contains the exact instructions the agent will parse.

During installation, the CLI scans the target repository using specific discovery heuristics. It looks in the root directory, standard skills/ folders, and curated paths like skills/.system/. Developers can use the --full-depth flag to force the CLI to scan beyond these standard container directories.

For lifecycle management, the ecosystem provides commands to modify existing local setups. npx skills update checks the remote source for changes and syncs the local copies. npx skills remove uninstalls skills interactively or via CLI flags. For users interested in developing their own instructions, npx skills init [name] scaffolds a new SKILL.md template locally.

Additionally, the use command allows a developer to invoke a skill without persistent installation. It reads the remote or local source and outputs the generated prompt to standard output, which can then be piped directly into interactive agents like claude-code.

Supported Agent Environments

The CLI is designed for broad compatibility, currently supporting over 70 distinct AI coding agents. The supported roster includes Claude Code, Cursor, Codex, GitHub Copilot, Windsurf, AiderDesk, OpenHands, and numerous others.

The installation process auto-detects which of these agents are present on the host system. If no agents are explicitly flagged in the command, the CLI prompts the developer to select their target environments. For more complex setups, such as custom agents built via the Kiro CLI, developers can map the skill paths manually within their agent's JSON configuration files.

By providing a unified packaging system, Vercel Labs' Skills ecosystem aims to standardizes how context and procedural instructions are distributed across the fragmented landscape of AI-assisted development tools.


References & Sources

  1. The Agent Skills Directory
  2. GitHub - vercel-labs/skills: The open agent skills tool

Enjoyed this?

Get more posts like this delivered to your inbox.