vercel-cli
Manage Vercel Deployments and CLI Workflows
Vercel operations can target the wrong project or confuse incomplete telemetry with successful execution. This skill guides scoped CLI workflows with credential safeguards and explicit verification.
Install with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "vercel-cli" from https://skillstore.io/skills/vercel-vercel-cli.md and its manifest at https://skillstore.io/api/skills/vercel-vercel-cli/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.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". Review my preview deployment plan before running it.
Expected outcome:
- Target check: confirm the resolved team and project from the application working directory.
- Source choice: use local source for checkout changes, or the prebuilt path for existing build output.
- Verification: wait for Ready or Error before reporting completion.
- No deployment has been started.
Using "vercel-cli". Does an empty log page prove that the incident did not happen?
Expected outcome:
- No. Confirm the project, deployment, environment, and affected time window.
- Check pagination and excluded intervals before drawing conclusions.
- Distinguish missing data from permission, retention, and subscription limits.
Using "vercel-cli". Why can a valid Blob token fail when local OIDC variables are present?
Expected outcome:
- Partial OIDC configuration produces an error instead of falling back to the read-write token.
- A complete OIDC pair takes precedence over a static token within the same environment source.
- Check configuration completeness without printing credential values.
Security Audit
SafeAll 28 static findings are false positives involving documentation links, Markdown formatting, or legitimate Vercel workflows with explicit safeguards. No evidence found of credential exfiltration, unauthorized reconnaissance, or prompt injection in the reviewed files. Actual operations still require appropriate credentials, verified targets, and user authorization.
Risk Factors
๐ Filesystem access (5)
๐ Network access (2)
โ๏ธ External commands (8)
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-vercel-cli/audits/1?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/vercel-vercel-cli?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/vercel-vercel-cli?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/vercel-vercel-cli/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/vercel-vercel-cli.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. (2026). vercel-cli security audit report (audit version 1) [Author version unspecified]. Skillstore. https://skillstore.io/skills/vercel-vercel-cli/audits/1BibTeX citation
@techreport{vercel-vercel-vercel-cli-2026,
author = {vercel},
title = {vercel-cli security audit report (audit version 1)},
institution = {Skillstore},
year = {2026},
number = {1},
url = {https://skillstore.io/skills/vercel-vercel-cli/audits/1},
note = {Author version unspecified}
}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 security audit report (audit version 1)"
version: "unspecified"
type: report
authors:
- name: "vercel"
date-released: "2026-11-06"
url: "https://skillstore.io/skills/vercel-vercel-cli/audits/1"
identifiers:
- type: other
value: "skillstore:vercel-vercel-cli:audit:1"
description: "Skillstore immutable audit report identifier"
Skillstore Score
Why this score Evidence Confidence: MediumWhat You Can Build
Validate an Application Deployment
Choose the correct source or prebuilt path, verify the target project, and check the deployment state before promotion.
Investigate a Production Regression
Inspect the supplied deployment, query the affected time window, and distinguish observed failures from telemetry gaps.
Configure Monorepo Delivery
Check repository mappings, align build and deployment environments, and verify artifact completeness across CI jobs.
Try These Prompts
Check the installed Vercel CLI and explain its help for inspecting a deployment. Do not install, upgrade, authenticate, or change resources.
Prepare a preview deployment from [app directory]. Verify the resolved team and project first. Explain the source choice and request approval before deploying.
Investigate [deployment URL] during [time window]. Inspect metadata and build logs, then relevant telemetry. Separate proven causes from hypotheses. Do not mutate resources.
Review [app directory] for a split build/deploy CI workflow. Verify mappings, environment consistency, and artifact completeness. Propose changes without applying them or revealing credentials.
Best Practices
- Verify the resolved team, project, and environment before pulling data or changing resources.
- Use installed CLI help, preserve the chosen version, and keep credentials out of arguments and output.
- Check final deployment states, pagination, and telemetry coverage before reporting success or absence.
Avoid
- Assuming an application directory name or successful login proves the intended project target.
- Treating non-interactive mode, suggested commands, or API access as permission to mutate resources.
- Disabling deployment protection or bypassing confirmation to work around access limitations.
Frequently Asked Questions
Does this skill include the Vercel CLI?
Can I use it with Claude, Codex, and Claude Code?
How does it choose the correct monorepo project?
Will an environment pull recover stored Secret values?
Can it diagnose missing logs?
Will it automatically bypass interactive confirmations?
Developer Details
Author
vercelLicense
Unknown
Skillstore revision
r1
Version notice
The author did not declare a version.
Repository
https://github.com/vercel/vercel/tree/84878e532142f0ac584953695658b324eb9e5b80/skills/vercel-cliRef
c993c6abcbffafea2683d7748b53b3dfaf438415
Maintenance freshness
11/9/2026
Usage
0 downloads ยท 0 views
File structure
๐ command/
๐ vercel.md
๐ references/
๐ advanced.md
๐ agent-and-ai.md
๐ bun.md
๐ ci.md
๐ comments.md
๐ connectors.md
๐ deployment.md
๐ domains-and-dns.md
๐ firewall.md
๐ flags.md
๐ integrations.md
๐ microfrontends.md
๐ monitoring-and-debugging.md
๐ monorepos.md
๐ node-backends.md
๐ platform-ops.md
๐ project-infra.md
๐ routing.md
๐ sandbox.md
๐ storage.md
๐ SKILL.md