How do I install the Deploy skill?

Run npx skillmds@latest add waseemnasir2k26/deploy-2 in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Deploy safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: makes network calls, reads secrets. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Deploy?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Deploy free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Deploy?

waseemnasir2k26 (@waseemnasir2k26) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Deploy by waseemnasir2k26 — Agent Skill

Name: Deploy
Rating: 4.2 (5 reviews)
Author: waseemnasir2k26

File contents

deploy — static folder → a real live URL

Prerequisite

The vercel CLI must be installed and already authenticated on this machine:

npm i -g vercel
vercel login

If vercel whoami errors, stop and tell the user to log in. Never fake a URL.

Steps

Confirm the CLI is available and authed: vercel whoami.
Deploy the site folder to production and capture the full output:
```
vercel deploy "./out/site" --prod --yes
```
Parse the Production: (and any Aliased:) URL from the CLI output.

Kill the auth wall (only if your account enables it). Vercel Team/Pro accounts default new projects to SSO "Deployment Protection" — the .vercel.app URL then redirects to a Vercel login and nobody but you can open it. Check step 5 first; if the URL is walled, disable protection via the API.

The CLI writes the project + org ids to ./out/site/.vercel/project.json on first deploy, so read them from there rather than hard-coding anything:

# A Vercel API token you created yourself:
#   https://vercel.com/account/tokens  →  export VERCEL_TOKEN=...
# (Never commit a token, and never read one out of the CLI's credentials file.)
PID=$(python -c "import json;print(json.load(open('./out/site/.vercel/project.json'))['projectId'])")
TID=$(python -c "import json;print(json.load(open('./out/site/.vercel/project.json'))['orgId'])")

curl -s -X PATCH "https://api.vercel.com/v9/projects/$PID?teamId=$TID" \
  -H "Authorization: Bearer $VERCEL_TOKEN" -H "Content-Type: application/json" \
  -d '{"ssoProtection":null}'

On a personal (hobby) account there is no team — drop the ?teamId= query entirely.

Verify it is actually public — a redirect to vercel.com/login = still walled, DO NOT report success:

curl -sL -o /dev/null -w "%{http_code} %{url_effective}\n" <URL>
# MUST be: 200 <URL>/   (NOT 200 https://vercel.com/login?...)

Return exactly one line: Live: <URL> — the real, clickable, PUBLIC production URL.

Rules

The URL must be real, PUBLIC (no auth wall), and load 200. Never invent or guess a URL.
If deploy fails, report the CLI error verbatim and stop.
Never print, log, or embed the token. Read it from the VERCEL_TOKEN environment variable only.
.vercel/ is generated per-machine and is git-ignored — it is not part of this repo.
The public-verify (step 5) is MANDATORY. The whole value of the chain is that anyone can open the URL you hand them.

---name: deploy-2description: Use to deploy a static site folder to Vercel and return the live production URL. Runs the vercel CLI (must already be logged in). Called as step 3 of the launch chain.---# deploy — static folder → a real live URL## PrerequisiteThe `vercel` CLI must be installed and already authenticated on this machine:```bashnpm i -g vercelvercel login```If `vercel whoami` errors, stop and tell the user to log in. Never fake a URL.## Steps1. Confirm the CLI is available and authed: `vercel whoami`.2. Deploy the site folder to production and capture the full output: ```bash vercel deploy "./out/site" --prod --yes ```3. Parse the `Production:` (and any `Aliased:`) URL from the CLI output.4. **Kill the auth wall (only if your account enables it).** Vercel Team/Pro accounts default new projects to SSO "Deployment Protection" — the `.vercel.app` URL then redirects to a Vercel login and nobody but you can open it. Check step 5 first; if the URL is walled, disable protection via the API. The CLI writes the project + org ids to `./out/site/.vercel/project.json` on first deploy, so read them from there rather than hard-coding anything: ```bash # A Vercel API token you created yourself: # https://vercel.com/account/tokens → export VERCEL_TOKEN=... # (Never commit a token, and never read one out of the CLI's credentials file.) PID=$(python -c "import json;print(json.load(open('./out/site/.vercel/project.json'))['projectId'])") TID=$(python -c "import json;print(json.load(open('./out/site/.vercel/project.json'))['orgId'])") curl -s -X PATCH "https://api.vercel.com/v9/projects/$PID?teamId=$TID" \ -H "Authorization: Bearer $VERCEL_TOKEN" -H "Content-Type: application/json" \ -d '{"ssoProtection":null}' ``` On a personal (hobby) account there is no team — drop the `?teamId=` query entirely.5. **Verify it is actually public** — a redirect to `vercel.com/login` = still walled, DO NOT report success: ```bash curl -sL -o /dev/null -w "%{http_code} %{url_effective}\n" <URL> # MUST be: 200 <URL>/ (NOT 200 https://vercel.com/login?...) ```6. Return exactly one line: `Live: <URL>` — the real, clickable, PUBLIC production URL.## Rules- The URL must be real, PUBLIC (no auth wall), and load 200. Never invent or guess a URL.- If deploy fails, report the CLI error verbatim and stop.- Never print, log, or embed the token. Read it from the `VERCEL_TOKEN` environment variable only.- `.vercel/` is generated per-machine and is git-ignored — it is not part of this repo.- The public-verify (step 5) is MANDATORY. The whole value of the chain is that anyone can open the URL you hand them.

Frequently asked questions

Deploy