[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M78FTX1ZW4RGATPWK10GFV2Y":3,"skill-same:01M78FTX1ZW4RGATPWK10GFV2Y":48},{"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":14,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":33,"install":34,"resources":47},"01M78FTX1ZW4RGATPWK10GFV2Y","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\".","princepatel04477-web\u002Ftrivoxa-group","princepatel04477-web","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F227740714?v=4","01M788ZAJ2KECD5KXVP55PZXKS","Prince Patel","01M788ZAJTCN8YSD737MRSKC5Q",0,"MIT","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fvercel-cli-with-tokens\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: 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\\\".\"\nrisk: safe\nsource: \"https:\u002F\u002Fgithub.com\u002Fvercel-labs\u002Fagent-skills\"\ndate_added: \"2026-06-02\"\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## When to Use\n- Use this skill when the task matches this description: 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\".\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\n[ -n \"${VERCEL_TOKEN:-}\" ] && printf 'VERCEL_TOKEN is set\\n'\n```\n\nIf this reports a configured token, you're ready. Skip to Step 2.\n\n### B) Token is in a `.env` file under `VERCEL_TOKEN`\n\n```bash\ngrep -q '^VERCEL_TOKEN=' .env 2>\u002Fdev\u002Fnull && printf 'VERCEL_TOKEN is present in .env\\n'\n```\n\nIf found, export it:\n\n```bash\nVERCEL_TOKEN=\"$(sed -n 's\u002F^VERCEL_TOKEN=\u002F\u002Fp' .env | tail -n 1)\"\nexport VERCEL_TOKEN\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 -Eio '^[A-Z0-9_]*VERCEL[A-Z0-9_]*(?==)' .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\nvercel_var=\"\u003CVARIABLE_NAME>\"\nVERCEL_TOKEN=\"$(sed -n \"s\u002F^${vercel_var}=\u002F\u002Fp\" .env | tail -n 1)\"\nexport VERCEL_TOKEN\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\n[ -n \"${VERCEL_TOKEN:-}\" ] || { echo \"Set VERCEL_TOKEN first\" >&2; exit 1; }\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\n[ -n \"${VERCEL_PROJECT_ID:-}\" ] && printf 'VERCEL_PROJECT_ID is set\\n'\n[ -n \"${VERCEL_ORG_ID:-}\" ] && printf 'VERCEL_ORG_ID is set\\n'\n\n# Or check .env\ngrep -Eio '^[A-Z0-9_]*VERCEL[A-Z0-9_]*(?==)' .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\nenv | grep -Eio '^[A-Z0-9_]*VERCEL[A-Z0-9_]*(?==)'\ngrep -Eio '^[A-Z0-9_]*VERCEL[A-Z0-9_]*(?==)' .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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\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## When to Use\n- Use this skill when the task matches this description: 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\".\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\n[ -n \"${VERCEL_TOKEN:-}\" ] && printf 'VERCEL_TOKEN is set\\n'\n```\n\nIf this reports a configured token, you're ready. Skip to Step 2.\n\n### B) Token is in a `.env` file under `VERCEL_TOKEN`\n\n```bash\ngrep -q '^VERCEL_TOKEN=' .env 2>\u002Fdev\u002Fnull && printf 'VERCEL_TOKEN is present in .env\\n'\n```\n\nIf found, export it:\n\n```bash\nVERCEL_TOKEN=\"$(sed -n 's\u002F^VERCEL_TOKEN=\u002F\u002Fp' .env | tail -n 1)\"\nexport VERCEL_TOKEN\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 -Eio '^[A-Z0-9_]*VERCEL[A-Z0-9_]*(?==)' .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\nvercel_var=\"\u003CVARIABLE_NAME>\"\nVERCEL_TOKEN=\"$(sed -n \"s\u002F^${vercel_var}=\u002F\u002Fp\" .env | tail -n 1)\"\nexport VERCEL_TOKEN\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\n[ -n \"${VERCEL_TOKEN:-}\" ] || { echo \"Set VERCEL_TOKEN first\" >&2; exit 1; }\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\n[ -n \"${VERCEL_PROJECT_ID:-}\" ] && printf 'VERCEL_PROJECT_ID is set\\n'\n[ -n \"${VERCEL_ORG_ID:-}\" ] && printf 'VERCEL_ORG_ID is set\\n'\n\n# Or check .env\ngrep -Eio '^[A-Z0-9_]*VERCEL[A-Z0-9_]*(?==)' .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\nenv | grep -Eio '^[A-Z0-9_]*VERCEL[A-Z0-9_]*(?==)'\ngrep -Eio '^[A-Z0-9_]*VERCEL[A-Z0-9_]*(?==)' .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\n## Limitations\n- Use this skill only when the task clearly matches the scope described above.\n- Do not treat the output as a substitute for environment-specific validation, testing, or expert review.\n- Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing.\n",{"name":5,"risk":24,"source":25,"date_added":26,"description":7},"safe","https:\u002F\u002Fgithub.com\u002Fvercel-labs\u002Fagent-skills","2026-06-02","master","877653a671c51fae6476bd9f0d34ee6c408d68b9",".github\u002Fskills\u002Fvercel-cli-with-tokens","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group","https:\u002F\u002Ftrivoxa-group.vercel.app","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web","2026-08-01 17:29:31",{"source":8,"skillName":5,"commands":35,"prompt":45,"zipAvailable":46},[36,39,42],{"tool":37,"command":38},"npx","npx skills add princepatel04477-web\u002Ftrivoxa-group --skill vercel-cli-with-tokens",{"tool":40,"command":41},"bunx","bunx skills add princepatel04477-web\u002Ftrivoxa-group --skill vercel-cli-with-tokens",{"tool":43,"command":44},"pnpm","pnpm dlx skills add princepatel04477-web\u002Ftrivoxa-group --skill vercel-cli-with-tokens","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fvercel-cli-with-tokens\u002FSKILL.md",true,[],[49,56,63,70,77,84],{"skillNo":50,"name":51,"nameZh":6,"description":52,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":53,"categories":54,"keywords":55,"publishedAt":19},"01M78G4Z5RFJ72G536XYPC77PG","zustand-store-ts","Create Zustand stores following established patterns with proper TypeScript types and middleware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzustand-store-ts\u002FSKILL.md",[],[],{"skillNo":57,"name":58,"nameZh":6,"description":59,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":60,"categories":61,"keywords":62,"publishedAt":19},"01M78G4WQMHRST36KDP7AV3NR3","zoom-automation","Automate Zoom meeting creation, management, recordings, webinars, and participant tracking via Rube MCP (Composio). Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoom-automation\u002FSKILL.md",[],[],{"skillNo":64,"name":65,"nameZh":6,"description":66,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":67,"categories":68,"keywords":69,"publishedAt":19},"01M78G4T37F4SPS7M4KT0A8JJB","zoho-crm-automation","Automate Zoho CRM tasks via Rube MCP (Composio): create\u002Fupdate records, search contacts, manage leads, and convert leads. Always search tools first for current schemas.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzoho-crm-automation\u002FSKILL.md",[],[],{"skillNo":71,"name":72,"nameZh":6,"description":73,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":74,"categories":75,"keywords":76,"publishedAt":19},"01M78G4QAJMF71KD1G38MNDQYK","zod-validation-expert","Expert in Zod — TypeScript-first schema validation. Covers parsing, custom errors, refinements, type inference, and integration with React Hook Form, Next.js, and tRPC.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzod-validation-expert\u002FSKILL.md",[],[],{"skillNo":78,"name":79,"nameZh":6,"description":80,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":81,"categories":82,"keywords":83,"publishedAt":19},"01M78G4MS3WE96MH5P561KFY95","zipai-optimizer","Adaptive token optimizer: intelligent filtering, surgical output, ambiguity-first, context-window-aware, VCS-aware, MCP-aware.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzipai-optimizer\u002FSKILL.md",[],[],{"skillNo":85,"name":86,"nameZh":6,"description":87,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":88,"categories":89,"keywords":90,"publishedAt":19},"01M78G4GZ0T47C6929V9CVH1AK","zeroize-audit","Detects missing zeroization of sensitive data in source code and identifies zeroization removed by compiler optimizations, with assembly-level analysis, and control-flow verification. Use for auditing C\u002FC++\u002FRust code handling secrets, keys, passwords, or other sensitive data.","https:\u002F\u002Fgithub.com\u002Fprincepatel04477-web\u002Ftrivoxa-group\u002Fblob\u002Fmaster\u002F.github\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[]]