Skills vercel-cli-with-tokens
📦
vercel-cli-with-tokens
v1.0.0 Content revision r1 High Risk ⚙️ External commands🌐 Network access📁 Filesystem access
Deploy Vercel Projects with Tokens
Interactive Vercel login can block AI-assisted deployment workflows. This skill guides token-based CLI setup, preview deployments, project linking, and environment management.
Supports: Claude Codex Code(CC)
Stop for confirmation before installing.
Review the plan and obtain explicit user consent before changing files.
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.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "vercel-cli-with-tokens". Deploy this app to Vercel as a preview using my token.
Expected outcome:
The assistant identifies the token source, confirms the project scope, starts a preview deployment, and returns the Vercel deployment URL.
Using "vercel-cli-with-tokens". Set the API endpoint for my Vercel project.
Expected outcome:
The assistant asks for the value, confirms the target environment, applies the variable through Vercel CLI, and summarizes the changed setting.
Using "vercel-cli-with-tokens". Check why the latest Vercel build failed.
Expected outcome:
The assistant lists recent deployments, opens the relevant build logs, and reports the likely cause with the next corrective step.
Security Audit
High Riskv5 • 7/7/2026 Open versioned report
Most Markdown backtick detections are false positives because SKILL.md is documentation, not executable Ruby or JavaScript. Confirmed issues are the intended handling of Vercel tokens and env files, plus automation that can mutate Vercel deployments, environment variables, domains, and confirmations. No prompt injection text was found.
1
Files scanned
329
Lines analyzed
7
Review items
0
False positives ignored
Confirmed security concerns (15)
High
Environment file access
### B) Token is in a `.env` file under `VERCEL_TOKEN`
The prose instructs the assistant to inspect environment variables or env files for Vercel tokens. That is credential discovery and should be treated as sensitive access.
High
Environment file access
grep '^VERCEL_TOKEN=' .env 2>/dev/null
The command reads or exports values from a local env file while looking for Vercel credentials. This is expected for token setup, but it can expose secrets.
High
Environment file access
export VERCEL_TOKEN=$(grep '^VERCEL_TOKEN=' .env | cut -d= -f2-)
The command reads or exports values from a local env file while looking for Vercel credentials. This is expected for token setup, but it can expose secrets.
High
Environment file access
### C) Token is in a `.env` file under a different name
The prose instructs the assistant to inspect environment variables or env files for Vercel tokens. That is credential discovery and should be treated as sensitive access.
High
Environment file access
grep -i 'vercel' .env 2>/dev/null
The command reads or exports values from a local env file while looking for Vercel credentials. This is expected for token setup, but it can expose secrets.
High
Environment file access
export VERCEL_TOKEN=$(grep '^<VARIABLE_NAME>=' .env | cut -d= -f2-)
The command reads or exports values from a local env file while looking for Vercel credentials. This is expected for token setup, but it can expose secrets.
High
Environment file access
# Or check .env
The prose instructs the assistant to inspect environment variables or env files for Vercel tokens. That is credential discovery and should be treated as sensitive access.
High
Environment file access
grep -i 'vercel' .env 2>/dev/null
The command reads or exports values from a local env file while looking for Vercel credentials. This is expected for token setup, but it can expose secrets.
Show all 15 confirmed findings
High
Environment file access
# Pull env vars to local .env file
The workflow pulls Vercel environment variables into a local env file. This can expose application secrets on disk, so it is a confirmed sensitive-data risk.
High
Environment file access
- **Check the environment for tokens before asking the user.** Look in the current env and `.env` fi
The prose instructs the assistant to inspect environment variables or env files for Vercel tokens. That is credential discovery and should be treated as sensitive access.
High
Environment file access
Check the environment and any `.env` files present:
The prose instructs the assistant to inspect environment variables or env files for Vercel tokens. That is credential discovery and should be treated as sensitive access.
High
Environment file access
grep -i vercel .env 2>/dev/null
The command reads or exports values from a local env file while looking for Vercel credentials. This is expected for token setup, but it can expose secrets.
Medium
System reconnaissance
- **Use `-y`** on commands that prompt for confirmation to avoid interactive blocking.
The instruction recommends using -y to bypass interactive confirmations. That can make deployment, environment, or domain changes proceed without a final user check.
Medium
Confirmation Bypass for Cloud Changes
The skill recommends using -y to avoid prompts and includes destructive or state-changing Vercel commands. This can remove environment variables or change cloud resources without a final interactive confirmation.
Line 248 removes a Vercel environment variable with -y, and line 283 recommends -y broadly. The risk is contextual because the skill is intended for automation, but confirmation bypass is still material.
Medium
Cloud Resource Mutation Workflows
The skill provides workflows for production deployment, environment variable changes, and domain management. These are legitimate Vercel operations, but they can affect live services if run with the wrong scope or without approval.
The cited sections explicitly cover production deploys, Vercel env add/remove, and domain add operations. The skill includes some safeguards, so this is a medium-confidence operational risk rather than evidence of malicious intent.
Capability review items (7)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Medium
Shell command substitution
export VERCEL_TOKEN=$(grep '^VERCEL_TOKEN=' .env | cut -d= -f2-)
The snippet instructs extraction of VERCEL_TOKEN from a local .env file through shell commands. This is intentional, but it handles credentials and should remain security-relevant.
Medium
Shell command substitution
export VERCEL_TOKEN=$(grep '^<VARIABLE_NAME>=' .env | cut -d= -f2-)
The snippet instructs extraction of VERCEL_TOKEN from a local .env file through shell commands. This is intentional, but it handles credentials and should remain security-relevant.
Low
Standard device file access
grep '^VERCEL_TOKEN=' .env 2>/dev/null
The command reads a local .env file, which commonly contains secrets. The access is expected for this skill, but still needs caution and output masking.
Low
Standard device file access
grep -i 'vercel' .env 2>/dev/null
The command reads a local .env file, which commonly contains secrets. The access is expected for this skill, but still needs caution and output masking.
Low
Standard device file access
grep -i 'vercel' .env 2>/dev/null
The command reads a local .env file, which commonly contains secrets. The access is expected for this skill, but still needs caution and output masking.
Low
Standard device file access
cat .vercel/project.json 2>/dev/null || cat .vercel/repo.json 2>/dev/null
The command reads local .vercel project metadata files. These files are not normally secret tokens, but they can expose project and organization identifiers.
Low
Standard device file access
grep -i vercel .env 2>/dev/null
The command reads a local .env file, which commonly contains secrets. The access is expected for this skill, but still needs caution and output masking.
Risk Factors
⚙️ External commands (98)
SKILL.md:11 SKILL.md:17 SKILL.md:19-21 SKILL.md:21-25 SKILL.md:25 SKILL.md:27-29 SKILL.md:29-33 SKILL.md:33-35 SKILL.md:35-37 SKILL.md:37-39 SKILL.md:39-41 SKILL.md:41-43 SKILL.md:43-45 SKILL.md:45-47 SKILL.md:47-49 SKILL.md:49-57 SKILL.md:57 SKILL.md:59-66 SKILL.md:66-70 SKILL.md:70-72 SKILL.md:72-79 SKILL.md:79-81 SKILL.md:81-83 SKILL.md:83-86 SKILL.md:86-88 SKILL.md:88 SKILL.md:90-93 SKILL.md:93-95 SKILL.md:95 SKILL.md:101-104 SKILL.md:104-112 SKILL.md:112 SKILL.md:114-116 SKILL.md:116-118 SKILL.md:118 SKILL.md:120-122 SKILL.md:122-126 SKILL.md:126-128 SKILL.md:128-132 SKILL.md:132-134 SKILL.md:134-142 SKILL.md:142-148 SKILL.md:148-154 SKILL.md:154-156 SKILL.md:156-158 SKILL.md:158 SKILL.md:162-164 SKILL.md:164-166 SKILL.md:166-170 SKILL.md:170-172 SKILL.md:172-174 SKILL.md:174 SKILL.md:184-188 SKILL.md:188-191 SKILL.md:191-194 SKILL.md:194-195 SKILL.md:195-199 SKILL.md:199-201 SKILL.md:201-205 SKILL.md:205-207 SKILL.md:207-212 SKILL.md:212-215 SKILL.md:215-217 SKILL.md:217-219 SKILL.md:219-222 SKILL.md:222-225 SKILL.md:225 SKILL.md:226 SKILL.md:228 SKILL.md:230 SKILL.md:234-249 SKILL.md:249-253 SKILL.md:253-262 SKILL.md:262-266 SKILL.md:266-272 SKILL.md:272-276 SKILL.md:276 SKILL.md:277-280 SKILL.md:280-282 SKILL.md:282-283 SKILL.md:283-289 SKILL.md:289-291 SKILL.md:291-294 SKILL.md:294-298 SKILL.md:298-300 SKILL.md:300 SKILL.md:307-309 SKILL.md:309-315 SKILL.md:315-317 SKILL.md:317-320 SKILL.md:320-321 SKILL.md:321-322 SKILL.md:322 SKILL.md:326-328 SKILL.md:34 SKILL.md:48 SKILL.md:33-35 SKILL.md:47-49
🌐 Network access (3)
📁 Filesystem access (6)
Detected Patterns
System reconnaissance
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.
Copy report link
https://skillstore.io/skills/vercel-labs-vercel-cli-with-tokens/audits/5?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](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 5) [Author version 1.0.0]. Skillstore. https://skillstore.io/skills/vercel-labs-vercel-cli-with-tokens/audits/5BibTeX citation
@techreport{vercel-labs-vercel-labs-vercel-cli-with-tokens-2026,
author = {vercel-labs},
title = {vercel-cli-with-tokens security audit report (audit version 5)},
institution = {Skillstore},
year = {2026},
number = {5},
url = {https://skillstore.io/skills/vercel-labs-vercel-cli-with-tokens/audits/5},
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 5)"
version: "1.0.0"
type: report
authors:
- name: "vercel-labs"
date-released: "2026-07-07"
url: "https://skillstore.io/skills/vercel-labs-vercel-cli-with-tokens/audits/5"
identifiers:
- type: other
value: "skillstore:vercel-labs-vercel-cli-with-tokens:audit:5"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: High 55
Architecture
100
Maintainability
87
Content
70
Community
83
Spec Compliance
What You Can Build
Deploy a preview build
Prepare token authentication and run a preview deployment without interactive Vercel login.
Connect a repository to Vercel
Link a local or cloned repository to the correct Vercel project and team scope.
Operate Vercel from an AI assistant
Guide Claude, Codex, or Claude Code through safe CLI-based Vercel workflows.
Try These Prompts
Deploy a preview
Use the Vercel CLI token workflow to deploy this project as a preview. Confirm the token source and return the deployment link.
Link the project
Find the correct Vercel team and project identifiers, then link this repository to the matching Vercel project.
Update environment variables
Add or update the required Vercel environment variables for preview and production. Ask before changing production values.
Run a controlled release
Review project state, confirm git and Vercel scope, request approval for production deployment, then deploy and inspect the result.
Best Practices
- Use preview deployments by default and require explicit approval for production changes.
- Keep Vercel tokens out of command arguments, shell history, logs, and shared transcripts.
- Confirm team scope, project ID, and environment target before changing Vercel resources.
Avoid
- Passing a Vercel token through a command-line flag or pasting it into public output.
- Using confirmation bypass flags for production, domain, or environment changes without user approval.
- Deploying from an unverified repository or team scope.
Frequently Asked Questions
Does this skill require interactive Vercel login?
No. It is designed for workflows that use Vercel access tokens instead of browser-based login.
Can it deploy to production?
Yes, but the skill says production deployment should happen only when the user explicitly requests it.
Does it manage environment variables?
Yes. It includes workflows to add, list, pull, and remove Vercel environment variables.
Is token handling a security risk?
Yes. The workflow may inspect environment variables and env files, so secrets must be masked and handled carefully.
Which assistants can use this skill?
The report lists support for Claude, Codex, and Claude Code.
Does it verify deployed URLs by fetching them?
No. The skill says to return the deployment link without fetching the deployed URL.
Developer Details
Author
vercel-labsLicense
MIT
Author version
v1.0.0
Skillstore revision
r1
Ref
36e07d5e13068e5be64447e8f20b427cf2cbd21a
Maintenance freshness
7/18/2026
Usage
4 downloads · 200 views
File structure
📄 SKILL.md