Skills vercel-cli-with-tokens
๐Ÿ“ฆ

vercel-cli-with-tokens

v1.0.0 Content revision r2 High Risk โš™๏ธ External commands๐ŸŒ Network access๐Ÿ“ Filesystem access

Deploy Vercel Projects with Access Tokens

Interactive authentication and unclear project scope complicate automated Vercel deployments. This skill provides token-based CLI guidance for deployments, project configuration, and troubleshooting.

Supports: Claude Codex Code(CC)
Maintain this Skill? Claim it โš ๏ธ 38 Poor

Install with my Agent

Copy this request to your Agent. It includes the canonical Skill page and manifest.

Agent request
Review the Skillstore skill "vercel-cli-with-tokens" from https://skillstore.io/skills/vercel-labs-vercel-cli-with-tokens.md and its manifest at https://skillstore.io/api/skills/vercel-labs-vercel-cli-with-tokens/manifest. Verify the artifact. Stop and obtain explicit user consent before installing or changing files.

Your Agent should still show its plan and request any confirmation required by the security policy.

Test it

Using "vercel-cli-with-tokens". Show a readiness summary when the token exists but project scope is incomplete.

Expected outcome:

  • Authentication: token present; value withheld.
  • Project context: organization identifier missing.
  • Next step: confirm the intended team and project before deployment.
  • Deployment: not started.

Using "vercel-cli-with-tokens". Explain a deployment failure when build logs indicate missing configuration.

Expected outcome:

  • Deployment state: build failed.
  • Reported cause: a required environment variable is missing.
  • Proposed action: add the variable to the intended deployment environment after approval.
  • Verification: inspect the next build result; no deployed-page request performed.

Security Audit

High Risk
v6 โ€ข 11/9/2026 Open versioned report

Most alerts identify Markdown formatting, local parsing, official Vercel links, or authorized CLI operations rather than malicious execution or reconnaissance. Credential lookup commands expose token values in captured output, while deployment guidance omits important commit, production-branch, and destructive-action safeguards. No evidence found of prompt injection or deliberate external credential exfiltration.

1
Files scanned
354
Lines analyzed
0
Review items
0
False positives ignored

Confirmed security concerns (7)

High
Environment file access
grep '^VERCEL_TOKEN=' .env 2>/dev/null
The grep command prints the complete VERCEL_TOKEN assignment, exposing the access token to captured command output and assistant transcripts.
High
Environment file access
grep -i 'vercel' .env 2>/dev/null
Broad grep prints every matching environment assignment, including Vercel credentials, into captured output instead of silently selecting the authentication variable.
High
Environment file access
grep -i 'vercel' .env 2>/dev/null
Although this step seeks project identifiers, its broad grep also prints token assignments, unnecessarily disclosing credentials in tool output.
High
Environment file access
grep -i vercel .env 2>/dev/null
The troubleshooting command prints matching environment values, including access tokens, into captured output without redaction.
Medium
Deployment Commits the Entire Working Directory
The Git deployment recipe runs git add . before committing and pushing. Unreviewed changes or unignored secrets can enter the approved deployment commit.
The recipe explicitly stages all current-directory changes without reviewing the diff or selecting paths. Push approval does not establish approval for every staged file.
Medium
Git Deployment Omits Production Branch Verification
The preferred Git flow pushes without checking the destination branch. A production-branch push can deploy production without the separate approval required elsewhere.
The document acknowledges branch-dependent deployments but supplies no branch check before git push. General push consent does not necessarily authorize production.
Medium
Blanket Prompt Bypass Lacks Destructive Action Approval
The working agreement recommends -y for confirmation prompts, and the environment-variable removal example uses it. Destructive removal has no explicit user-approval requirement.
Both instructions explicitly bypass confirmation, while approval requirements only cover Git pushes, production deployment, and paid or destructive plan changes.
Audited by: codex View Audit History โ†’
Share & cite this report

Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.

Open versioned report
Security Assessment

Copy report link

https://skillstore.io/skills/vercel-labs-vercel-cli-with-tokens/audits/6?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_report

Markdown badge

[![Skillstore security assessment](https://skillstore.io/badges/skills/vercel-labs-vercel-cli-with-tokens/security.svg)](https://skillstore.io/skills/vercel-labs-vercel-cli-with-tokens?utm_source=security_passport_badge)

HTML badge

<a href="https://skillstore.io/skills/vercel-labs-vercel-cli-with-tokens?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/vercel-labs-vercel-cli-with-tokens/security.svg" alt="Skillstore security assessment" loading="lazy"></a>

Embed card

<iframe src="https://skillstore.io/embed/skills/vercel-labs-vercel-cli-with-tokens.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>
Academic citations (APA ยท BibTeX ยท CFF)

APA citation

vercel-labs. (2026). vercel-cli-with-tokens security audit report (audit version 6) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/vercel-labs-vercel-cli-with-tokens/audits/6

BibTeX citation

@techreport{vercel-labs-vercel-labs-vercel-cli-with-tokens-2026, author = {vercel-labs}, title = {vercel-cli-with-tokens security audit report (audit version 6)}, institution = {Skillstore}, year = {2026}, number = {6}, url = {https://skillstore.io/skills/vercel-labs-vercel-cli-with-tokens/audits/6}, note = {Author version 1.0.0} }

CITATION.cff

cff-version: 1.2.0 message: "If you use this Skill, cite its author and this versioned security audit report." title: "vercel-cli-with-tokens security audit report (audit version 6)" version: "1.0.0" type: report authors: - name: "vercel-labs" date-released: "2026-11-09" url: "https://skillstore.io/skills/vercel-labs-vercel-cli-with-tokens/audits/6" identifiers: - type: other value: "skillstore:vercel-labs-vercel-cli-with-tokens:audit:6" description: "Skillstore immutable audit report identifier"

Skillstore Score

Why this score Evidence Confidence: High
55
Architecture
80
Maintainability
87
Content
70
Community
65
Spec Compliance

What You Can Build

Prepare a Preview Deployment

Select the intended Vercel project and prepare a token-authenticated preview deployment without interactive login.

Manage Project Configuration

Review team scope, environment-variable operations, and domain assignments across Vercel projects.

Investigate Release Failures

Inspect deployment state and logs while checking authentication, team selection, and production approval.

Try These Prompts

Check Authentication Readiness
Check whether VERCEL_TOKEN is available without printing its value. Identify missing setup requirements, but do not deploy or change project settings.
Prepare a Scoped Preview
Prepare a preview deployment for [project] under [team]. Verify both project identifiers and keep secrets out of output. Do not push Git changes.
Review Environment Changes
Review environment-variable names for [project] in [environment] without displaying values. Propose changes first. Ask for approval before adding, removing, or downloading variables.
Audit a Production Release
Prepare a production release plan for [project]. Review changed files, destination branch, project scope, and build logs. Require explicit approval before pushing or deploying production.

Best Practices

  • Use presence-only token checks and silent loading; keep credentials out of transcripts, shell history, and shared logs.
  • Confirm team, project, environment, and destination branch; use preview deployments unless production is explicitly approved.
  • Review diffs and stage only approved files; obtain specific approval before pushes, destructive operations, and paid plan changes.

Avoid

  • Printing token values with environment dumps or broad environment-file searches.
  • Staging every changed file or pushing an unchecked branch as a deployment shortcut.
  • Using automatic confirmation to replace user approval for destructive operations or paid changes.

Frequently Asked Questions

Does this skill require interactive Vercel login?
It describes access-token authentication instead of interactive login. You still need a valid token and suitable project permissions.
Where should the authentication token be supplied?
The skill describes using VERCEL_TOKEN in the environment. Load it securely and never print its value during checks.
Can deployments run without a local project link?
The documented workflow uses VERCEL_ORG_ID and VERCEL_PROJECT_ID together to select the project without local linking metadata.
Are deployments always previews?
CLI guidance defaults to preview, but Git pushes depend on branch configuration. Check the destination branch and require explicit production approval.
Does the skill verify the deployed website?
It describes deployment inspection and log retrieval, but explicitly avoids fetching deployed pages. A returned deployment link does not prove application correctness.
Can it change a Vercel subscription plan?
It documents Stripe Projects plan commands for eligible projects. Paid or destructive plan changes require user approval and appropriate access.

Developer Details

License

Unknown

Author version

v1.0.0

Skillstore revision

r2

Version notice

The installable content changed, but the author did not update the declared version.

Ref

1f79e59ae427a74eab604c013e03b61f04634721

Maintenance freshness

11/10/2026

Usage

12 downloads ยท 200 views

File structure

๐Ÿ“„ SKILL.md

More from vercel-labs

View all
View all