Vercel CI Integration
jeremylongshore/tons-of-skills-marketplace
Configure Vercel CI/CD with GitHub Actions, preview deployments, and automated testing.
Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI.
$ npx skills add amondnet/vercel-action --skill use-vercel-action -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install amondnet/vercel-action use-vercel-action --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/amondnet/vercel-action.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/use-vercel-action .claude/skills/use-vercel-action && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "use-vercel-action" agent skill from https://github.com/amondnet/vercel-action/tree/master/skills/use-vercel-action into .claude/skills/use-vercel-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-vercel-action", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/amondnet/vercel-action/tree/master/skills/use-vercel-actionType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add amondnet/vercel-action --skill use-vercel-action -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install amondnet/vercel-action use-vercel-action --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amondnet/vercel-action.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/use-vercel-action .agents/skills/use-vercel-action && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "use-vercel-action" agent skill from https://github.com/amondnet/vercel-action/tree/master/skills/use-vercel-action into .agents/skills/use-vercel-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-vercel-action", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add amondnet/vercel-action --skill use-vercel-action -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install amondnet/vercel-action use-vercel-action --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amondnet/vercel-action.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/use-vercel-action .cursor/skills/use-vercel-action && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "use-vercel-action" agent skill from https://github.com/amondnet/vercel-action/tree/master/skills/use-vercel-action into .cursor/skills/use-vercel-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-vercel-action", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/amondnet/vercel-action.git --path skills/use-vercel-action--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add amondnet/vercel-action --skill use-vercel-action -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install amondnet/vercel-action use-vercel-action --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amondnet/vercel-action.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/use-vercel-action .gemini/skills/use-vercel-action && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "use-vercel-action" agent skill from https://github.com/amondnet/vercel-action/tree/master/skills/use-vercel-action into .gemini/skills/use-vercel-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-vercel-action", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install amondnet/vercel-action use-vercel-actionInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add amondnet/vercel-action --skill use-vercel-action -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/amondnet/vercel-action.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/use-vercel-action .github/skills/use-vercel-action && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "use-vercel-action" agent skill from https://github.com/amondnet/vercel-action/tree/master/skills/use-vercel-action into .github/skills/use-vercel-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-vercel-action", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add amondnet/vercel-action --skill use-vercel-action -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install amondnet/vercel-action use-vercel-action --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/amondnet/vercel-action.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/use-vercel-action .opencode/skills/use-vercel-action && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "use-vercel-action" agent skill from https://github.com/amondnet/vercel-action/tree/master/skills/use-vercel-action into .opencode/skills/use-vercel-action/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "use-vercel-action", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
use-vercel-actionWire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI.
Use Vercel Action is an agent skill from amondnet/vercel-action. Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI. Use when the user asks to deploy to Vercel from GitHub Actions, add Vercel preview deploys, post a Vercel preview URL on a PR, configure prebuilt Vercel deployments, set up alias domains for previews, create a GitHub Deployment for Vercel, or migrate off Vercel's native GitHub integration. Covers required tokens/IDs, the CLI vs experimental-API modes, prebuilt flows, alias placeholders, deprecated zeit-/now- aliases, and…
Its SKILL.md is about 2.7k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in DevOps & Cloud, covering Deployment and CI/CD. It works with Vercel, GitHub and GitHub Actions. The repository describes itself as: This action make a deployment with github actions instead of Vercel builder. The licence is MIT.
4 steps, taken from the first numbered list in SKILL.md.
Read from SKILL.md and the folder at commit 9471a56. It shows what the files ask for, not the result of running them.
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Shell commands in SKILL.md call:
vercelnpmFrom the folder's file list and the shell code blocks in SKILL.md.
Links to these hosts (documentation or services it may open):
vercel.comFrom URLs in SKILL.md, links to its own repository left out.
Names these keys or tokens, usually read from environment variables:
VERCEL_TOKENGITHUB_TOKENFrom names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Use Vercel Action loads about 2.7k tokens when it runs. Until then it costs about 154 tokens; SKILL.md has 901 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
The full file from amondnet/vercel-action at commit 9471a56, republished under its MIT licence (© amondnet). 901 words, ~2,676 tokens.
.claude/skills/use-vercel-action/SKILL.md (or your agent's skills folder).This skill teaches an agent how to consume amondnet/vercel-action correctly. Inputs and outputs documented here come from action.yml in this repo — when in doubt, open action.yml for the full surface.
amondnet/vercel-action to a workflow for the first time.Consumers consistently miss these. Verify each before writing the workflow:
Disable Vercel's native auto-deploys in the project repo, otherwise both Vercel and the action will deploy and you'll get duplicate previews. Add to vercel.json (or vercel.ts):
{ "git": { "deploymentEnabled": false } }Legacy projects may instead use the older { "github": { "enabled": false } } — both are accepted.
Link the project locally and capture the IDs. Run vercel link once on a developer machine; this writes .vercel/project.json with projectId and orgId. Store those values as GitHub repository secrets:
VERCEL_TOKEN — created at https://vercel.com/account/tokensVERCEL_ORG_ID — from .vercel/project.jsonVERCEL_PROJECT_ID — from .vercel/project.jsonDo not commit raw IDs into workflow files; reference them via ${{ secrets.* }}.
GitHub Deployments need explicit permission. If you set github-deployment: true, the workflow job must declare permissions: deployments: write (and usually contents: read). Without it the deployment write call fails.
Action runtime is Node 24. No consumer-side Node setup is needed for the action itself — the runner provides it.
name: Preview Deploy
on:
pull_request:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: amondnet/vercel-action@v42
with:
vercel-token: ${{ secrets.VERCEL_TOKEN }}
vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
github-token: ${{ secrets.GITHUB_TOKEN }}github-token is what enables the action to comment the preview URL on the PR. Omit it (or set github-comment: false) if you don't want the comment.
on:
push:
branches: [main]
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: amondnet/vercel-action@v42
with:
vercel-token: ${{ secrets.VERCEL_TOKEN }}
vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
vercel-args: --prodBuild with the Vercel CLI in a prior step, then deploy the prebuilt output. Best when you need to share the build artifact with other steps (tests, smoke checks).
- run: npm install --global vercel@latest
- run: vercel pull --yes --environment=preview --token=${{ secrets.VERCEL_TOKEN }}
env:
VERCEL_ORG_ID: ${{ secrets.VERCEL_ORG_ID }}
VERCEL_PROJECT_ID: ${{ secrets.VERCEL_PROJECT_ID }}
- run: vercel build --token=${{ secrets.VERCEL_TOKEN }}
env:
VERCEL_ORG_ID: ${{ secrets.VERCEL_ORG_ID }}
VERCEL_PROJECT_ID: ${{ secrets.VERCEL_PROJECT_ID }}
- uses: amondnet/vercel-action@v42
with:
vercel-token: ${{ secrets.VERCEL_TOKEN }}
vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
prebuilt: trueThe npm install --global vercel@latest step is required on a fresh runner — the Vercel CLI is not preinstalled on GitHub-hosted runners.
vercel-build: true runs vercel pull + vercel build inside the action and then deploys the prebuilt output. Simpler — one step total — but you can't reuse the build artifact elsewhere.
- uses: amondnet/vercel-action@v42
with:
vercel-token: ${{ secrets.VERCEL_TOKEN }}
vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
vercel-build: truealias-domains accepts one domain per line and substitutes {{PR_NUMBER}} and {{BRANCH}}. The domains must already exist on the Vercel project.
- uses: amondnet/vercel-action@v42
with:
vercel-token: ${{ secrets.VERCEL_TOKEN }}
vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
alias-domains: |
pr-{{PR_NUMBER}}.preview.example.com
{{BRANCH}}.preview.example.comWhen alias domains are present the preview-url output is the first alias rather than the raw deployment URL.
permissions:
contents: read
deployments: write
jobs:
deploy:
runs-on: ubuntu-latest
steps:
- uses: actions/checkout@v4
- uses: amondnet/vercel-action@v42
id: vercel
with:
vercel-token: ${{ secrets.VERCEL_TOKEN }}
vercel-org-id: ${{ secrets.VERCEL_ORG_ID }}
vercel-project-id: ${{ secrets.VERCEL_PROJECT_ID }}
github-token: ${{ secrets.GITHUB_TOKEN }}
github-deployment: true
# Optional override; otherwise auto-derived from vercel-args.
# github-deployment-environment: staging
- run: echo "Deployment id ${{ steps.vercel.outputs.deployment-id }}"Deployment lifecycle: created in_progress before deploy, then transitioned to success (with the preview/alias URL as the environment URL) or failure. Previous deployments to the same environment are auto-deactivated.
| Input | Required | Notes |
|---|---|---|
vercel-token | yes | Vercel personal token. |
vercel-org-id | yes | Required for Vercel CLI 17+. Works for both CLI and API modes — prefer over scope. |
vercel-project-id | yes | Required for Vercel CLI 17+. |
vercel-args | no | Ad-hoc CLI flags (e.g. --prod, --force). Mutually exclusive with experimental-api and vercel-build. |
working-directory | no | Run the deploy from a subdirectory. |
alias-domains | no | Multi-line list; supports {{PR_NUMBER}} and {{BRANCH}}. |
prebuilt | no | Deploy a prebuilt .vercel/output directory. Mutually exclusive with vercel-build. |
vercel-build | no | Run vercel pull + vercel build inside the action. Mutually exclusive with prebuilt and vercel-args. |
vercel-output-dir | no | Override the prebuilt output path. Defaults to {working-directory}/.vercel/output when prebuilt: true. |
github-token | no | Needed for PR/commit comments. |
github-comment | no | true (default), false, or a custom comment string. |
github-deployment | no | true to create a GitHub Deployment. Requires permissions: deployments: write. |
github-deployment-environment | no | Override the auto-derived environment name. |
For the long tail (target, force, env, build-env, regions, archive, root-directory, auto-assign-custom-domains, custom-environment, public, with-cache, scope, vercel-version, vercel-project-name, experimental-api) read action.yml — every input there is the source of truth.
| Output | Set when | Notes |
|---|---|---|
preview-url | always | Raw deployment URL, or the first alias domain if alias-domains is set. |
preview-name | always | Deployment name (resolved via vercel inspect). |
deployment-id | only when github-deployment: true | GitHub Deployment ID — useful for follow-up status updates. |
experimental-api: true cannot be combined with vercel-args. The API client uses @vercel/client, an internal Vercel package without semver guarantees — keep CLI mode (the default) unless the user explicitly wants the typed inputs (target, regions, env, build-env, public, with-cache, custom-environment, auto-assign-custom-domains).prebuilt cannot be combined with vercel-build. Pick exactly one prebuilt flow.vercel-build: true cannot be combined with a non-empty vercel-args. The action throws at config-parse time with a clear error — vercel-build deploys the locally produced .vercel/output via the prebuilt path, while vercel-args routes through the CLI path which would ignore that output.scope is CLI-mode only. Prefer vercel-org-id so the same workflow works in both modes.production if vercel-args contains --prod or --production, otherwise preview. Experimental API mode: derived from target (production or preview). Set github-deployment-environment explicitly for staging and similar in either mode.zeit-token → vercel-token, now-args → vercel-args, now-project-id → vercel-project-id, now-org-id → vercel-org-id. Always rewrite to the modern names.VERCEL_TELEMETRY_DISABLED=1 and exports VERCEL_ORG_ID / VERCEL_PROJECT_ID from the corresponding inputs — don't redeclare them in env: for the action step itself.action.yml — full input/output contract (source of truth).README.md — additional examples and a longer changelog.VERCEL_TOKEN secret.© amondnet, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/use-vercel-action of amondnet/vercel-action.
Open the folder on GitHubat commit 9471a56
Use Vercel Action next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Use Vercel Action this skillamondnet/vercel-action | 764 | — | ~2.7k | Automated safety check: Pass | MIT | |
| Vercel CI Integrationjeremylongshore/tons-of-skills-marketplace | 2.8k | — | ~1.9k | Automated safety check: Pass | MIT | |
| AI News RadarLearnPrompt/ai-news-radar | 1.8k | — | ~2.5k | Automated safety check: Notes | MIT | |
| Prepare Cloudflare Production DeploymentLubomirGeorgiev/cloudflare-workers-nextjs-saas-template | 786 | — | ~5.9k | Automated safety check: Notes | MIT | |
| Deployments Cicdvercel/vercel-plugin | 301 | 1 repos | ~3k | Automated safety check: Pass | Custom licence | |
| GitHub Actions Docsdevantler-tech/ksail | 165 | 2 repos | ~1.3k | Automated safety check: Pass | Custom licence |
jeremylongshore/tons-of-skills-marketplace
Configure Vercel CI/CD with GitHub Actions, preview deployments, and automated testing.
LearnPrompt/ai-news-radar
A skill your agent uses when working on AI News Radar, 24 小时 AI 更新雷达, AI 更新雷达, 伯乐Skill, or Scout Skill: finding high-signal AI/tech sources, adding RSS/OPML/GitHub feeds, checking source health…
LubomirGeorgiev/cloudflare-workers-nextjs-saas-template
Source-of-truth runbook for preparing this Vinext Cloudflare Workers SaaS template for production deployment.
vercel/vercel-plugin
Vercel deployment and CI/CD expert guidance. An agent skill from vercel/vercel-plugin.
devantler-tech/ksail
A skill your agent uses when users ask how to write, explain, customize, migrate, secure, or troubleshoot GitHub Actions workflows, workflow syntax, triggers, matrices, runners, reusable workflows…
EliasOulkadi/shokunin
Design CI/CD pipelines for GitHub Actions, GitLab CI, and CircleCI with matrix builds, test sharding, caching, Docker layer caching, OIDC auth, deployment strategies (rolling, blue-green, canary)…
Works with
Categories
Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI. Use Vercel Action is an agent skill from amondnet/vercel-action. Wire amondnet/vercel-action into a GitHub Actions workflow to deploy Vercel projects from CI.
Use Vercel Action fits situations like: the user asks to deploy to Vercel from GitHub Actions; add Vercel preview deploys; post a Vercel preview URL on a PR; configure prebuilt Vercel deployments.
Run `npx skills add amondnet/vercel-action --skill use-vercel-action -a claude-code`. Or copy the skill folder (skills/use-vercel-action in amondnet/vercel-action) into .claude/skills/use-vercel-action in your project. Claude Code loads it when a task matches its description.
Run `npx skills add amondnet/vercel-action --skill use-vercel-action -a codex`. Or copy the skill folder (skills/use-vercel-action in amondnet/vercel-action) into .agents/skills/use-vercel-action in your project. Codex loads it when a task matches its description.
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add amondnet/vercel-action --skill use-vercel-action -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/use-vercel-action, .gemini/skills/use-vercel-action, .github/skills/use-vercel-action and .opencode/skills/use-vercel-action in your project.
Going by SKILL.md and its folder, Use Vercel Action needs the command-line tools its instructions call (vercel and npm) and credentials named VERCEL_TOKEN and GITHUB_TOKEN. Our summary lists: Node.js; A credential in VERCEL_TOKEN; A credential in GITHUB_TOKEN.
SKILL.md names 1 domain. As links in the text: vercel.com. This is read from the text; nothing was executed.
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
Use Vercel Action is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.
About 2.7k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
Skills that share tags, products or a category with Use Vercel Action: Vercel CI Integration (jeremylongshore/tons-of-skills-marketplace, 2.8k stars), AI News Radar (LearnPrompt/ai-news-radar, 1.8k stars), Prepare Cloudflare Production Deployment (LubomirGeorgiev/cloudflare-workers-nextjs-saas-template, 786 stars) and Deployments Cicd (vercel/vercel-plugin, 301 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
amondnet (a GitHub user) maintains it in amondnet/vercel-action, which has 764 GitHub stars. The repository was last updated on July 20, 2026.
Source: amondnet/vercel-action on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.