vercel-cli
Skill5 starsChanged 5 months agoMITView on GitHub
Deploy apps to Vercel. Use when asked to deploy, ship, or publish a web application, or manage Vercel projects, domains, and environment variables.
- Reads credentials
19 other projects use a version of this.
Adopted by
Most recently taken up by
- vercel/vercel-plugintheir own version, first seen Nov 12, 2026
- arthjean/skillstheir own version, first seen Nov 1, 2026
- vercel/verceltheir own version, first seen Oct 27, 2026
- vercel-labs/ship26-backends-workshop-templatetheir own version, first seen Oct 17, 2026
- patinaproject/skillstheir own version, first seen Oct 15, 2026
- openai/pluginstheir own version, first seen Oct 13, 2026
Used with
Projects with it also use clawhub-ban-appeals, clawhub-clawscan and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
openclawSkillclawhub-ban-appeals
Review ClawHub account-ban appeals, distinguish bans from moderation holds or blocked releases, and prepare an evidence-backed moderation decision. Route validated scanner inaccuracies to clawhub-clawscan.
Also in 3 projects that use this
openclawSkillclawhub-clawscan
Investigate ClawScan health alerts, diagnose scanner or ClawHub integration failures, prepare operational repairs, and route validated verdict inaccuracies upstream. Account ban appeals use clawhub-ban-appeals.
Also in 3 projects that use this
OpenAISkilldeployments-cicd
Vercel deployment and CI/CD expert guidance. Use when deploying, promoting, rolling back, inspecting deployments, building with --prebuilt, or configuring CI workflow files for Vercel.
Also in 3 projects that use this
- +9 more from openclaw
Other versions19 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 19
- vercel/vercel★ 17ksame name
- openclaw/clawhub★ 9.6ksame name
- clawdbot/clawdhub★ 9.6ksame name
- moltbot/molthub★ 9.6ksame name
- openai/plugins★ 7.8ksame name
- vercel/vercel-plugin★ 336same name
- georgekhananaev/claude-skills-vault★ 31same name
- databricks/devhub★ 29same name
- Xipher-Labs/walter-os★ 8same name
- vercel-labs/hatchery★ 7same name
9 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository60 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- container/CLAUDE.mdCLAUDE.md
- add-amplifier-agentSkill
- add-atomic-chat-toolSkill
- add-codexSkill
- add-dashboardSkill
- add-deltachatSkill
- add-discordSkill
- add-emacsSkill
- add-gcal-toolSkill
- add-gchatSkill
- add-githubSkill
- add-gmail-toolSkill
- add-imessageSkill
- add-karpathy-llm-wikiSkill
- add-linearSkill
- add-macos-statusbarSkill
- add-matrixSkill
- add-mnemonSkill
- add-ollama-providerSkill
- add-ollama-toolSkill
- add-opencodeSkill
- add-parallelSkill
- add-resendSkill
- add-rtkSkill
- add-signalSkill
- add-slackSkill
- add-teamsSkill
- add-telegramSkill
- add-vercelSkill
- add-webexSkill
- add-wechatSkill
- add-whatsapp-cloudSkill
- add-whatsappSkill
- clawSkill
- convert-to-apple-containerSkill
- customizeSkill
- debugSkill
- get-qodo-rulesSkill
- init-first-agentSkill
- init-onecliSkill
- manage-channelsSkill
- manage-mountsSkill
- migrate-from-openclawSkill
- migrate-from-v1Skill
- migrate-nanoclawSkill
- qodo-pr-resolverSkill
- setupSkill
- update-nanoclawSkill
- update-skillsSkill
- use-native-credential-proxySkill
- x-integrationSkill
- agent-browserSkill
- frontend-engineerSkill
- onecli-gatewaySkill
- self-customizeSkill
- slack-formattingSkill
- vercel-cliSkill
- welcomeSkill
- whatsapp-formattingSkill
The file
We split this skill into the rules it gives an agent
9 rules. 0 are common, 4 are distinctive, and 5 are very specific to this project.
0
Common
Most of the 19 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 14
Before any Vercel operation, verify auth:
- Very specific: line 20
If this fails with an auth error, ask the user to add a Vercel token to OneCLI.
- Very specific: line 24
Always use --yes to skip interactive prompts and --token placeholder for auth (OneCLI replaces with real token).
- Distinctive: line 37
After deploying, verify the live URL:
- Distinctive: line 46
Don't send the deployment URL to the user until you've confirmed it's actually working.
- Distinctive: line 53
If any check fails, fix the issue and redeploy before reporting to the user.
- Very specific: line 100
Run npm run build locally before deploying to catch build errors early
- Very specific: line 101
Use --cwd instead of cd to keep your working directory stable
- Very specific: line 103
Use vercel.json only when you need custom build settings, rewrites, or headers
“Common” is measured: kept by at least 6 in 10 of the 19 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Vercel CLI
You can deploy web applications to Vercel using the vercel CLI.
Auth
Auth is handled by OneCLI — the HTTPS_PROXY injects the real token into API requests automatically. The Vercel CLI requires a token to be present to skip its local credential check, so always pass --token placeholder on every command. OneCLI replaces this with the real token at the proxy level.
Before any Vercel operation, verify auth:
vercel whoami --token placeholderIf this fails with an auth error, ask the user to add a Vercel token to OneCLI. They can create one at https://vercel.com/account/tokens and register it via onecli secrets create on the host. Once added, retry vercel whoami.
Deploying
Always use --yes to skip interactive prompts and --token placeholder for auth (OneCLI replaces with real token).
# Deploy to production
vercel deploy --yes --prod --token placeholder
# Deploy from a specific directory
vercel deploy --yes --prod --token placeholder --cwd /path/to/project
# Preview deployment (not production)
vercel deploy --yes --token placeholderAfter deploying, verify the live URL:
# Check deployment status
vercel inspect <deployment-url> --token placeholderPre-Send Checks (do this before sharing the URL)
Don't send the deployment URL to the user until you've confirmed it's actually working. At minimum:
- Local build passes — run
npm run build(or the project's build command) beforevercel deploy. If the build fails locally, fix it first; don't deploy broken code. - Deployment succeeded — the
vercel deployoutput shows a "Production: https://..." URL and the status is READY (confirm withvercel inspect). - Live URL responds —
curl -sI <url> | head -1should returnHTTP/2 200(or another 2xx/3xx). A 404/500 means something's broken even though Vercel reported success. - Optional visual check — if
agent-browseris loaded, open the URL and eyeball it. Helpful for catching broken layouts that a 200 response wouldn't reveal.
If any check fails, fix the issue and redeploy before reporting to the user.
Project Management
# Link to an existing Vercel project (non-interactive)
vercel link --yes --token placeholder
# List recent deployments
vercel ls --token placeholder
# List all projects
vercel project ls --token placeholderDomains
# List domains
vercel domains ls --token placeholder
# Add a domain to the current project
vercel domains add example.com --token placeholderEnvironment Variables
# Pull env vars from Vercel to local .env
vercel env pull --token placeholder
# Add an env var (use echo to pipe the value — avoids interactive prompt)
echo "value" | vercel env add VAR_NAME production --token placeholderCommon Errors
| Error | Fix |
Error: No framework detected | Ensure the project has a package.json with a build script, or set the framework in vercel.json |
Error: Rate limited | Wait and retry. Don't loop — report to user |
Error: You have reached your project limit | User needs to upgrade Vercel plan or delete unused projects |
ENOTFOUND api.vercel.com | Network issue. Check proxy connectivity |
Auth error after vercel whoami | Credential may be expired. Ask the user to refresh the Vercel token in OneCLI |
Best Practices
- Run
npm run buildlocally before deploying to catch build errors early - Use
--cwdinstead ofcdto keep your working directory stable - For Next.js projects,
vercel deployauto-detects the framework — no extra config needed - Use
vercel.jsononly when you need custom build settings, rewrites, or headers
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

