Vercel opens Skills API with 600,000 skills for agents and platforms

• Vercel made the skills.sh API GA, and vercel_dev's launch post vercel_dev's launch post says it exposes more than 600,000 skills from the open source ecosystem.
• Guillermo Rauch's framing rauchg's registry analogy pitched it as an npm-like registry for agent capabilities, not just a hosted directory.
• The official changelog says the API uses short-lived Vercel OIDC tokens and enforces 600 requests per minute per team and project, which is a notably platform-shaped auth model for a public skills registry vercel_dev's launch post.
• The launch sits on top of a broader open agent skills ecosystem where skills install with a single command and already target agents like Claude Code, Codex, Cursor, and OpenCode, according to the skills CLI repo and Andrew Qu's directory link rauchg linking skills.sh.

You can read the official changelog, browse the live skills.sh directory, and inspect the CLI repository. The interesting bit is how little of this is framed as a Vercel-only feature: the directory advertises a cross-agent ecosystem, the repo lists support for Claude Code, Codex, Cursor, and dozens more, and Mastra's registry example suggests third-party agent tooling was already wiring skills.sh in before the GA post Mastra's registry example.

The new API exposes three core actions in the launch materials: search for skills, fetch detailed data for a specific skill, and inspect a skill's security audit. Vercel's changelog is short, but it makes the service sound like an indexable capability layer for agents and platforms, not a consumer UI feature.

Rauch described it as "the npm registry for agent capabilities and extensibility." That is the cleanest mental model in the source set, especially because the public directory already presents skills as installable, reusable units rather than one-off prompts.

The most concrete implementation detail is auth. The official announcement says requests use a short-lived Vercel OIDC token scoped to a team and project, rotated automatically, with verification on every call.

That same post sets the rate limit at 600 requests per minute per team and project. For teams already running agents on Vercel, that removes the usual API-key plumbing and makes the registry look more like infrastructure than marketplace chrome.

The launch landed into an ecosystem that was already being treated as a registry source. Mastra's post shows skill registries configured against skills.sh so teammates can browse and add skills to their agents.

That lines up with the skills CLI repo, which describes itself as "the CLI for the open agent skills ecosystem" and says it supports OpenCode, Claude Code, Codex, Cursor, and 67 more agents. The registry story here is bigger than one API endpoint, it is a packaging and distribution layer that other agent frameworks can point at.

The public skills.sh directory adds two details missing from the launch tweet. It markets skills as reusable procedural knowledge, installable with a single command, and it exposes a leaderboard instead of just a flat catalog.

A repost from cramforce cramforce reposting Andrew Qu also suggests Andrew Qu had quietly exposed the API docs with "email me" instructions before the formal GA announcement. That makes this look less like a cold launch and more like a soft-opened service that already had inbound demand before Vercel put its name on it.