deploy-to-vercel SKILL.md skillA

This file is byte-identical to the first copy the registry indexed, one of 4 indexed copies. Same content hash, so the same checks give both the same grade.

deploy-to-vercel from asymmetric-al/core is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

mdr add asymmetric-al/core/deploy-to-vercel@v3.0.0

Pins v3.0.0 in mdr.lock. Pin the fingerprint instead.

Audit grade

A, 17 of 17 checks passed

Kind

SKILL.md skill

Repository

asymmetric-al/core

Path

.agents/skills/deploy-to-vercel/SKILL.md

Versions recorded

1

Latest version

v3.0.0, committed May 26, 2026

Size

11,786 bytes

Repository stars

370

License

AGPL-3.0

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.

What the file says

# Deploy to Vercel

Deploy any project to Vercel. **Always deploy as preview** (not production) unless the user explicitly asks for production.

The goal is to get the user into the best long-term setup: their project linked to Vercel with git-push deploys. Every method below tries to move the user closer to that state.

## Step 1: Gather Project State

Run all four checks before deciding which method to use:

```bash
# 1. Check for a git remote
git remote get-url origin 2>/dev/null

# 2. Check if locally linked to a Vercel project (either file means linked)
cat .vercel/project.json 2>/dev/null || cat .vercel/repo.json 2>/dev/null

# 3. Check if the Vercel CLI is installed and authenticated
vercel whoami 2>/dev/null

# 4. List available teams (if authenticated)
vercel teams list --format json 2>/dev/null
```

### Team selection

If the user belongs to multiple teams, present all available team slugs as a bulleted list and ask which one to deploy to. Once the user picks a team, proceed immediately to the next step — do not ask for additional confirmation.

Pass the team slug via `--scope` on all subsequent CLI commands (`vercel deploy`, `vercel link`, `vercel inspect`, etc.):
…

Read the whole file at its exact version.

How to install

mdr add asymmetric-al/core/deploy-to-vercel@sha256:cfcc3dd479ab2e0a

[![mdr](https://markdownregistry.com/badge/art_2dxbdwykvjdo7mgv.svg)](https://markdownregistry.com/a/art_2dxbdwykvjdo7mgv)

Versions

The registry has recorded 1 version of this file, committed on May 26, 2026.

Audit of the latest version

Source

API

GET https://markdownregistry.com/api/v1/artifacts/art_2dxbdwykvjdo7mgv
GET https://markdownregistry.com/api/v1/resolve?ref=asymmetric-al/core/deploy-to-vercel
GET https://markdownregistry.com/api/v1/blob/cfcc3dd479ab2e0ae721ddf39b8af84d977321487672f1487c8d6855f576927b

Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.

Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.

More from asymmetric-al/core

Every file in asymmetric-al/core

Other files named deploy-to-vercel

Browse by kind, by grade A, or by owner.