Skills deploy-to-vercel
๐Ÿ“ฆ

deploy-to-vercel

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

Deploy Projects to Vercel

Vercel deployments require different steps depending on Git integration, project linking, and authentication. This skill guides deployment selection, team setup, and deployment URL reporting.

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 "deploy-to-vercel" from https://skillstore.io/skills/vercel-labs-deploy-to-vercel.md and its manifest at https://skillstore.io/api/skills/vercel-labs-deploy-to-vercel/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 "deploy-to-vercel". Check whether this project is ready for a Vercel deployment.

Expected outcome:

  • Example readiness report: The project has a Git remote and local Vercel linking metadata.
  • Review the branch and changed files before approving a commit and push.
  • No deployment has been started.

Using "deploy-to-vercel". Deploy this linked project directly and report its status.

Expected outcome:

  • Example deployment report: The CLI returned a deployment URL; include the actual URL here.
  • Build status: Building. Deployment creation does not establish that the application works.
  • No HTTP verification was performed.

Using "deploy-to-vercel". Create an approved temporary deployment for this demonstration.

Expected outcome:

  • Example temporary deployment report: Include the deployment URL returned by the CLI.
  • Include the separate claim URL and expiration returned by the CLI.
  • Keep the claim URL private.

Security Audit

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

All 68 static findings are false positives involving Markdown, documentation links, error redirection, or deployment account checks. Two semantic risks remain: indiscriminate Git staging and deployment paths that can publish production without explicit production approval. No evidence found of malicious exfiltration or audit-directed prompt injection.

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

Confirmed security concerns (2)

High
Broad Git Staging Can Publish Unreviewed Files
The approved push workflow runs "git add ." before committing and pushing. Without reviewing changes, this can publish unrelated work or unignored secrets.
The example explicitly stages every change under the current directory without a diff or secret review. Push approval does not identify the staged contents.
High
Production Deployment Paths Bypass The Preview Default
The skill requires previews unless production is requested. Its Git workflow pushes the current branch without checking production settings, and its no-auth fallback uses a temporary production URL.
The text explicitly says production branches deploy production, but the push steps never check the branch. The temporary fallback also explicitly describes production deployment.
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-deploy-to-vercel/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-deploy-to-vercel/security.svg)](https://skillstore.io/skills/vercel-labs-deploy-to-vercel?utm_source=security_passport_badge)

HTML badge

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

Embed card

<iframe src="https://skillstore.io/embed/skills/vercel-labs-deploy-to-vercel.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). deploy-to-vercel security audit report (audit version 6) [Author version 4.0.0]. Skillstore. https://skillstore.io/skills/vercel-labs-deploy-to-vercel/audits/6

BibTeX citation

@techreport{vercel-labs-vercel-labs-deploy-to-vercel-2026, author = {vercel-labs}, title = {deploy-to-vercel security audit report (audit version 6)}, institution = {Skillstore}, year = {2026}, number = {6}, url = {https://skillstore.io/skills/vercel-labs-deploy-to-vercel/audits/6}, note = {Author version 4.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: "deploy-to-vercel security audit report (audit version 6)" version: "4.0.0" type: report authors: - name: "vercel-labs" date-released: "2026-11-09" url: "https://skillstore.io/skills/vercel-labs-deploy-to-vercel/audits/6" identifiers: - type: other value: "skillstore:vercel-labs-deploy-to-vercel:audit:6" description: "Skillstore immutable audit report identifier"

Skillstore Score

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

What You Can Build

Share A Feature Preview

Deploy an approved feature branch through an existing Vercel Git integration and retrieve its deployment URL.

Set Up Team Deployment

Select a Vercel team, link a local project, and choose an appropriate deployment method.

Publish A Temporary Demonstration

Use the no-login fallback for a non-sensitive demonstration, then report its claim link and expiration.

Try These Prompts

Check Deployment Readiness
Check this project's Git remote, Vercel linking state, authentication, and teams. Recommend a deployment method without changing files or deploying.
Deploy A Linked Project
Deploy this linked project as a preview using the Vercel CLI. Confirm the target team and report the deployment URL and build status.
Deploy Through Git
Review changed files and stage only approved paths. Confirm this is not the production branch, then request my approval before committing and pushing.
Use A Temporary Deployment
Check temporary deployment eligibility and confirm no sensitive files will be uploaded. I approve a temporary production URL; report its claim link and expiration.

Best Practices

  • Review changed files and secrets, then stage only approved paths before authorizing a Git push.
  • Confirm the target team, project, and production branch before deploying; require explicit approval for production or temporary production URLs.
  • Inspect build status and keep temporary deployment claim links private.

Avoid

  • Running the broad Git staging example without reviewing unrelated changes and unignored secrets.
  • Assuming every Git push or temporary deployment produces a preview environment.
  • Treating a returned deployment URL as proof that the application builds successfully or works correctly.

Frequently Asked Questions

Which AI tools can use this skill?
The report lists Claude, Codex, and Claude Code. Actual deployment requires the environment to provide the necessary shell and network permissions.
Do I need a Vercel account?
Standard linking and deployment use Vercel authentication. The skill also describes a temporary deployment fallback without login.
Does it always create preview deployments?
No. Although previews are the stated default, pushing a production branch or using the temporary fallback can create production deployments.
Will it commit and push my changes?
The Git workflow requests approval before committing and pushing. Its example stages all local changes, so review files and narrow staging first.
How does it choose a Vercel team?
It reads linked organization metadata or lists available teams. It asks when multiple teams are available and otherwise uses the single destination.
Does it test the deployed website?
No. It reports deployment URLs and can inspect build status, but explicitly avoids fetching the deployed URL for verification.

Developer Details

License

Unknown

Author version

v4.0.0

Skillstore revision

r2

Ref

1f79e59ae427a74eab604c013e03b61f04634721

Maintenance freshness

11/10/2026

Usage

18 downloads ยท 185 views

File structure

๐Ÿ“„ SKILL.md

More from vercel-labs

View all
View all