Rank #5 of 5 in Agent Skills & Extensions
Access
Showcase


Products
Vercel, product by product →Vercel ships more than one product — each judged line competes in its own arena on the same stories as everyone else.
| Line | Arena | Rank | PA Score | Agent-ready |
|---|---|---|---|---|
| Vercel | Edge & App Platforms | #4/6 | 25/100 | 44/100 |
| v0 | Vibe-Coding App Builders | #4/6 | 21/100 | 24/100 |
| Vercel Sandbox | Agent Sandboxes & Code Execution | #5/8 | 25/100 | 41/100 |
| Vercel AI Gateway | Model Gateways & Routers | #3/7 | 29/100 | 41/100 |
| skills.shthis page | Agent Skills & Extensions | #5/5 | 18/100 | 29/100 |
Try itExperimental
See what an agent can do with skills.sh before you ever sign up. Pick a story: recorded sessions replay real probe-harness transcripts; sandboxed self-drive sessions are designed and gated (docs/TRY-IT.md).
$npx -y skills --versionrecorded session — replayed, not liveVerified integrations
Connections to other tracked products — hover a chip for the verbatim evidence quote behind it.
By theme — the product's score on each story themeBy theme
Agent workflows — stories about agent workflows in this arenaAgent workflowsevidence →
Stories about agent workflows in this arena
Agenticness — how well agents can access and operate the productAgenticnessevidence →
How well agents can access and operate the product
Automation depth — how much of the product can run unattendedAutomation depthevidence →
How much of the product can run unattended
Cross agent portability — stories about cross agent portability in this arenaCross agent portabilityevidence →
Stories about cross agent portability in this arena
Discovery distribution — stories about discovery distribution in this arenaDiscovery distributionevidence →
Stories about discovery distribution in this arena
Docs onboarding — stories about docs onboarding in this arenaDocs onboardingevidence →
Stories about docs onboarding in this arena
Install experience — stories about install experience in this arenaInstall experienceevidence →
Stories about install experience in this arena
Openness — open source, data portability, and self-hosting storiesOpennessevidence →
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy postureevidence →
Data-handling and privacy stories
Safety review — stories about safety review in this arenaSafety reviewevidence →
Stories about safety review in this arena
Skill authoring — stories about skill authoring in this arenaSkill authoringevidence →
Stories about skill authoring in this arena
Testing quality — stories about testing quality in this arenaTesting qualityevidence →
Stories about testing quality in this arena
Versioning updates — stories about versioning updates in this arenaVersioning updatesevidence →
Stories about versioning updates in this arena
Story verdicts — every judged story with its evidenceStory verdicts
What’s free: 4 free · 0 paid · 0 enterprise · 24 not stated in evidence
Follow the green: where the map greys out is where skills.sh stops today. ✓ full · ~ partial · ! disputed · — none · n/a not applicable.
Agent workflows — stories about agent workflows in this arenaAgent workflows
Stories about agent workflows in this arena
Agenticness — how well agents can access and operate the productAgenticness
How well agents can access and operate the product
API surface
Drive the product through a documented public API
~5/10
unlocks → Official SDKs · MCP server · Machine-readable spec · Versioning policy · API sandbox
Subscribe to events via webhooks
n/an/a
Build against official SDKs
—–
Issue scoped/least-privilege API credentials for an agent
n/an/a
Connect an agent via an official MCP server
—0/10
Download a machine-readable API spec (OpenAPI or equivalent)
—0/10
Rely on versioned APIs with a documented deprecation policy
—0/10
Test against a sandbox environment without touching production data
—–
Explore an interactive API reference with runnable examples
n/an/a
Docs for agents
Point an agent at llms.txt or agent-oriented docs
~5/10
Agentic features
Delegate tasks to a built-in AI assistant inside the product
—–
Operate the product with natural-language commands
—0/10
Plug MCP servers into this product so it can use their tools
—–
Get AI-generated insights and suggestions from my data inside the product
—–
Set up automations that run autonomously in the background
—–
Automation depth — how much of the product can run unattendedAutomation depth
How much of the product can run unattended
Cross agent portability — stories about cross agent portability in this arenaCross agent portability
Stories about cross agent portability in this arena
Discovery distribution — stories about discovery distribution in this arenaDiscovery distribution
Stories about discovery distribution in this arena
Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anything
✓8/10
Distribute a standard skill set to my whole team — via a marketplace, a shared repo, or files committed to the project
✓8/10
Installed skills trigger automatically from task context, with descriptions engineered so the agent activates the right skill at the right moment
~6/10
Docs onboarding — stories about docs onboarding in this arenaDocs onboarding
Stories about docs onboarding in this arena
Install experience — stories about install experience in this arenaInstall experience
Stories about install experience in this arena
Install
List what is installed and remove skills cleanly, without orphaned files or lingering instructions
~6/10
Openness — open source, data portability, and self-hosting storiesOpenness
Open source, data portability, and self-hosting stories
Privacy posture — data-handling and privacy storiesPrivacy posture
Data-handling and privacy stories
Safety review — stories about safety review in this arenaSafety review
Stories about safety review in this arena
Skill authoring — stories about skill authoring in this arenaSkill authoring
Stories about skill authoring in this arena
Testing quality — stories about testing quality in this arenaTesting quality
Stories about testing quality in this arena
Versioning updates — stories about versioning updates in this arenaVersioning updates
Stories about versioning updates in this arena
Sorted by importance (agentic first) (high → low) · 52/52 stories · click a row’s chevron for the rationale and evidence
Drive the product through a documented public API G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | partial | 5/10 | Xcommunity | |
Connect an agent via an official MCP server G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | 0/10 | ||
Delegate tasks to a built-in AI assistant inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Plug MCP servers into this product so it can use their tools G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 3 | none | untested | none yet | |
Use an official CLI G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 9/10 | Xcommunity | |
Run the product headlessly / in CI for automation G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | full | 8/10 | Xcommunity | |
Point an agent at llms.txt or agent-oriented docs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | partial | 5/10 | Tprobed | |
Download a machine-readable API spec (OpenAPI or equivalent) G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Operate the product with natural-language commands G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Rely on versioned APIs with a documented deprecation policy G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | 0/10 | ||
Build against official SDKs G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Explore an interactive API reference with runnable examples G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Get AI-generated insights and suggestions from my data inside the product G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Issue scoped/least-privilege API credentials for an agent G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Set up automations that run autonomously in the background G Agentic features | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | none | untested | none yet | |
Subscribe to events via webhooks G Agent access | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 2 | n/a | untested | none yet | |
Test against a sandbox environment without touching production data G Api quality | ai-native user | Agenticness — how well agents can access and operate the productAgenticness | 1 | none | untested | none yet | |
Install a skill collection with one documented command — a package-manager one-liner, CLI, or in-agent marketplace command — and it is active in my next session C Install | developer | Install experience — stories about install experience in this arenaInstall experience | 3 | full | 8/10 | Xcommunity | |
Install the same collection into multiple different coding agents — Claude Code, Codex, Cursor, and others — with per-harness instructions C Portability | developer | Cross agent portability — stories about cross agent portability in this arenaCross agent portability | 3 | full | 8/10 | Cclaimed | |
My coding agent can install a skill by itself — a non-interactive, promptless install path an agent can run headlessly end to end C Agent ops | ai-native user | Agent workflows — stories about agent workflows in this arenaAgent workflows | 3 | full | 8/10 | Cclaimed | |
There is a documented update path — marketplace auto-updates or an explicit update command — so I get fixes without reinstalling from scratch C Updates | developer | Versioning updates — stories about versioning updates in this arenaVersioning updates | 3 | full | 8/10 | Xcommunity | |
Author a new skill from a documented template — a SKILL.md with name and description frontmatter — without reverse-engineering existing skills C Authoring | developer | Skill authoring — stories about skill authoring in this arenaSkill authoring | 3 | full | 7/10 | Cclaimed | |
A quickstart takes me from nothing to a working installed skill in under five minutes C Onboarding | developer | Docs onboarding — stories about docs onboarding in this arenaDocs onboarding | 3 | partial | 6/10 | Xcommunity | |
Installed skills trigger automatically from task context, with descriptions engineered so the agent activates the right skill at the right moment C Triggering | developer | Discovery distribution — stories about discovery distribution in this arenaDiscovery distribution | 3 | partialfree | 6/10 | Cclaimed | |
Export all of my data in open formats and leave G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partial | 5/10 | Cclaimed | |
Review exactly what instructions and scripts a skill will add — list contents before installing and read every file afterward C Review | engineering-lead | Safety review — stories about safety review in this arenaSafety review | 3 | partial | 5/10 | Xcommunity | |
Self-host the core product G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 3 | partialfree | 4/10 | Tprobed | |
Define rules that trigger actions automatically on events G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 3 | n/a | untested | none yet | |
Prevent my data from being used to train AI models G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 3 | n/a | untested | none yet | |
Choose install scope — project-local files committed with my repo, or user-global across all projects C Install | developer | Install experience — stories about install experience in this arenaInstall experience | 2 | full | 9/10 | Cclaimed | |
Install only the specific skills I want from a collection instead of taking the whole bundle C Install | developer | Install experience — stories about install experience in this arenaInstall experience | 2 | fullfree | 9/10 | Cclaimed | |
Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anything C Discovery | developer | Discovery distribution — stories about discovery distribution in this arenaDiscovery distribution | 2 | full | 8/10 | Xcommunity | |
Distribute a standard skill set to my whole team — via a marketplace, a shared repo, or files committed to the project C Distribution | engineering-lead | Discovery distribution — stories about discovery distribution in this arenaDiscovery distribution | 2 | full | 8/10 | Xcommunity | |
Skills are plain markdown files and folders I can read, copy, and carry to another harness — not a proprietary binary format C Portability | developer | Cross agent portability — stories about cross agent portability in this arenaCross agent portability | 2 | full | 8/10 | Cclaimed | |
Skills follow the open Agent Skills specification so the same skill folder is valid beyond this one vendor's tooling C Spec | developer | Skill authoring — stories about skill authoring in this arenaSkill authoring | 2 | full | 8/10 | Cclaimed | |
Every skill documents what it does and when it activates, so I can predict my agent's new behavior before it surprises me C Onboarding | developer | Docs onboarding — stories about docs onboarding in this arenaDocs onboarding | 2 | fullfree | 7/10 | Cclaimed | |
My agent can author and package a new skill end to end by following the project's own spec, template, or meta-skill C Agent ops | ai-native user | Agent workflows — stories about agent workflows in this arenaAgent workflows | 2 | full | 7/10 | Cclaimed | |
Perform bulk operations across many items at once G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | partial | 6/10 | Cclaimed | |
The collection ships a meta-skill or tool that guides my agent through writing, improving, and packaging new skills C Authoring | developer | Skill authoring — stories about skill authoring in this arenaSkill authoring | 2 | partial | 5/10 | Cclaimed | |
Control data retention and deletion G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | partial | 4/10 | Xcommunity | |
Do everything through the API that I can do in the UI G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 4/10 | Xcommunity | |
Read the product's source under an open license G | ai-native user | Openness — open source, data portability, and self-hosting storiesOpenness | 2 | partial | 4/10 | Tprobed | |
The collection is actively maintained — recent releases, triaged issues, and accepted community contributions C Maintenance | developer | Testing quality — stories about testing quality in this arenaTesting quality | 2 | none | 0/10 | ||
The collection maintains tests or evals for its skills so changes are verified against regressions rather than shipped on vibes C Testing | developer | Testing quality — stories about testing quality in this arenaTesting quality | 2 | none | 0/10 | ||
The project documents its security posture — what skills can execute, the trust model for third-party skills, and any telemetry or data collection C Trust | engineering-lead | Safety review — stories about safety review in this arenaSafety review | 2 | none | 0/10 | ||
Choose where my data is stored (region/residency) G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | n/a | untested | none yet | |
Opt out of telemetry and usage tracking G | ai-native user | Privacy posture — data-handling and privacy storiesPrivacy posture | 2 | none | untested | none yet | |
Schedule recurring jobs or workflows G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 2 | n/a | untested | none yet | |
List what is installed and remove skills cleanly, without orphaned files or lingering instructions C Lifecycle | developer | Install experience — stories about install experience in this arenaInstall experience | 1 | partial | 6/10 | Xcommunity | |
Version, review, and roll back my automations G | ai-native user | Automation depth — how much of the product can run unattendedAutomation depth | 1 | disputed | 4/10 | Dcontradicted | |
Control when skill changes reach my team — pinned versions or a lockfile rather than silent behind-the-back updates C Pinning | engineering-lead | Versioning updates — stories about versioning updates in this arenaVersioning updates | 1 | disputed | 3/10 | Dcontradicted | |
Releases ship with notes or a changelog so I can see what changed in the skills before I take an update C Updates | developer | Versioning updates — stories about versioning updates in this arenaVersioning updates | 1 | none | 0/10 |
Opportunities — the stories that would move this product's scores, from its own judged verdictsOpportunitiestop 8 of 28 stories with headroom
What would move skills.sh’s scores — derived from its own judged verdicts, biggest headroom first. Each line quotes what the judge found missing; shipping it (or evidencing it publicly) is the fix.
Agenticness — how well agents can access and operate the productDelegate tasks to a built-in AI assistant inside the product
nonemoves Built-in AIimpact 45
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productPlug MCP servers into this product so it can use their tools
nonemoves agent-readyimpact 45
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productConnect an agent via an official MCP server
nonemoves agent-readyimpact 45
skills.sh is a CLI package manager that installs skill files/prompts into agent directories (via add/use/symlink mechanisms), not an MCP server; no evidence anywhere in the pack mentions an MCP server or MCP protocol integration, only file-based/CLI installation across supported agents.
Agenticness — how well agents can access and operate the productGet AI-generated insights and suggestions from my data inside the product
nonemoves Built-in AIimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productSet up automations that run autonomously in the background
nonemoves Built-in AIimpact 30
The axis applies to this product kind (peer products hold positive or none verdicts on this story), so lack of evidence for an applicable capability is "none", never "na".
Agenticness — how well agents can access and operate the productOperate the product with natural-language commands
nonemoves Built-in AIimpact 30
skills.sh is a structured CLI (npm-style syntax like `npx skills add`, `--skill`, `--agent` flags) with no evidence of a natural-language command interface for operating the tool itself; all documented usage requires exact flag syntax.
Agenticness — how well agents can access and operate the productBuild against official SDKs
nonemoves agent-readyimpact 30
Evidence shows only a CLI (`skills` npx tool) and a SKILL.md specification/validator, not an official SDK (e.g., a JS/Python library) for programmatic integration; no SDK is mentioned anywhere in the pack.
Agenticness — how well agents can access and operate the productDownload a machine-readable API spec (OpenAPI or equivalent)
nonemoves API qualityimpact 30
Evidence shows a CLI tool and a Skill-format specification (SKILL.md schema, agentskills.io/specification.md), but no OpenAPI or machine-readable API spec for skills.sh itself; a community comment explicitly requests 'Please make a rest API!' implying none currently exists.
Showing the top 8 of 28 — every none/partial verdict in the story verdicts table is headroom.
Think a verdict is wrong? Every verdicts-table row has a Flag link — see the methodology.
Coverage map — which docs area, API section, or community source covers which judged storiesCoverage map5 surfaces · 30 covered stories
Where the cited evidence behind each covered verdict came from — the same citations the verdicts table shows, no extra judging.
GitHub README28 stories
- My agent can author and package a new skill end to end by following the project's own spec, template, or meta-skill
- My coding agent can install a skill by itself — a non-interactive, promptless install path an agent can run headlessly end to end
- Point an agent at llms.txt or agent-oriented docs
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Perform bulk operations across many items at once
- Version, review, and roll back my automations
- Install the same collection into multiple different coding agents — Claude Code, Codex, Cursor, and others — with per-harness instructions
- Skills are plain markdown files and folders I can read, copy, and carry to another harness — not a proprietary binary format
- Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anything
- Distribute a standard skill set to my whole team — via a marketplace, a shared repo, or files committed to the project
- A quickstart takes me from nothing to a working installed skill in under five minutes
- Install a skill collection with one documented command — a package-manager one-liner, CLI, or in-agent marketplace command — and it is active in my next session
- Choose install scope — project-local files committed with my repo, or user-global across all projects
- Install only the specific skills I want from a collection instead of taking the whole bundle
- List what is installed and remove skills cleanly, without orphaned files or lingering instructions
- Do everything through the API that I can do in the UI
- Export all of my data in open formats and leave
- Read the product's source under an open license
- Self-host the core product
- Control data retention and deletion
- Review exactly what instructions and scripts a skill will add — list contents before installing and read every file afterward
- Author a new skill from a documented template — a SKILL.md with name and description frontmatter — without reverse-engineering existing skills
- The collection ships a meta-skill or tool that guides my agent through writing, improving, and packaging new skills
- Skills follow the open Agent Skills specification so the same skill folder is valid beyond this one vendor's tooling
- Control when skill changes reach my team — pinned versions or a lockfile rather than silent behind-the-back updates
- There is a documented update path — marketplace auto-updates or an explicit update command — so I get fixes without reinstalling from scratch
Hacker News14 stories
- Run the product headlessly / in CI for automation
- Use an official CLI
- Drive the product through a documented public API
- Version, review, and roll back my automations
- Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anything
- Distribute a standard skill set to my whole team — via a marketplace, a shared repo, or files committed to the project
- A quickstart takes me from nothing to a working installed skill in under five minutes
- Install a skill collection with one documented command — a package-manager one-liner, CLI, or in-agent marketplace command — and it is active in my next session
- List what is installed and remove skills cleanly, without orphaned files or lingering instructions
- Do everything through the API that I can do in the UI
- Control data retention and deletion
- Review exactly what instructions and scripts a skill will add — list contents before installing and read every file afterward
- Control when skill changes reach my team — pinned versions or a lockfile rather than silent behind-the-back updates
- There is a documented update path — marketplace auto-updates or an explicit update command — so I get fixes without reinstalling from scratch
Home docs8 stories
- Install the same collection into multiple different coding agents — Claude Code, Codex, Cursor, and others — with per-harness instructions
- Skills are plain markdown files and folders I can read, copy, and carry to another harness — not a proprietary binary format
- Installed skills trigger automatically from task context, with descriptions engineered so the agent activates the right skill at the right moment
- Every skill documents what it does and when it activates, so I can predict my agent's new behavior before it surprises me
- Install a skill collection with one documented command — a package-manager one-liner, CLI, or in-agent marketplace command — and it is active in my next session
- Review exactly what instructions and scripts a skill will add — list contents before installing and read every file afterward
- Author a new skill from a documented template — a SKILL.md with name and description frontmatter — without reverse-engineering existing skills
- Skills follow the open Agent Skills specification so the same skill folder is valid beyond this one vendor's tooling
Specification docs5 stories
- My agent can author and package a new skill end to end by following the project's own spec, template, or meta-skill
- Every skill documents what it does and when it activates, so I can predict my agent's new behavior before it surprises me
- Author a new skill from a documented template — a SKILL.md with name and description frontmatter — without reverse-engineering existing skills
- The collection ships a meta-skill or tool that guides my agent through writing, improving, and packaging new skills
- Skills follow the open Agent Skills specification so the same skill folder is valid beyond this one vendor's tooling
skills.sh4 stories
- Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anything
- Distribute a standard skill set to my whole team — via a marketplace, a shared repo, or files committed to the project
- Do everything through the API that I can do in the UI
- Self-host the core product
Probe proofs — replayable recordings from the probe harnessProbe proofs
Replayable recordings from our probe harness — see the Prove-It protocol to submit one.
$npx -y skills --versionreproduced$ npx -y skills --version \|/1.5.24 \
$npx -y skills add vercel-labs/agent-skills --listreproduced$ npx -y skills add vercel-labs/agent-skills --list \|/ ███████╗██╗ ██╗██╗██╗ ██╗ ███████╗ ██╔════╝██║ ██╔╝██║██║ ██║ ██╔════╝ ███████╗█████╔╝ ██║██║ ██║ ███████╗ ╚════██║██╔═██╗ ██║██║ ██║ ╚════██║ ███████║██║ ██╗██║███████╗███████╗███████║ ╚══════╝╚═╝ ╚═╝╚═╝╚══════╝╚══════╝╚══════╝ ┌ skills │ ◇ Source: https://github.com/vercel-labs/agent-skills.git │ [ 3 5 m ◒ [ 3 9m F e t c h i n g s k i l l s … [ 3 5 m ◐ [ 3 9m F e t c h i n g s k i l l s … [ 3 5 m ◓ [ 3 9m F e t c h i n g s k i l l s … [ 3 5 m ◑ [ 3 9m F e t c h i n g s k i l l s … [ 3 5 m ◒ [ 3 9m F e t c h i n g s k i l l s … [ 3 5 m ◐ [ 3 9m F e t c h i n g s k i l l s … [ 3 5 m ◓ [ 3 9m F e t c h i n g s k i l l s …◇ Found 9 skills │ ◇ Available Skills │ │ vercel-composition-patterns │ │ React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes. │ │ deploy-to-vercel │ │ Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment". │ │ vercel-react-best-practices │ │ React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements. │ │ vercel-react-native-skills │ │ React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs. │ │ vercel-react-view-transitions │ │ Guide for implementing smooth, native-feeling animations using React's View Transition API (`<ViewTransition>` component, `addTransitionType`, and CSS view transition pseudo-elements). Use this skill whenever the user wants to add page transitions, animate route changes, create shared element animations, animate enter/exit of components, animate list reorder, implement directional (forward/back) navigation animations, or integrate view transitions in Next.js. Also use when the user mentions view transitions, `startViewTransition`, `ViewTransition`, transition types, or asks about animating between UI states in React without third-party animation libraries. │ │ vercel-cli-with-[redacted]s │ │ Deploy and manage projects on Vercel using [redacted]-based authentication. Use when working with Vercel CLI using access [redacted]s rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel". │ │ vercel-optimize │ │ Use for Vercel cost and performance optimization on deployed projects, especially Next.js, SvelteKit, Nuxt, and limited Astro apps. Collect Vercel metrics, usage, project config, and code scan results first; investigate only metric-backed candidates; produce ranked recommendations grounded in verified files and version-aware Vercel/framework docs. Trigger for Vercel bill reduction, slow or expensive routes, caching opportunities, Function Invocations, Build Minutes, Fast Data Transfer, Core Web Vitals, Bot Management, Fluid compute, or cost breakdown requests. │ │ web-design-guidelines │ │ Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices". │ │ writing-guidelines │ │ Review docs/prose for Writing Guidelines compliance. Use when asked to "review my docs", "check writing style", "audit prose", "review docs voice and tone", or "check this page against the writing handbook". │ └ Use --skill <name> to install specific skills \
Claims vs evidence — vendor claims reconciled against independent verdictsClaims vs evidence
6 of 15 testable claims verified · 1 contradicted → integrity 27/100
26 distinct capability claims found in skills.sh’s own claimed-docs/GitHub materials, reconciled against our judge’s independent verdicts.
6
Verified
8
Unverified
1
Contradicted
14
Undersold
Verified (12)
“Install a skill collection from a GitHub repo with a single npx command”
Install a skill collection with one documented command — a package-manager one-liner, CLI, or in-agent marketplace command — and it is active in my next sessionfullproof ↗
“List available skills in a repo without installing them”
Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anythingfullproof ↗
“Non-interactive installation flag suitable for CI/CD pipelines”
Run the product headlessly / in CI for automationfullproof ↗
“List all installed skills, similar to `npm ls`”
List what is installed and remove skills cleanly, without orphaned files or lingering instructionspartialproof ↗
“Search for skills interactively or by keyword”
Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anythingfullproof ↗
“Search for skills across every repository owned by an org or user”
Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anythingfullproof ↗
“Update installed skills to their latest versions”
There is a documented update path — marketplace auto-updates or an explicit update command — so I get fixes without reinstalling from scratchfullproof ↗
“Remove installed skills from agents cleanly”
List what is installed and remove skills cleanly, without orphaned files or lingering instructionspartialproof ↗
“Project-scoped install location committed with the repo and shared with the team by default”
Distribute a standard skill set to my whole team — via a marketplace, a shared repo, or files committed to the projectfullproof ↗
“A public Skills Leaderboard lets you discover popular skills”
Browse or search a catalog of available skills — a registry, leaderboard, or marketplace listing — before installing anythingfullproof ↗
“Update a single named skill without updating everything else”
There is a documented update path — marketplace auto-updates or an explicit update command — so I get fixes without reinstalling from scratchfullproof ↗
“Remove a specific skill from a specific agent by name”
List what is installed and remove skills cleanly, without orphaned files or lingering instructionspartialproof ↗
Unverified (12)
“Generate and pipe a skill's prompt directly into an agent (e.g. piping to claude) for immediate use”
My coding agent can install a skill by itself — a non-interactive, promptless install path an agent can run headlessly end to endfullproof ↗
“`skills use` resolves sources like `skills add` but writes files to a temp dir and prints only the generated prompt to stdout”
My coding agent can install a skill by itself — a non-interactive, promptless install path an agent can run headlessly end to endfullproof ↗
“Install only specific named skills from a repo instead of the whole bundle (or '*' for all)”
Install only the specific skills I want from a collection instead of taking the whole bundlefullproof ↗
“Target specific coding agents when installing (e.g. claude-code, codex)”
Install the same collection into multiple different coding agents — Claude Code, Codex, Cursor, and others — with per-harness instructionsfullproof ↗
“Install skills to a user-global directory instead of the project”
Choose install scope — project-local files committed with my repo, or user-global across all projectsfullproof ↗
“Create a new SKILL.md template via a scaffolding command”
Author a new skill from a documented template — a SKILL.md with name and description frontmatter — without reverse-engineering existing skillsfullproof ↗
“A skill can be built once and reused across any skills-compatible agent”
Install the same collection into multiple different coding agents — Claude Code, Codex, Cursor, and others — with per-harness instructionsfullproof ↗
“A skill can be built once and reused across any skills-compatible agent”
Skills are plain markdown files and folders I can read, copy, and carry to another harness — not a proprietary binary formatfullproof ↗
“Project-scoped install location committed with the repo and shared with the team by default”
Choose install scope — project-local files committed with my repo, or user-global across all projectsfullproof ↗
“Officially supports OpenCode, Claude Code, Codex, Cursor, and 73+ other agents”
Install the same collection into multiple different coding agents — Claude Code, Codex, Cursor, and others — with per-harness instructionsfullproof ↗
“Agents load only each skill's name and description at startup, loading full content only when relevant”
Installed skills trigger automatically from task context, with descriptions engineered so the agent activates the right skill at the right momentpartialproof ↗
“A validator command checks a skill folder against the skill spec”
Skills follow the open Agent Skills specification so the same skill folder is valid beyond this one vendor's toolingfullproof ↗
Contradicted (1)
“`skills experimental_install` restores a team's exact skill set from a skills-lock.json file”
Control when skill changes reach my team — pinned versions or a lockfile rather than silent behind-the-back updatesdisputedproof ↗
Undersold (14)
My agent can author and package a new skill end to end by following the project's own spec, template, or meta-skillfullproof ↗
Point an agent at llms.txt or agent-oriented docspartialproof ↗
Drive the product through a documented public APIpartialproof ↗
Perform bulk operations across many items at oncepartialproof ↗
A quickstart takes me from nothing to a working installed skill in under five minutespartialproof ↗
Every skill documents what it does and when it activates, so I can predict my agent's new behavior before it surprises mefullproof ↗
Do everything through the API that I can do in the UIpartialproof ↗
Export all of my data in open formats and leavepartialproof ↗
Read the product's source under an open licensepartialproof ↗
Review exactly what instructions and scripts a skill will add — list contents before installing and read every file afterwardpartialproof ↗
The collection ships a meta-skill or tool that guides my agent through writing, improving, and packaging new skillspartialproof ↗
Claims outside our story set (3)
Real capability claims found in skills.sh’s own materials, but no story in this arena’s taxonomy covers them yet — that’s feedback on the taxonomy, not a mark against the product.
“Same install command works for public and private repos using existing configured auth”
source ↗“Installs create symlinks from each agent to one canonical skill copy, giving a single source of truth for updates”
source ↗“Install a skill directly from a raw SKILL.md file or archive download URL”
source ↗
Business model
MIT open-source CLI (npm "skills") plus the free skills.sh registry and leaderboard for the open agent-skills ecosystem; no paid tier — Vercel monetizes its hosting platform, not the CLI.
pricing ↗Score trend
How this product’s scores have moved as evidence and verdicts are re-derived — a point per change, not per day.
Try Experimental
Run it in the microterminal →Recorded agent sessions — and a live MCP handshake where the vendor ships one.
Flag
⚑ Flag a verdictThink a verdict is wrong? Opens a prefilled GitHub issue — or use the ⚑ next to any verdict above.
For agents
Agent surface uptime llms.txt 100% (30d, checked every 6h since Sep 8 '26)
