[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M75KFD3N7D8RNGF7MB906JVF":3,"skill-same:01M75KFD3N7D8RNGF7MB906JVF":49},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":26,"commitSha":27,"skillDirectory":28,"forksCount":29,"repositoryHtmlUrl":30,"repositoryHomepageUrl":31,"ownerHtmlUrl":32,"ownerBlogUrl":33,"ownerDescription":6,"updatedAt":34,"install":35,"resources":48},"01M75KFD3N7D8RNGF7MB906JVF","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\".","agisota\u002Fold-one","agisota","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F121413592?v=4","01M75B4BRNT67EC1NDRT8QZEP2","01M75B4BS7QR9VP580MSCPTS3X",3,"MIT","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-cli-with-tokens\u002FSKILL.md",[],[],"2026-11-12 13:55:43",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\".\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":23,"description":7},{"author":24,"version":25},"vercel","1.0.0","main","f37de8f681f0c0ca0e0ebab6e5fddf764ca7553d","skills\u002Fvercel-cli-with-tokens",1,"https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one","https:\u002F\u002Fagisota.github.io\u002Fold-one\u002F","https:\u002F\u002Fgithub.com\u002Fagisota","pzd.world","2026-07-04 22:32:06",{"source":8,"skillName":5,"commands":36,"prompt":46,"zipAvailable":47},[37,40,43],{"tool":38,"command":39},"npx","npx skills add agisota\u002Fold-one --skill vercel-cli-with-tokens",{"tool":41,"command":42},"bunx","bunx skills add agisota\u002Fold-one --skill vercel-cli-with-tokens",{"tool":44,"command":45},"pnpm","pnpm dlx skills add agisota\u002Fold-one --skill vercel-cli-with-tokens","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fvercel-cli-with-tokens\u002FSKILL.md",true,[],[50,57,64,73,80,87],{"skillNo":51,"name":52,"nameZh":6,"description":53,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":54,"categories":55,"keywords":56,"publishedAt":18},"01M75KRGZWQWE9JDBS6RX42NWV","zoom-out","Tell the agent to zoom out and give broader context or a higher-level perspective. Use when you're unfamiliar with a section of code or need to understand how it fits into the bigger picture.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzoom-out\u002FSKILL.md",[],[],{"skillNo":58,"name":59,"nameZh":6,"description":60,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":61,"categories":62,"keywords":63,"publishedAt":18},"01M75KRCZHKE0ZYAQFFYHS0YNP","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\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fzeroize-audit\u002FSKILL.md",[],[],{"skillNo":65,"name":66,"nameZh":6,"description":67,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":68,"licenseFileUrl":69,"sourceHtmlUrl":70,"categories":71,"keywords":72,"publishedAt":18},"01M75KR94KYQ30DTE1P9WNDAE0","yeet","Use only when the user explicitly asks to stage, commit, push, and open a GitHub pull request in one flow using the GitHub CLI (`gh`).","Apache-2.0","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FLICENSE.txt","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyeet\u002FSKILL.md",[],[],{"skillNo":74,"name":75,"nameZh":6,"description":76,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":77,"categories":78,"keywords":79,"publishedAt":18},"01M75KR3H13YJ9QHMD49818FA1","yara-rule-authoring","Guides authoring of high-quality YARA-X detection rules for malware identification. Use when writing, reviewing, or optimizing YARA rules. Covers naming conventions, string selection, performance optimization, migration from legacy YARA, and false positive reduction. Triggers on: YARA, YARA-X, malware detection, threat hunting, IOC, signature, crx module, dex module.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fyara-rule-authoring\u002FSKILL.md",[],[],{"skillNo":81,"name":82,"nameZh":6,"description":83,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":84,"categories":85,"keywords":86,"publishedAt":18},"01M75KQMPY8A4Y8XTDD2DT0M9T","x-twitter-growth","X\u002FTwitter growth engine for building audience, crafting viral content, and analyzing engagement. Use when the user wants to grow on X\u002FTwitter, write tweets or threads, analyze their X profile, research competitors on X, plan a posting strategy, or optimize engagement. Complements social-content (generic multi-platform) with X-specific depth: algorithm mechanics, thread engineering, reply strategy, profile optimization, and competitive intelligence via web search.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-twitter-growth\u002FSKILL.md",[],[],{"skillNo":88,"name":89,"nameZh":6,"description":90,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":9,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":91,"categories":92,"keywords":93,"publishedAt":18},"01M75KQHNZ0ANZNJGZY6M8MDAK","x-api","X\u002FTwitter API integration for posting tweets, threads, reading timelines, search, and analytics. Covers OAuth auth patterns, rate limits, and platform-native content posting. Use when the user wants to interact with X programmatically.","https:\u002F\u002Fgithub.com\u002Fagisota\u002Fold-one\u002Fblob\u002Fmain\u002Fskills\u002Fx-api\u002FSKILL.md",[],[]]