Vercel

Deploy and manage Vercel projects, including linking repositories, env vars, and domains.

Security Scan

The instructions match the stated purpose (Vercel deploy/manage); there are no unexpected env vars, installs, or persistence requirements, though the doc omits practical notes about authentication and reliance on npx.

Purpose & Capability

The name/description (deploy & manage Vercel projects) aligns with the runtime instructions (vercel link, vercel git connect, vercel env add, vercel domains ls). There are no unrelated credentials, binaries, or config paths requested.

Instruction Scope

Instructions are narrowly scoped to running Vercel CLI commands from a project repo root and adding env vars. They instruct the agent to change directories to project roots and reference a local 'domains.md' file, which implies reading repository files (expected for repo-based deploys). The SKILL.md does not mention authentication requirements (e.g., VERCEL_TOKEN or being logged in) or how to install the vercel CLI if missing.

Install Mechanism

No install spec or bundled code — instruction-only. The only runtime dependency implied is npx/vercel CLI; npx may fetch packages from the npm registry at runtime, which is normal but means code could be executed from the network if the CLI isn't already installed.

Credentials

The skill declares no required environment variables, which is consistent with being instruction-only, but in practice the vercel CLI typically requires authentication (interactive login or VERCEL_TOKEN). The SKILL.md does not declare or explain these credentials, so users should expect to supply them outside the skill.

Persistence & Privilege

always is false and there is no install or code that persists or modifies other skills or system-wide settings. The skill does not request permanent presence or elevated privileges.

Assessment

This skill is instruction-only and appears coherent for managing Vercel projects. Before using it, ensure the agent environment has a trusted vercel CLI (or be aware that npx will download and run code from npm), and that you are comfortable with the agent running shell commands in your repository directories. The SKILL.md omits authentication details — you will likely need to be logged into Vercel or provide a VERCEL_TOKEN in the environment when running these commands. Avoid running these commands in environments containing untrusted or sensitive data unless you control the CLI binary and know which credentials will be used.

Vercel — Deploy and Manage Projects

Set Up a New Project

cd <project-root>   # must be the directory with .git
npx vercel link      # link to Vercel project
npx vercel git connect  # connect GitHub repo for auto-deploys

Run vercel git connect from the repo root (where .git lives), not a subdirectory.

Set Environment Variables

NEVER use echo — it adds a trailing \n:

printf 'value' | npx vercel env add VAR_NAME production

Check Domains

cd any-vercel-project && npx vercel domains ls

For the full domain list: see domains.md in this folder.