# Vercel Deploy

> Deploy or manage projects on Vercel from an agent workflow. Use when the user asks to deploy to Vercel, create a preview deployment, push a Vercel preview, link a project to Vercel, explain Vercel deployment flow, or work with Vercel CLI/token setup.

- **Type:** Skill
- **Install:** `agentstack add skill-tommylower-cortex-vercel-deploy`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [tommylower](https://agentstack.voostack.com/s/tommylower)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [tommylower](https://github.com/tommylower)
- **Source:** https://github.com/tommylower/cortex/tree/main/agent-workflows/vercel-deploy

## Install

```sh
agentstack add skill-tommylower-cortex-vercel-deploy
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# Vercel Deploy

Use this for deployment workflow, not design work. Default to preview deployments unless the user explicitly asks for production.

## What Vercel Deployment Does

Vercel can deploy in two common ways:

- **Git integration:** pushing a branch triggers a Vercel build. Non-production branches produce preview URLs; the production branch produces the production deployment.
- **CLI deployment:** `vercel deploy` uploads the current project and returns a deployment URL. This is useful for unlinked projects, prototypes, or repos without git integration.

Linking creates `.vercel/project.json` or `.vercel/repo.json`, which tells the CLI which Vercel project/team the local repo belongs to.

## Initial Checks

Run these before choosing a path:

```bash
git remote get-url origin 2>/dev/null
cat .vercel/project.json 2>/dev/null || cat .vercel/repo.json 2>/dev/null
vercel whoami 2>/dev/null
vercel teams list --format json 2>/dev/null
```

If multiple teams are available and the project is not already linked, ask which team slug to use. If `.vercel/` already exists, use the linked org/project.

## Preferred Flow

1. If the project is linked and has a git remote, ask before committing or pushing.
2. Commit intentionally, push the branch, and let Vercel create the preview deployment.
3. Use `vercel ls --format json` or the git provider checks to find the preview URL.

## CLI Flow

Use CLI deploy when there is no git remote or the user explicitly wants direct deployment:

```bash
vercel deploy -y --no-wait
vercel inspect 
```

Production deploys require explicit user wording:

```bash
vercel deploy --prod -y --no-wait
```

## Token-Based Flow

If using a token, prefer `VERCEL_TOKEN` in the environment. Do not pass tokens through command-line flags.

```bash
export VERCEL_TOKEN=""
vercel deploy -y --no-wait
```

If available, also export both project variables:

```bash
export VERCEL_ORG_ID=""
export VERCEL_PROJECT_ID=""
```

## Safety Rules

- Preview by default.
- Never push, create production deployments, or modify Vercel environment variables without explicit user intent.
- Never commit `.env` files or token values.
- Do not rely on interactive commands when a non-interactive flag or state check exists.
- If a build fails after adding dev tools, inspect top-level imports for dev-only packages first.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [tommylower](https://github.com/tommylower)
- **Source:** [tommylower/cortex](https://github.com/tommylower/cortex)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** yes
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-tommylower-cortex-vercel-deploy
- Seller: https://agentstack.voostack.com/s/tommylower
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.