agentleFS
MicrosoftKnown publishermicrosoft/amplifier-app-nanoclaw/.claude/skills/add-vercel/container-skills/vercel-cli/SKILL.md

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

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.
  • openclawSkill

    clawhub-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

  • openclawSkill

    clawhub-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

  • OpenAISkill

    deployments-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

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
  1. Distinctive:

    Before any Vercel operation, verify auth:

    line 14
  2. Very specific:

    If this fails with an auth error, ask the user to add a Vercel token to OneCLI.

    line 20
  3. Very specific:

    Always use --yes to skip interactive prompts and --token placeholder for auth (OneCLI replaces with real token).

    line 24
  4. Distinctive:

    After deploying, verify the live URL:

    line 37
  5. Distinctive:

    Don't send the deployment URL to the user until you've confirmed it's actually working.

    line 46
  6. Distinctive:

    If any check fails, fix the issue and redeploy before reporting to the user.

    line 53
  7. Very specific:

    Run npm run build locally before deploying to catch build errors early

    line 100
  8. Very specific:

    Use --cwd instead of cd to keep your working directory stable

    line 101
  9. Very specific:

    Use vercel.json only when you need custom build settings, rewrites, or headers

    line 103

“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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 placeholder

If 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 placeholder

After deploying, verify the live URL:

# Check deployment status
vercel inspect <deployment-url> --token placeholder

Pre-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:

  1. Local build passes — run npm run build (or the project's build command) before vercel deploy. If the build fails locally, fix it first; don't deploy broken code.
  2. Deployment succeeded — the vercel deploy output shows a "Production: https://..." URL and the status is READY (confirm with vercel inspect).
  3. Live URL responds — curl -sI <url> | head -1 should return HTTP/2 200 (or another 2xx/3xx). A 404/500 means something's broken even though Vercel reported success.
  4. Optional visual check — if agent-browser is 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 placeholder

Domains

# List domains
vercel domains ls --token placeholder

# Add a domain to the current project
vercel domains add example.com --token placeholder

Environment 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 placeholder

Common Errors

ErrorFix
Error: No framework detectedEnsure the project has a package.json with a build script, or set the framework in vercel.json
Error: Rate limitedWait and retry. Don't loop — report to user
Error: You have reached your project limitUser needs to upgrade Vercel plan or delete unused projects
ENOTFOUND api.vercel.comNetwork issue. Check proxy connectivity
Auth error after vercel whoamiCredential may be expired. Ask the user to refresh the Vercel token in OneCLI

Best Practices

  • Run npm run build locally before deploying to catch build errors early
  • Use --cwd instead of cd to keep your working directory stable
  • For Next.js projects, vercel deploy auto-detects the framework — no extra config needed
  • Use vercel.json only when you need custom build settings, rewrites, or headers

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.