Vercel Deploy

Name: Vercel Deploy
Author: Dokhacgiakhoa

ASecurity

Automated Vercel deployment skill.

508 stars
0 votes
0 copies
7 views
Added February 8, 2026

developmentgonextjstestingfrontendci/cd

Works with

Security analysis

A92/100

mediumInstalls packages at runtime which could introduce malicious dependencies

Pro shows the line behind each finding and how to fix it

Scanned February 12, 2026

npx -y skills add Dokhacgiakhoa/antigravity-ide --skill vercel-deploy --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Vercel Deploy?

Add the live security badge to your README. It updates with every re-scan.

[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/dokhacgiakhoa-vercel-deploy/badge)](https://www.skillsdirectory.com/skills/dokhacgiakhoa-vercel-deploy)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro

SKILL.md

---
name: vercel-deploy
description: Automated Vercel deployment skill.
category: infrastructure
version: 4.0.5
layer: master-skill
---

# Vercel Deployment Skill

> **Goal**: Seamlessly deploy any frontend/full-stack application to Vercel global edge network.

## 1. Prerequisites

- **CLI**: `vercel` (Install via `npm i -g vercel`)
- **Auth**: User must be logged in (`vercel login`) or provide `VERCEL_TOKEN`.

## 2. Deployment Workflow

1.  **Detection**:
    - Scanner checks `package.json` for frameworks (Next.js, Vite, Remix, Astro).
    - Identifies build command (`npm run build`) and output directory (`dist` or `.next`).

2.  **Configuration**:
    - Generates `vercel.json` if custom headers/rewrites are needed.
    - Sets project settings (Root Directory, Framework Preset).

3.  **Execution**:
    - **Preview**: `vercel --no-prod` (For testing feature branches).
    - **Production**: `vercel --prod` (For live release).

4.  **Verification**:
    - Checks deployment status via `vercel inspect <url>`.
    - Returns the **Claimable URL** for the user.

## 3. Environment Variables

- **Auto-Sync**: Pulls `.env` from Vercel Project Settings (`vercel env pull`).
- **Push**: Pushes local `.env` to Vercel (Interactive confirmation required).

## 4. Troubleshooting common errors

- **Build Fail**: Usually due to strict type checking or linting in CI. Suggest `ignoreBuildErrors: true` ONLY for hotfixes.
- **Missing Secrets**: Check if `VERCEL_TOKEN` is active in CI/CD environment.

---

**Command Reference**:
- `vercel link`: Link local folder to remote project.
- `vercel deploy`: Deploy preview.
- `vercel deploy --prod`: Deploy production.