Vercel
Set up a Codex monitor for Vercel deployments and preview URLs. Use when the user invokes /vercel or $vercel, asks Codex to watch or monitor a Vercel deployment, waits for a Vercel preview or PR preview to become ready, or wants to be notified with both the deployment URL and preview URL once Vercel is READY.
Get the complete skill folder, including its scripts and reference files.
When to use this skill
Use Vercel when an AI agent needs a reusable SKILL.md workflow for this job: Set up a Codex monitor for Vercel deployments and preview URLs. Use when the user invokes /vercel or $vercel, asks Codex to watch or monitor a Vercel deployment, waits for a Vercel preview or PR preview to become ready, or wants to be notified with both the deployment URL and preview URL once Vercel is READY.
When not to use it
Skip Vercel when the task is outside the productivity category, or when a more specific skill in this directory already covers the same workflow with clearer triggers.
How to install
Where will you use it?
mkdir -p ~/.claude/skills/vercel # Save SKILL.md to ~/.claude/skills/vercel/SKILL.md
- Claude Code personal install: place the skill and its bundled files at ~/.claude/skills/vercel/SKILL.md. For a shared project, commit the folder at .claude/skills/vercel/ instead.
- Current Claude Code detects SKILL.md changes in watched directories during the session. If you just created a top-level skills directory, run /reload-skills. Check that the skill is listed before testing its trigger.
- For Claude chat or Cowork in the Desktop app, manage uploaded skills in Customize > Skills; copying files into a local Claude Code folder is not a Desktop install. Other agents may use different install locations.
Full install guide for Claude, Cursor, and Codex →
Try a starter prompt
After installing the skill, paste this starter prompt into your agent to verify it triggers on a small task.
Use the Vercel skill for this task: Use Vercel when this documented workflow matches the task. Confirm any required inputs or files before making changes.
What supports this recommendation?
70/100 provisional content score. This measures documentation, practical detail and source signals. It is not a measured task success rate or a security certification.
- Documentation
- 77/100
- Practical detail
- 68/100
- Source evidence
- 63/100
- Source signals
- 70/100
Model compatibility evidence
- claudeuntested
No model-specific signal or recorded compatibility test was found.
- chatgptuntested
No model-specific signal or recorded compatibility test was found.
- geminiuntested
No model-specific signal or recorded compatibility test was found.
- copilotuntested
No model-specific signal or recorded compatibility test was found.
- llamauntested
No model-specific signal or recorded compatibility test was found.
- perplexityuntested
No model-specific signal or recorded compatibility test was found.
- mistraluntested
No model-specific signal or recorded compatibility test was found.
- grokuntested
No model-specific signal or recorded compatibility test was found.
Inferred compatibility is based on content signals. Check the app, its available tools and setup requirements before running a skill.
What this skill does
# Vercel Monitor
Monitor one immutable Vercel deployment for the `remotion` project and notify the current task when that exact deployment becomes ready or fails.
## Non-negotiable rules
- Never infer deployment state from an HTTP response. A branch preview alias can return 200 from the previous deployment while the new deployment is building. - Never monitor a branch preview alias. It is movable and can resolve to an older or newer deployment. - Pin the monitor to a Vercel deployment ID (`dpl_...`) or the immutable automatic deployment hostname (`<project>-<random>-<scope>.vercel.app`). - Read the machine-readable Vercel deployment state. Do not parse human CLI output. - Default to the `remotion` project and the `remotion` Vercel scope. Ignore the `bugs` project unless the user explicitly asks for it.
## Resolve the exact deployment
Prefer these sources, in order:
1. A Vercel deployment/dashboard URL supplied by the user. 2. The `Vercel – remotion` check on the active GitHub PR. Its dashboard URL has the form `https://vercel.com/remotion/remotion/<deployment-id-suffix>`. 3. The `remotion` row in the Vercel bot's PR comment. 4. `vercel list remotion --scope remotion --format=json`, matched to the exact PR, commit SHA, or branch in `.deployments[].meta`.
The final path segment of a dashboard URL becomes the deployment ID by prefixing it with `dpl_`. For example:
```text https://vercel.com/remotion/remotion/AbCd1234 -> dpl_AbCd1234 ```
The `Preview` link in a Vercel PR comment is normally a branch alias. Preserve it for the final notification, but do not use it for state checks.
When using `vercel list`, select the newest deployment that matches all available identity fields:
- `.name == "remotion"` - `.meta.githubPrId == <PR number>`, when a PR is known - `.meta.githubCommitSha == <full commit SHA>`, when a commit is known
Do not silently fall back to a different commit. If no exact deployment can be identified, ask for the Vercel dashboard URL, PR number, or commit SHA.
## Read state
Run the bundled checker from the repository root:
```bash python3 .agents/skills/vercel/scripts/check-deployment.py <deployment-id-or-url> ```
The checker calls:
```bash vercel inspect <deployment-id-or-immutable-url> \ --scope remotion \ --format=json ```
It validates the project, rejects moving aliases, and emits normalized JSON. Use its `state` field:
- `READY`: success. - `ERROR`, `CANCELED`, or `CANCELLED`: failure. - `BUILDING`, `QUEUED`, or `INITIALIZING`: still in progress. - `UNKNOWN`: not terminal. Report the diagnostic only if it persists or prevents creation of a trustworthy monitor.
HTTP probing may be used after `READY` as an optional reachability check. It must never promote a non-ready or unknown deployment to `READY`.
## Create the monitor
Use the Codex automation tool to create a one-minute heartbeat with a bounded count, normally 30 attempts. The heartbeat prompt must be self-contained and include:
- The pinned deployment ID or immutable deployment hostname. - The dashboard URL. - The branch preview alias, if known, for the final notification only. - The project, PR, branch, and commit context, if known. - The exact checker command. - The terminal-state rules above.
Use this prompt shape:
```text Monitor this exact Vercel deployment until it reaches a terminal state.
Pinned deployment: <dpl_id_or_immutable_hostname> Dashboard: <dashboard_url> Preview alias (reporting only; never use for state): <preview_url_or_unknown> Context: <project/pr/branch/commit>
From the repository root, run: python3 .agents/skills/vercel/scripts/check-deployment.py <pinned_deployment>
Only the JSON `state` is authoritative. - READY: reply "Vercel deployment is ready" and include Dashboard and Preview. - ERROR, CANCELED, or CANCELLED: reply with the failure state and include both links. - BUILDING, QUEUED, INITIALIZING, or UNKNOWN: stay quiet and check again next time.
Never curl the preview URL to determine readiness. After reporting a terminal state, delete or pause this heartbeat if its automation ID is available. ```
Before creating a heartbeat, run the checker once. If the deployment is already terminal, report immediately instead. Otherwise, tell the user which exact deployment is being watched and the cadence.
Intended uses
- Use Vercel when this documented workflow matches the task.
Implementation notes
- Review the source instructions and adapt inputs before running the workflow.
Try it, then tell us how it went
A copied prompt does not tell us whether the task worked. Report your result after checking the output. We collect your tool and outcome, never your files or prompt.