[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M781M8YTYRZKBRSJS6RDKFE4":3,"skill-same:01M781M8YTYRZKBRSJS6RDKFE4":56},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":27,"commitSha":28,"skillDirectory":29,"forksCount":30,"repositoryHtmlUrl":31,"repositoryHomepageUrl":6,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":34,"updatedAt":35,"install":36,"resources":49},"01M781M8YTYRZKBRSJS6RDKFE4","vercel-agent-vercel-cli-with-tokens",null,"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\".","TheAngryPit\u002FTheAngrySkills","TheAngryPit","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F7040636?v=4","01M7803EENA9ATXJ46S9268QJX","Vitor Cepeda Lopes","01M7803EF9FMF4G4420XE4DV7Y",0,"MIT","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-vercel-agent-skills\u002Fvercel-agent-vercel-cli-with-tokens\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: vercel-agent-vercel-cli-with-tokens\ndescription: \"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\\\".\"\nmetadata:\n  author: vercel\n  version: \"1.0.0\"\n---\n\n# Vercel CLI with Tokens\n\nDeploy and manage projects on Vercel using the CLI with token-based authentication, without relying on `vercel login`.\n\n## Step 1: Locate the Vercel Token\n\nBefore running any Vercel CLI commands, identify where the token is coming from. Work through these scenarios in order:\n\n### A) `VERCEL_TOKEN` is already set in the environment\n\n```bash\nprintenv VERCEL_TOKEN\n```\n\nIf this returns a value, you're ready. Skip to Step 2.\n\n### B) Token is in a `.env` file under `VERCEL_TOKEN`\n\n```bash\ngrep '^VERCEL_TOKEN=' .env 2>\u002Fdev\u002Fnull\n```\n\nIf found, export it:\n\n```bash\nexport VERCEL_TOKEN=$(grep '^VERCEL_TOKEN=' .env | cut -d= -f2-)\n```\n\n### C) Token is in a `.env` file under a different name\n\nLook for any variable that looks like a Vercel token (Vercel tokens typically start with `vca_`):\n\n```bash\ngrep -i 'vercel' .env 2>\u002Fdev\u002Fnull\n```\n\nInspect the output to identify which variable holds the token, then export it as `VERCEL_TOKEN`:\n\n```bash\nexport VERCEL_TOKEN=$(grep '^\u003CVARIABLE_NAME>=' .env | cut -d= -f2-)\n```\n\n### D) No token found — ask the user\n\nIf none of the above yield a token, ask the user to provide one. They can create a Vercel access token at vercel.com\u002Faccount\u002Ftokens.\n\n---\n\n**Important:** Once `VERCEL_TOKEN` is exported as an environment variable, the Vercel CLI reads it natively — **do not pass it as a `--token` flag**. Putting secrets in command-line arguments exposes them in shell history and process listings.\n\n```bash\n# Bad — token visible in shell history and process listings\nvercel deploy --token \"vca_abc123\"\n\n# Good — CLI reads VERCEL_TOKEN from the environment\nexport VERCEL_TOKEN=\"vca_abc123\"\nvercel deploy\n```\n\n## Step 2: Locate the Project and Team\n\nSimilarly, check for the project ID and team scope. These let the CLI target the right project without needing `vercel link`.\n\n```bash\n# Check environment\nprintenv VERCEL_PROJECT_ID\nprintenv VERCEL_ORG_ID\n\n# Or check .env\ngrep -i 'vercel' .env 2>\u002Fdev\u002Fnull\n```\n\n**If you have a project URL** (e.g. `https:\u002F\u002Fvercel.com\u002Fmy-team\u002Fmy-project`), extract the team slug:\n\n```bash\n# e.g. \"my-team\" from \"https:\u002F\u002Fvercel.com\u002Fmy-team\u002Fmy-project\"\necho \"$PROJECT_URL\" | sed 's|https:\u002F\u002Fvercel.com\u002F||' | cut -d\u002F -f1\n```\n\n**If you have both `VERCEL_ORG_ID` and `VERCEL_PROJECT_ID` in your environment**, export them — the CLI will use these automatically and skip any `.vercel\u002F` directory:\n\n```bash\nexport VERCEL_ORG_ID=\"\u003Corg-id>\"\nexport VERCEL_PROJECT_ID=\"\u003Cproject-id>\"\n```\n\nNote: `VERCEL_ORG_ID` and `VERCEL_PROJECT_ID` must be set together — setting only one causes an error.\n\n## CLI Setup\n\nEnsure the Vercel CLI is installed and up to date:\n\n```bash\nnpm install -g vercel\nvercel --version\n```\n\n## Deploying a Project\n\nAlways deploy as **preview** unless the user explicitly requests production. Choose a method based on what you have available.\n\n### Quick Deploy (have project ID — no linking needed)\n\nWhen `VERCEL_TOKEN` and `VERCEL_PROJECT_ID` are set in the environment, deploy directly:\n\n```bash\nvercel deploy -y --no-wait\n```\n\nWith a team scope (either via `VERCEL_ORG_ID` or `--scope`):\n\n```bash\nvercel deploy --scope \u003Cteam-slug> -y --no-wait\n```\n\nProduction (only when explicitly requested):\n\n```bash\nvercel deploy --prod --scope \u003Cteam-slug> -y --no-wait\n```\n\nCheck status:\n\n```bash\nvercel inspect \u003Cdeployment-url>\n```\n\n### Full Deploy Flow (no project ID — need to link)\n\nUse this when you have a token and team but no pre-existing project ID.\n\n#### Check project state first\n\n```bash\n# Does the project have a git remote?\ngit remote get-url origin 2>\u002Fdev\u002Fnull\n\n# Is it already linked to a Vercel project?\ncat .vercel\u002Fproject.json 2>\u002Fdev\u002Fnull || cat .vercel\u002Frepo.json 2>\u002Fdev\u002Fnull\n```\n\n#### Link the project\n\n**With git remote (preferred):**\n\n```bash\nvercel link --repo --scope \u003Cteam-slug> -y\n```\n\nReads the git remote and connects to the matching Vercel project. Creates `.vercel\u002Frepo.json`. More reliable than plain `vercel link`, which matches by directory name.\n\n**Without git remote:**\n\n```bash\nvercel link --scope \u003Cteam-slug> -y\n```\n\nCreates `.vercel\u002Fproject.json`.\n\n**Link to a specific project by name:**\n\n```bash\nvercel link --project \u003Cproject-name> --scope \u003Cteam-slug> -y\n```\n\nIf the project is already linked, check `orgId` in `.vercel\u002Fproject.json` or `.vercel\u002Frepo.json` to verify it matches the intended team.\n\n#### Deploy after linking\n\n**A) Git Push Deploy — has git remote (preferred)**\n\nGit pushes trigger automatic Vercel deployments.\n\n1. **Ask the user before pushing.** Never push without explicit approval.\n2. Commit and push:\n   ```bash\n   git add .\n   git commit -m \"deploy: \u003Cdescription of changes>\"\n   git push\n   ```\n3. Vercel builds automatically. Non-production branches get preview deployments.\n4. Retrieve the deployment URL:\n   ```bash\n   sleep 5\n   vercel ls --format json --scope \u003Cteam-slug>\n   ```\n   Find the latest entry in the `deployments` array.\n\n**B) CLI Deploy — no git remote**\n\n```bash\nvercel deploy --scope \u003Cteam-slug> -y --no-wait\n```\n\nCheck status:\n\n```bash\nvercel inspect \u003Cdeployment-url>\n```\n\n### Deploying from a Remote Repository (code not cloned locally)\n\n1. Clone the repository:\n   ```bash\n   git clone \u003Crepo-url>\n   cd \u003Crepo-name>\n   ```\n2. Link to Vercel:\n   ```bash\n   vercel link --repo --scope \u003Cteam-slug> -y\n   ```\n3. Deploy via git push (if you have push access) or CLI deploy.\n\n### About `.vercel\u002F` Directory\n\nA linked project has either:\n- `.vercel\u002Fproject.json` — from `vercel link`. Contains `projectId` and `orgId`.\n- `.vercel\u002Frepo.json` — from `vercel link --repo`. Contains `orgId`, `remoteName`, and a `projects` map.\n\nNot needed when `VERCEL_ORG_ID` + `VERCEL_PROJECT_ID` are both set in the environment.\n\n**Do NOT** run `vercel project inspect` or `vercel link` in an unlinked directory to detect state — they will interactively prompt or silently link as a side-effect. `vercel ls` is safe (in an unlinked directory it defaults to showing all deployments for the scope). `vercel whoami` is safe anywhere.\n\n## Managing Environment Variables\n\n```bash\n# Set for all environments\necho \"value\" | vercel env add VAR_NAME --scope \u003Cteam-slug>\n\n# Set for a specific environment (production, preview, development)\necho \"value\" | vercel env add VAR_NAME production --scope \u003Cteam-slug>\n\n# List environment variables\nvercel env ls --scope \u003Cteam-slug>\n\n# Pull env vars to local .env.local file\nvercel env pull --scope \u003Cteam-slug>\n\n# Remove a variable\nvercel env rm VAR_NAME --scope \u003Cteam-slug> -y\n```\n\n## Inspecting Deployments\n\n```bash\n# List recent deployments\nvercel ls --format json --scope \u003Cteam-slug>\n\n# Inspect a specific deployment\nvercel inspect \u003Cdeployment-url>\n\n# View build logs (requires Vercel CLI v35+)\nvercel inspect \u003Cdeployment-url> --logs\n\n# View runtime request logs (follows live by default; add --no-follow for a one-shot snapshot)\nvercel logs \u003Cdeployment-url>\n```\n\n## Managing Domains\n\n```bash\n# List domains\nvercel domains ls --scope \u003Cteam-slug>\n\n# Add a domain to the project — linked or env-linked directory (1 arg)\nvercel domains add \u003Cdomain> --scope \u003Cteam-slug>\n\n# Add a domain — unlinked directory (requires \u003Cproject> positional)\nvercel domains add \u003Cdomain> \u003Cproject> --scope \u003Cteam-slug>\n```\n\n## Stripe Projects Plan Changes\n\nIf this project is managed by Stripe Projects. **Ask the user before running any paid or destructive plan change** — upgrades bill a real card, downgrades remove seats.\n\nFirst run `stripe projects status --json` to confirm the Vercel resource's local name. The examples below assume the default (`vercel-plan`); substitute the actual name if it was renamed at `stripe projects add` time.\n\n- **Upgrade to Pro:** `stripe projects add vercel\u002Fpro` (or `stripe projects upgrade vercel-plan pro`)\n- **Downgrade to Hobby:** `stripe projects downgrade vercel-plan hobby`\n\n### What Pro gives you\n\n- $20\u002Fmonth platform fee, includes $20\u002Fmonth of usage credit.\n- Turbo build machines (30 vCPUs, 60 GB memory) by default for new projects — significantly faster builds than Hobby.\n- 1 deploying seat + unlimited free Viewer seats (read-only collaborators, preview comments).\n- Higher included allocations (1 TB Fast Data Transfer, 10M Edge Requests per month).\n- Paid add-ons available: SAML SSO, HIPAA BAA, Flags Explorer, Observability Plus, Speed Insights, Web Analytics Plus.\n\nFull details: https:\u002F\u002Fvercel.com\u002Fdocs\u002Fplans\u002Fpro-plan\n\n## Working Agreement\n\n- **Never pass `VERCEL_TOKEN` as a `--token` flag.** Export it as an environment variable and let the CLI read it natively.\n- **Check the environment for tokens before asking the user.** Look in the current env and `.env` files first.\n- **Default to preview deployments.** Only deploy to production when explicitly asked.\n- **Ask before pushing to git.** Never push commits without the user's approval.\n- **Do not modify `.vercel\u002F` files directly.** The CLI manages this directory. Reading them (e.g. to verify `orgId`) is fine.\n- **Do not curl\u002Ffetch deployed URLs to verify.** Just return the link to the user.\n- **Use `--format json`** when structured output will help with follow-up steps.\n- **Use `-y`** on commands that prompt for confirmation to avoid interactive blocking.\n\n## Troubleshooting\n\n### Token not found\n\nCheck the environment and any `.env` files present:\n\n```bash\nprintenv | grep -i vercel\ngrep -i vercel .env 2>\u002Fdev\u002Fnull\n```\n\n### Authentication error\n\nIf the CLI fails with `Authentication required`:\n- The token may be expired or invalid.\n- Verify: `vercel whoami` (uses `VERCEL_TOKEN` from environment).\n- Ask the user for a fresh token.\n\n### Wrong team\n\nVerify the scope is correct:\n\n```bash\nvercel whoami --scope \u003Cteam-slug>\n```\n\n### Build failure\n\nCheck the build logs:\n\n```bash\nvercel inspect \u003Cdeployment-url> --logs\n```\n\nCommon causes:\n- Missing dependencies — ensure `package.json` is complete and committed.\n- Missing environment variables — add with `vercel env add`.\n- Framework misconfiguration — check `vercel.json`. Vercel auto-detects frameworks (Next.js, Remix, Vite, etc.) from `package.json`; override with `vercel.json` if detection is wrong.\n\n### CLI not installed\n\n```bash\nnpm install -g vercel\n```\n","# Vercel CLI with Tokens\n\nDeploy and manage projects on Vercel using the CLI with token-based authentication, without relying on `vercel login`.\n\n## Step 1: Locate the Vercel Token\n\nBefore running any Vercel CLI commands, identify where the token is coming from. Work through these scenarios in order:\n\n### A) `VERCEL_TOKEN` is already set in the environment\n\n```bash\nprintenv VERCEL_TOKEN\n```\n\nIf this returns a value, you're ready. Skip to Step 2.\n\n### B) Token is in a `.env` file under `VERCEL_TOKEN`\n\n```bash\ngrep '^VERCEL_TOKEN=' .env 2>\u002Fdev\u002Fnull\n```\n\nIf found, export it:\n\n```bash\nexport VERCEL_TOKEN=$(grep '^VERCEL_TOKEN=' .env | cut -d= -f2-)\n```\n\n### C) Token is in a `.env` file under a different name\n\nLook for any variable that looks like a Vercel token (Vercel tokens typically start with `vca_`):\n\n```bash\ngrep -i 'vercel' .env 2>\u002Fdev\u002Fnull\n```\n\nInspect the output to identify which variable holds the token, then export it as `VERCEL_TOKEN`:\n\n```bash\nexport VERCEL_TOKEN=$(grep '^\u003CVARIABLE_NAME>=' .env | cut -d= -f2-)\n```\n\n### D) No token found — ask the user\n\nIf none of the above yield a token, ask the user to provide one. They can create a Vercel access token at vercel.com\u002Faccount\u002Ftokens.\n\n---\n\n**Important:** Once `VERCEL_TOKEN` is exported as an environment variable, the Vercel CLI reads it natively — **do not pass it as a `--token` flag**. Putting secrets in command-line arguments exposes them in shell history and process listings.\n\n```bash\n# Bad — token visible in shell history and process listings\nvercel deploy --token \"vca_abc123\"\n\n# Good — CLI reads VERCEL_TOKEN from the environment\nexport VERCEL_TOKEN=\"vca_abc123\"\nvercel deploy\n```\n\n## Step 2: Locate the Project and Team\n\nSimilarly, check for the project ID and team scope. These let the CLI target the right project without needing `vercel link`.\n\n```bash\n# Check environment\nprintenv VERCEL_PROJECT_ID\nprintenv VERCEL_ORG_ID\n\n# Or check .env\ngrep -i 'vercel' .env 2>\u002Fdev\u002Fnull\n```\n\n**If you have a project URL** (e.g. `https:\u002F\u002Fvercel.com\u002Fmy-team\u002Fmy-project`), extract the team slug:\n\n```bash\n# e.g. \"my-team\" from \"https:\u002F\u002Fvercel.com\u002Fmy-team\u002Fmy-project\"\necho \"$PROJECT_URL\" | sed 's|https:\u002F\u002Fvercel.com\u002F||' | cut -d\u002F -f1\n```\n\n**If you have both `VERCEL_ORG_ID` and `VERCEL_PROJECT_ID` in your environment**, export them — the CLI will use these automatically and skip any `.vercel\u002F` directory:\n\n```bash\nexport VERCEL_ORG_ID=\"\u003Corg-id>\"\nexport VERCEL_PROJECT_ID=\"\u003Cproject-id>\"\n```\n\nNote: `VERCEL_ORG_ID` and `VERCEL_PROJECT_ID` must be set together — setting only one causes an error.\n\n## CLI Setup\n\nEnsure the Vercel CLI is installed and up to date:\n\n```bash\nnpm install -g vercel\nvercel --version\n```\n\n## Deploying a Project\n\nAlways deploy as **preview** unless the user explicitly requests production. Choose a method based on what you have available.\n\n### Quick Deploy (have project ID — no linking needed)\n\nWhen `VERCEL_TOKEN` and `VERCEL_PROJECT_ID` are set in the environment, deploy directly:\n\n```bash\nvercel deploy -y --no-wait\n```\n\nWith a team scope (either via `VERCEL_ORG_ID` or `--scope`):\n\n```bash\nvercel deploy --scope \u003Cteam-slug> -y --no-wait\n```\n\nProduction (only when explicitly requested):\n\n```bash\nvercel deploy --prod --scope \u003Cteam-slug> -y --no-wait\n```\n\nCheck status:\n\n```bash\nvercel inspect \u003Cdeployment-url>\n```\n\n### Full Deploy Flow (no project ID — need to link)\n\nUse this when you have a token and team but no pre-existing project ID.\n\n#### Check project state first\n\n```bash\n# Does the project have a git remote?\ngit remote get-url origin 2>\u002Fdev\u002Fnull\n\n# Is it already linked to a Vercel project?\ncat .vercel\u002Fproject.json 2>\u002Fdev\u002Fnull || cat .vercel\u002Frepo.json 2>\u002Fdev\u002Fnull\n```\n\n#### Link the project\n\n**With git remote (preferred):**\n\n```bash\nvercel link --repo --scope \u003Cteam-slug> -y\n```\n\nReads the git remote and connects to the matching Vercel project. Creates `.vercel\u002Frepo.json`. More reliable than plain `vercel link`, which matches by directory name.\n\n**Without git remote:**\n\n```bash\nvercel link --scope \u003Cteam-slug> -y\n```\n\nCreates `.vercel\u002Fproject.json`.\n\n**Link to a specific project by name:**\n\n```bash\nvercel link --project \u003Cproject-name> --scope \u003Cteam-slug> -y\n```\n\nIf the project is already linked, check `orgId` in `.vercel\u002Fproject.json` or `.vercel\u002Frepo.json` to verify it matches the intended team.\n\n#### Deploy after linking\n\n**A) Git Push Deploy — has git remote (preferred)**\n\nGit pushes trigger automatic Vercel deployments.\n\n1. **Ask the user before pushing.** Never push without explicit approval.\n2. Commit and push:\n   ```bash\n   git add .\n   git commit -m \"deploy: \u003Cdescription of changes>\"\n   git push\n   ```\n3. Vercel builds automatically. Non-production branches get preview deployments.\n4. Retrieve the deployment URL:\n   ```bash\n   sleep 5\n   vercel ls --format json --scope \u003Cteam-slug>\n   ```\n   Find the latest entry in the `deployments` array.\n\n**B) CLI Deploy — no git remote**\n\n```bash\nvercel deploy --scope \u003Cteam-slug> -y --no-wait\n```\n\nCheck status:\n\n```bash\nvercel inspect \u003Cdeployment-url>\n```\n\n### Deploying from a Remote Repository (code not cloned locally)\n\n1. Clone the repository:\n   ```bash\n   git clone \u003Crepo-url>\n   cd \u003Crepo-name>\n   ```\n2. Link to Vercel:\n   ```bash\n   vercel link --repo --scope \u003Cteam-slug> -y\n   ```\n3. Deploy via git push (if you have push access) or CLI deploy.\n\n### About `.vercel\u002F` Directory\n\nA linked project has either:\n- `.vercel\u002Fproject.json` — from `vercel link`. Contains `projectId` and `orgId`.\n- `.vercel\u002Frepo.json` — from `vercel link --repo`. Contains `orgId`, `remoteName`, and a `projects` map.\n\nNot needed when `VERCEL_ORG_ID` + `VERCEL_PROJECT_ID` are both set in the environment.\n\n**Do NOT** run `vercel project inspect` or `vercel link` in an unlinked directory to detect state — they will interactively prompt or silently link as a side-effect. `vercel ls` is safe (in an unlinked directory it defaults to showing all deployments for the scope). `vercel whoami` is safe anywhere.\n\n## Managing Environment Variables\n\n```bash\n# Set for all environments\necho \"value\" | vercel env add VAR_NAME --scope \u003Cteam-slug>\n\n# Set for a specific environment (production, preview, development)\necho \"value\" | vercel env add VAR_NAME production --scope \u003Cteam-slug>\n\n# List environment variables\nvercel env ls --scope \u003Cteam-slug>\n\n# Pull env vars to local .env.local file\nvercel env pull --scope \u003Cteam-slug>\n\n# Remove a variable\nvercel env rm VAR_NAME --scope \u003Cteam-slug> -y\n```\n\n## Inspecting Deployments\n\n```bash\n# List recent deployments\nvercel ls --format json --scope \u003Cteam-slug>\n\n# Inspect a specific deployment\nvercel inspect \u003Cdeployment-url>\n\n# View build logs (requires Vercel CLI v35+)\nvercel inspect \u003Cdeployment-url> --logs\n\n# View runtime request logs (follows live by default; add --no-follow for a one-shot snapshot)\nvercel logs \u003Cdeployment-url>\n```\n\n## Managing Domains\n\n```bash\n# List domains\nvercel domains ls --scope \u003Cteam-slug>\n\n# Add a domain to the project — linked or env-linked directory (1 arg)\nvercel domains add \u003Cdomain> --scope \u003Cteam-slug>\n\n# Add a domain — unlinked directory (requires \u003Cproject> positional)\nvercel domains add \u003Cdomain> \u003Cproject> --scope \u003Cteam-slug>\n```\n\n## Stripe Projects Plan Changes\n\nIf this project is managed by Stripe Projects. **Ask the user before running any paid or destructive plan change** — upgrades bill a real card, downgrades remove seats.\n\nFirst run `stripe projects status --json` to confirm the Vercel resource's local name. The examples below assume the default (`vercel-plan`); substitute the actual name if it was renamed at `stripe projects add` time.\n\n- **Upgrade to Pro:** `stripe projects add vercel\u002Fpro` (or `stripe projects upgrade vercel-plan pro`)\n- **Downgrade to Hobby:** `stripe projects downgrade vercel-plan hobby`\n\n### What Pro gives you\n\n- $20\u002Fmonth platform fee, includes $20\u002Fmonth of usage credit.\n- Turbo build machines (30 vCPUs, 60 GB memory) by default for new projects — significantly faster builds than Hobby.\n- 1 deploying seat + unlimited free Viewer seats (read-only collaborators, preview comments).\n- Higher included allocations (1 TB Fast Data Transfer, 10M Edge Requests per month).\n- Paid add-ons available: SAML SSO, HIPAA BAA, Flags Explorer, Observability Plus, Speed Insights, Web Analytics Plus.\n\nFull details: https:\u002F\u002Fvercel.com\u002Fdocs\u002Fplans\u002Fpro-plan\n\n## Working Agreement\n\n- **Never pass `VERCEL_TOKEN` as a `--token` flag.** Export it as an environment variable and let the CLI read it natively.\n- **Check the environment for tokens before asking the user.** Look in the current env and `.env` files first.\n- **Default to preview deployments.** Only deploy to production when explicitly asked.\n- **Ask before pushing to git.** Never push commits without the user's approval.\n- **Do not modify `.vercel\u002F` files directly.** The CLI manages this directory. Reading them (e.g. to verify `orgId`) is fine.\n- **Do not curl\u002Ffetch deployed URLs to verify.** Just return the link to the user.\n- **Use `--format json`** when structured output will help with follow-up steps.\n- **Use `-y`** on commands that prompt for confirmation to avoid interactive blocking.\n\n## Troubleshooting\n\n### Token not found\n\nCheck the environment and any `.env` files present:\n\n```bash\nprintenv | grep -i vercel\ngrep -i vercel .env 2>\u002Fdev\u002Fnull\n```\n\n### Authentication error\n\nIf the CLI fails with `Authentication required`:\n- The token may be expired or invalid.\n- Verify: `vercel whoami` (uses `VERCEL_TOKEN` from environment).\n- Ask the user for a fresh token.\n\n### Wrong team\n\nVerify the scope is correct:\n\n```bash\nvercel whoami --scope \u003Cteam-slug>\n```\n\n### Build failure\n\nCheck the build logs:\n\n```bash\nvercel inspect \u003Cdeployment-url> --logs\n```\n\nCommon causes:\n- Missing dependencies — ensure `package.json` is complete and committed.\n- Missing environment variables — add with `vercel env add`.\n- Framework misconfiguration — check `vercel.json`. Vercel auto-detects frameworks (Next.js, Remix, Vite, etc.) from `package.json`; override with `vercel.json` if detection is wrong.\n\n### CLI not installed\n\n```bash\nnpm install -g vercel\n```\n",{"name":5,"metadata":24,"description":7},{"author":25,"version":26},"vercel","1.0.0","main","f31e1d2df163b90a48e30d0a3df67285f6641418","skills\u002Fmirrors-vercel-agent-skills\u002Fvercel-agent-vercel-cli-with-tokens",1,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills","https:\u002F\u002Fgithub.com\u002FTheAngryPit","www.vitorcepedalopes.com","Creative Director | Executive Producer | Storyteller | Narrative Worlds & Creative Production Systems\r\nFounder @TheHive-Mind ","2026-11-14 21:48:38",{"source":8,"skillName":5,"commands":37,"prompt":47,"zipAvailable":48},[38,41,44],{"tool":39,"command":40},"npx","npx skills add TheAngryPit\u002FTheAngrySkills --skill vercel-agent-vercel-cli-with-tokens",{"tool":42,"command":43},"bunx","bunx skills add TheAngryPit\u002FTheAngrySkills --skill vercel-agent-vercel-cli-with-tokens",{"tool":45,"command":46},"pnpm","pnpm dlx skills add TheAngryPit\u002FTheAngrySkills --skill vercel-agent-vercel-cli-with-tokens","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-vercel-agent-skills\u002Fvercel-agent-vercel-cli-with-tokens\u002FSKILL.md",true,[50],{"path":51,"resourceType":52,"resourceTypeDesc":53,"sizeBytes":54,"sourceHtmlUrl":55},"MIRROR.md","REFERENCE","参考文档",611,"https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fskills\u002Fmirrors-vercel-agent-skills\u002Fvercel-agent-vercel-cli-with-tokens\u002FMIRROR.md",[57,64,71,78,85,92],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":19},"01M782GJ4CTPNKZN0WXTASXXZ4","X MCP guide","ALWAYS read this before using any X tool (the X plugin, any X MCP, or Grok Bot's built-in public X reads) and again on any X error. X tools are included in Grok Bot at no cost: never estimate costs, check credits, or tell the user to buy credits. tools=0 \u002F user-X-* not found is a setup failure, not a paywall. Covers Spaces, communities, and Lists (reads and list writes), X Chat (XChat, inbox, DMs, unread, message requests, Chat PIN, juicebox, xchat_lite: clone xchat-grokbot-helper yourself and decrypt locally), scheduled X calls (schedule_call, list_scheduled_calls and the other call tools), and livestreams (stream sources, broadcasts, scheduled broadcasts, broadcast chat, moderators, mutes). Chat, call, livestream, Spaces, or Lists tools missing while other X tools work: reconnect the X plugin.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fx\u002Fskills\u002Fx-api-mcp-guide\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":68,"categories":69,"keywords":70,"publishedAt":19},"01M782GBW77901ESC9PD3XAM6V","X Money guide","Read this before the first X Money action in a session and again on any X Money error, refusal, or missing capability. Covers the approval rule for every action that moves money (always ask, every time, no exceptions), how the connection works (connection code plus passkey in the X app), how to guide the user through connect, reconnect, and revoke at x.com\u002Fi\u002Fmoney\u002Fsettings\u002Fconnections, and what each failure message means.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fx-money\u002Fskills\u002Fx-money-guide\u002FSKILL.md",[],[],{"skillNo":72,"name":73,"nameZh":6,"description":74,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":75,"categories":76,"keywords":77,"publishedAt":19},"01M782G7CMYD2JSVT3RX81QRB8","google-slides","Build and edit Google Slides through the google-slides MCP tools - slides, grids of cards and columns, text boxes, shapes, images, tables, styling, layout inspection, and per-slide PNG rendering. Use when creating a deck, laying out slide elements, matching a template, or verifying how a slide looks.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-slides\u002Fskills\u002Fgoogle-slides\u002FSKILL.md",[],[],{"skillNo":79,"name":80,"nameZh":6,"description":81,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":82,"categories":83,"keywords":84,"publishedAt":19},"01M782G4DDAJ4SMGJEF13HTX69","google-sheets","Build and edit Google Sheets with the google-sheets tools - values, formatting, charts, conditional formatting, structure, validation, named and protected ranges. Use when creating a spreadsheet or dashboard, formatting cells, adding or fixing charts, or reorganizing tabs and rows.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-sheets\u002Fskills\u002Fgoogle-sheets\u002FSKILL.md",[],[],{"skillNo":86,"name":87,"nameZh":6,"description":88,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":89,"categories":90,"keywords":91,"publishedAt":19},"01M782G1F8QNMNKRSY6M3Y0QG6","google-drive","Work with Google Drive through its MCP tools - search, read, create, organize, share, comment, and export files. Use when creating files in specific folders, moving or renaming, converting Markdown\u002FCSV into Docs\u002FSheets, managing comments, or exporting a rendered PDF.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-drive\u002Fskills\u002Fgoogle-drive\u002FSKILL.md",[],[],{"skillNo":93,"name":94,"nameZh":6,"description":95,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":96,"categories":97,"keywords":98,"publishedAt":19},"01M782FYVJ5XTP2R0B446RRYTX","google-docs","Author and edit Google Docs with the google-docs tools - structured writing, character and paragraph styling, lists, tables, images, headers\u002Ffooters. Use when creating a formatted document, editing document content, or applying styles.","https:\u002F\u002Fgithub.com\u002FTheAngryPit\u002FTheAngrySkills\u002Fblob\u002Fmain\u002Fsources\u002Fcursor-plugins\u002Fupstream-tree\u002Fthird_party\u002Fgoogle-docs\u002Fskills\u002Fgoogle-docs\u002FSKILL.md",[],[]]