☁️ DevOps & Cloud · Incidents & Edge Deploys

Deploy to Vercel with token-based CLI auth

Authenticate Vercel CLI via a stored token instead of browser OAuth — the reliable path when clock drift breaks login flows. Use when deploying, linking projects, or scripting CI-style pushes.

intermediate~15 minDevOps EngineersSREsCloud Architects

Steps

1Read the token from local storage at runtime into a shell variable only
2Never echo, log, commit, or write the token into any file
3Link once per project with vercel link --yes --project <name> --token $tok
4Ship production with vercel deploy --prod --yes --token $tok
5Prefer git push auto-deploys for repos already linked to GitHub integration
6Scope team with --scope when the token spans multiple teams

Common Pitfalls

▲Browser login loops caused by PC clock skew — use tokens exclusively
▲Tokens pasted into terminal history via inline export

Commands

Install with skills CLI

$ npx skills add aniruddhaadak80/skills --skill vercel-token-deploy

Install globally

$ npx skills add aniruddhaadak80/skills --skill vercel-token-deploy -g

Link project

$ vercel link --yes --project <name> --token $VERCEL_TOKEN

Production deploy

$ vercel deploy --prod --yes --token $VERCEL_TOKEN

Tags

#vercel#cli#deployment#devops-cloud#incidents-vercel

Install this skill

$ npx skills add aniruddhaadak80/skills --skill vercel-token-deploy -a opencode

SKILL.md

# Deploy to Vercel with token-based CLI auth

> Authenticate Vercel CLI via a stored token instead of browser OAuth — the reliable path when clock drift breaks login flows. Use when deploying, linking projects, or scripting CI-style pushes.

## When to Use This Skill

Authenticate Vercel CLI via a stored token instead of browser OAuth — the reliable path when clock drift breaks login flows. Use when deploying, linking projects, or scripting CI-style pushes.

## Steps

1. Read the token from local storage at runtime into a shell variable only
2. Never echo, log, commit, or write the token into any file
3. Link once per project with vercel link --yes --project <name> --token $tok
4. Ship production with vercel deploy --prod --yes --token $tok
5. Prefer git push auto-deploys for repos already linked to GitHub integration
6. Scope team with --scope when the token spans multiple teams

## Common Pitfalls

- Browser login loops caused by PC clock skew — use tokens exclusively
- Tokens pasted into terminal history via inline export

View source on GitHub ↗

Roles, comms cadence, and mitigation-first mindset that turns chaos into checklist.

☁️ DevOps & Cloud·~30m

Open →

Ship frontends via edge platforms safelyfoundation

Preview-per-PR, promotion flows, and env hygiene on platforms like Vercel/Netlify.

☁️ DevOps & Cloud·~20m