Vercel CLI with Tokens

by zhukunpenglinyutong

Vercel CLI with Tokens is a DevOps skill for Claude Code, published by zhukunpenglinyutong in desktop-cc-gui.

4K stars356 forkson zhukunpenglinyutong/desktop-cc-guiAdded 2026/08/20Repository updated 2026/08/20

View source on GitHub Download repo ZIP

ai-codingclaude-codecodexdeepseek-harnessdesktop-appdshtaurivibe-coding

Install in seconds

Install Vercel CLI with Tokens

Copy Vercel CLI with Tokens into your Claude Code skills folder. Run the command in your terminal, or review the source on GitHub before installing.

terminal

npx degit https://github.com/zhukunpenglinyutong/desktop-cc-gui/tree/main/.agents/skills/vercel-cli-with-tokens ~/.claude/skills/vercel-cli-with-tokens

Requires Node.js. Downloads this skill only — not the rest of the repository — into your Claude Code skills folder.

Without Node.js

git clone https://github.com/zhukunpenglinyutong/desktop-cc-gui.git

Clones the whole repository, then copy the skill’s own directory into your skills folder yourself.

In this catalog

Source file: .agents/skills/vercel-cli-with-tokens/SKILL.md in zhukunpenglinyutong/desktop-cc-gui
Installs to: ~/.claude/skills/vercel-cli-with-tokens
Collection: One of 13 skills cataloged from this repository
Category: DevOps — 798 skills

What Vercel CLI with Tokens does

Vercel CLI with Tokens deploys and manages projects on Vercel using token-based authentication without interactive login. Use when setting up Vercel CLI with access tokens, deploying previews, or managing environment variables.

Vercel CLI with Tokens is cataloged under DevOps on DirSkills. Vercel CLI with Tokens comes from a repository tagged ai-coding, claude-code, codex, deepseek-harness and desktop-app.

Documentation

README

Excerpt

Vercel CLI with Tokens

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

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:

A) `VERCEL_TOKEN` is already set in the environment

printenv VERCEL_TOKEN

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

B) Token is in a `.env` file under `VERCEL_TOKEN`

grep '^VERCEL_TOKEN=' .env 2>/dev/null

If found, export it:

export VERCEL_TOKEN=$(grep '^VERCEL_TOKEN=' .env | cut -d= -f2-)

C) Token is in a `.env` file under a different name

This is the opening of the README. Read the full README on GitHub.

Frequently asked about Vercel CLI with Tokens

What else does zhukunpenglinyutong publish alongside Vercel CLI with Tokens?
Vercel CLI with Tokens is one of 13 skills that DirSkills catalogs from zhukunpenglinyutong/desktop-cc-gui, the repository it ships in. Its siblings there include Caveman, Coss UI and Deploy to Vercel. Each one is a separate skill with its own page in this directory, installs the same way Vercel CLI with Tokens does, and is maintained by zhukunpenglinyutong in that same repository. The rest of the collection is listed on the zhukunpenglinyutong/desktop-cc-gui page.
How does Vercel CLI with Tokens compare to other DevOps skills?
Vercel CLI with Tokens ranks #182 by stars among the 798 DevOps skills in this catalog. The most-starred ones next to it are Backend Patterns, API Connector Builder and Migration. DirSkills ranks by the star count of the repository each skill ships in, so that order reflects how popular those repositories are rather than any review of Vercel CLI with Tokens against them. Open each page to compare what they document and how they install.