vercel-cli-with-tokens

Deploy and manage projects on Vercel using token-based authentication. Use when working with Vercel CLI using access tokens rather than interactive login — e.g. "deploy to vercel", "set up vercel", "add environment variables to vercel".

Quality

83%

Does it follow best practices?

Impact

—

No eval scenarios have been run

Securityby

Advisory

Suggest reviewing before use

Quality

Content

77%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This is a strong, highly actionable skill with excellent workflow clarity and concrete executable commands throughout. Its main weakness is length — at ~250 lines with no supporting bundle files, it packs a lot of content (including Stripe plan details and extensive troubleshooting) into a single file that could benefit from splitting into focused reference documents. The security practices and working agreement sections are well-crafted guardrails.

Suggestions

Extract the Stripe Projects section and Pro plan details into a separate STRIPE_INTEGRATION.md reference file to reduce the main skill's token footprint.

Consider moving the Troubleshooting section into a separate TROUBLESHOOTING.md file, referenced from the main skill with a one-line pointer.

Dimension	Reasoning	Score
Conciseness	The skill is generally efficient and avoids explaining basic concepts Claude already knows, but it's quite long (~250 lines) with some redundancy — e.g., the token lookup steps repeat similar grep/export patterns multiple times, and the deployment section covers many overlapping scenarios that could be condensed. The Stripe Projects section and Pro plan details feel like they could be in a separate reference file.	2 / 3
Actionability	Nearly every instruction includes concrete, copy-paste-ready bash commands. The skill provides specific commands for each scenario (token lookup, linking, deploying, env vars, domains, inspection) with clear flags and arguments. The security guidance (don't use --token flag) includes both bad and good examples.	3 / 3
Workflow Clarity	The skill has a clear sequential flow: locate token → locate project/team → install CLI → deploy. Decision trees are well-structured (e.g., 'Quick Deploy' vs 'Full Deploy Flow', git push vs CLI deploy). Validation checkpoints are present (check env first, verify with `vercel whoami`, inspect deployments, check build logs). The 'ask before pushing' and 'default to preview' constraints serve as safety gates.	3 / 3
Progressive Disclosure	The content is well-organized with clear headers and logical sections, but it's entirely monolithic — the Stripe Projects plan details, the `.vercel/` directory explanation, and the troubleshooting section could reasonably be split into separate reference files. With no bundle files provided, there's no progressive disclosure structure at all, and the single file is quite long.	2 / 3
	Total	10 / 12 Passed

Description

89%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

This is a solid skill description that clearly identifies its niche (Vercel deployment with token-based auth) and provides explicit trigger guidance with natural user phrases. The main weakness is that the 'what' portion could be more specific about the full range of concrete actions supported beyond deploying and managing environment variables.

Suggestions

Expand the capability list with more specific actions, e.g., 'Deploy projects, configure domains, set environment variables, check deployment status on Vercel' to improve specificity.

Dimension	Reasoning	Score
Specificity	Names the domain (Vercel deployment) and mentions some actions like 'deploy', 'manage', and 'add environment variables', but doesn't comprehensively list specific concrete actions beyond those. 'Manage projects' is somewhat vague.	2 / 3
Completeness	Clearly answers both 'what' (deploy and manage projects on Vercel using token-based authentication) and 'when' (explicit 'Use when' clause with specific trigger scenarios like deploying, setting up, and adding environment variables).	3 / 3
Trigger Term Quality	Includes strong natural trigger terms users would actually say: 'deploy to vercel', 'set up vercel', 'add environment variables to vercel', 'Vercel CLI', 'access tokens'. Good coverage of common user phrases.	3 / 3
Distinctiveness Conflict Risk	Highly distinctive — specifically targets Vercel with token-based authentication, differentiating it from general deployment skills or other hosting platform skills. The mention of 'access tokens rather than interactive login' further narrows the niche.	3 / 3
	Total	11 / 12 Passed

Validation

100%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 11 / 11 Passed

Validation for skill structure

No warnings or errors.

Repository: vercel-labs/agent-skills
Commit: f8a72b9

Reviewed: 16 days ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.