C✳CODEZ.WIN
🌐 English

Localized reading guide

vercel-cli-with-tokensPurpose, usage and source

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

Source retrieved:

Source repository
vercel-labs/agent-skills
SKILL.md
skills/vercel-cli-with-tokens/SKILL.md
Repository stars
33,269
Repository updated
2026-10-29
Categories
Automation
Last collected

License: Unspecified

Source SKILL.md

Workflow excerpts are reading aids, not executable instructions from Codez. No third-party Skill was run to produce this page.

The purpose and workflow passages below are upstream material, organized and translated for reading. They are distinct from the separately labeled Codez editorial analysis.

What this Skill does

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

How the upstream workflow works

Step 1: Locate the Vercel Token

Before running any Vercel CLI commands, identify where the token is coming from. Work through these scenarios in order:

Upstream passage · L13 ↗

Step 2: Locate the Project and Team

Similarly, check for the project ID and team scope. These let the CLI target the right project without needing vercel link. If you have a project URL (e.g. https://vercel.com/my-team/my-project), extract the team slug: 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/ directory: Note: VERCEL_ORG_ID and VERCEL_PROJECT_ID must be set together — setting only one causes an error.

Upstream passage · L68 ↗

Vercel CLI with Tokens

Deploy and manage projects on Vercel using the CLI with token-based authentication, without relying on vercel login.

Upstream passage · L9 ↗

Requirements and setup

A) VERCEL_TOKEN is already set in the environment

If this returns a value, you're ready. Skip to Step 2.

Upstream passage · L17 ↗

CLI Setup

Ensure the Vercel CLI is installed and up to date:

Upstream passage · L97 ↗
Upstream passage · bash ↗
printenv VERCEL_TOKEN

Limits and quality checks

No separate limits passage was selected from this file. This does not mean the Skill is safe for every input or environment. Review the complete source and validate your own result.

Start with a safe trial

  1. Check the supported host and the repository installation instructions. Keep the Skill directory and its referenced scripts, assets and documentation together; SKILL.md alone may omit dependencies.
  2. Give the agent your real input, desired output and acceptance criteria. Invocation syntax and available tools depend on the host; this site does not assume a universal install command.
  3. Try the source workflow in a disposable project or on a copy. Review operations that change files, remote services or billable resources before allowing them.
  4. Validate the output against the source quality checks and your own requirements. A successful trigger or a high repository Star count does not establish a correct result.

Skill format and directory specification ↗

Read further in the source

Translation and scope

This reading guide selects passages from the pinned upstream SKILL.md. Translation is assisted. It is not a complete manual or a claim of tested compatibility. Read the original and its referenced files before use.

This introduction refers to the pinned version below; current repository activity and collection time are shown separately.

Source retrieved
Source commit
1a2c79d4e6c4a2283dc2c614b6538cbe1ed5ca62
Source SHA-256
c06bea99e75eab07fde4fae26069baa002f82f39b53f07981704c2901551dd4c
Back to the full Skill catalog