skilld
All skills
vercel-labs avatar

/deployments-cicd

@b06012d official
by Vercel Labsvercel-labs/vercel-plugin295 stars
64

Vercel deployment and CI/CD expert guidance. Use when deploying, promoting, rolling back, inspecting deployments, building with --prebuilt, or configuring CI workflow files for Vercel.

  • 5 files
  • 19.5 KB
  • Updated 15 hours ago
  • GitHub

Ask your Agent

Use this Skill: https://skilld.dev/gh/vercel-labs/vercel-plugin/deployments-cicd

This session only. Nothing lands on disk.

referenceslive-status.md

≈363 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Live Deployment Status

The Vercel MCP server's open_deployments tool shows deployments as a live card. Hosts that support MCP Apps (ChatGPT, Codex) render a card that updates while the build runs; other hosts receive a text summary. Use it instead of polling vercel inspect when it's available.

The user wants Call open_deployments with
The build or preview for the current branch or commit view: "preview", branch, sha
A project's recent deployments view: "dashboard", projectId, optionally target (production or preview) or branch
  • Read projectId and teamId (orgId) from .vercel/project.json. Without that file, pass repo (git remote get-url origin) for a preview: the tool finds the linked project, even before the deployment exists. A project name also works as projectId.
  • Get branch from git rev-parse --abbrev-ref HEAD and sha from git rev-parse HEAD.
  • Call it right after pushing a branch or running vercel deploy. Calling again updates the same card, so call it once: it updates by itself until the build finishes.
  • A repository linked to several Vercel projects shows a project chooser in the card.
  • When a build fails, the card's Send Logs to Chat button asks the agent to investigate. Call get_deployment_build_logs with the deployment ID, and if that is not enough, use get_deployment, get_runtime_logs, or reproduce the build locally.

Source: SKILL.md on GitHub

Third-party checks

No third-party reports yet.

Provenance

Signed by skilld at b06012d. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 11 hours ago.

Activeupdated 15 hours ago

Capability

Other metadata
metadata
{
  "priority": 6,
  "docs": [
    "https://vercel.com/docs/deployments",
    "https://vercel.com/docs/git",
    "https://vercel.com/docs/deployments/promoting-a-deployment",
    "https://vercel.com/docs/deployment-checks"
  ],
  "sitemap": "https://vercel.com/sitemap.xml",
  "pathPatterns": [
    ".github/workflows/*.yml",
    ".github/workflows/*.yaml",
    ".gitlab-ci.yml",
    "bitbucket-pipelines.yml",
    "vercel.json",
    "apps/*/vercel.json"
  ],
  "bashPatterns": [
    "\\bvercel\\s+deploy\\b",
    "\\bvercel\\s+--prod\\b",
    "\\bvercel\\s+promote\\b",
    "\\bvercel\\s+rollback\\b",
    "\\bvercel\\s+inspect\\b",
    "\\bvercel\\s+build\\b",
    "\\bvercel\\s+deploy\\s+--prebuilt\\b"
  ]
}
validate
[
  {
    "pattern": "cron:\\s*['\"]|from\\s+['\"](node-cron)['\"]|cron\\.schedule\\(",
    "message": "Manual cron scheduling detected. Use Vercel Cron Jobs (vercel.json crons) for platform-native scheduled tasks.",
    "severity": "recommended",
    "skipIfFileContains": "vercel\\.json.*crons|@vercel/cron"
  }
]
retrieval
{
  "aliases": [
    "deploy",
    "ci cd",
    "continuous deployment",
    "release pipeline"
  ],
  "intents": [
    "deploy to vercel",
    "set up ci cd",
    "promote deployment",
    "rollback deploy"
  ],
  "entities": [
    "vercel deploy",
    "preview",
    "production",
    "rollback",
    "promote",
    "CI workflow"
  ]
}

README badge

README badge for vercel-labs/vercel-plugin/deployments-cicd