Update to Vercel

{
  "name": "vercel-cli",
  "description": "Vercel CLI expert guidance. Use when deploying, managing environment variables, linking projects, viewing logs, querying metrics, managing domains, or interacting with the Vercel platform from the command line.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 90
    },
    {
      "relative_path": "references/advanced.md",
      "size_in_bytes": 882
    },
    {
      "relative_path": "references/bun.md",
      "size_in_bytes": 1195
    },
    {
      "relative_path": "references/ci-automation.md",
      "size_in_bytes": 1537
    },
    {
      "relative_path": "references/deployment.md",
      "size_in_bytes": 1747
    },
    {
      "relative_path": "references/domains-and-dns.md",
      "size_in_bytes": 896
    },
    {
      "relative_path": "references/environment-variables.md",
      "size_in_bytes": 1084
    },
    {
      "relative_path": "references/flags.md",
      "size_in_bytes": 3491
    },
    {
      "relative_path": "references/getting-started.md",
      "size_in_bytes": 1371
    },
    {
      "relative_path": "references/global-options.md",
      "size_in_bytes": 703
    },
    {
      "relative_path": "references/integrations.md",
      "size_in_bytes": 7564
    },
    {
      "relative_path": "references/local-development.md",
      "size_in_bytes": 913
    },
    {
      "relative_path": "references/monitoring-and-debugging.md",
      "size_in_bytes": 2360
    },
    {
      "relative_path": "references/monorepos.md",
      "size_in_bytes": 2995
    },
    {
      "relative_path": "references/node-backends.md",
      "size_in_bytes": 2719
    },
    {
      "relative_path": "references/projects-and-teams.md",
      "size_in_bytes": 1068
    },
    {
      "relative_path": "references/storage.md",
      "size_in_bytes": 821
    }
  ],
  "skill_md_contents": "---\nname: vercel-cli\ndescription: Vercel CLI expert guidance. Use when deploying, managing environment variables, linking projects, viewing logs, querying metrics, managing domains, or interacting with the Vercel platform from the command line.\nmetadata:\n  priority: 4\n  docs:\n    - \"https://vercel.com/docs/cli\"\n  sitemap: \"https://vercel.com/sitemap/docs.xml\"\n  pathPatterns:\n    - 'vercel.json'\n    - 'vercel.ts'\n    - '.vercel/**'\n    - '.vercelignore'\n    - 'now.json'\n  bashPatterns:\n    - '^\\s*vercel(?:\\s|$)'\n    - '^\\s*vc(?:\\s|$)'\n    - '\\bnpx\\s+vercel\\b'\n    - '\\bpnpm\\s+dlx\\s+vercel\\b'\n    - '\\bbunx\\s+vercel\\b'\n    - '\\byarn\\s+dlx\\s+vercel\\b'\n    - '\\bnpx\\s+@vercel/config\\b'\n  promptSignals:\n    phrases:\n      - \"check deployment\"\n      - \"check deploy\"\n      - \"deployment status\"\n      - \"deploy status\"\n      - \"vercel logs\"\n      - \"vercel metrics\"\n      - \"deployment logs\"\n      - \"deploy logs\"\n      - \"vercel inspect\"\n      - \"is it deployed\"\n      - \"deploy failing\"\n      - \"deploy failed\"\n      - \"deployment error\"\n      - \"check vercel\"\n      - \"vercel status\"\n    allOf:\n      - [check, deployment]\n      - [check, deploy]\n      - [vercel, status]\n      - [vercel, logs]\n      - [vercel, metrics]\n      - [deploy, error]\n      - [deploy, failed]\n      - [deploy, stuck]\n    anyOf:\n      - \"deployment\"\n      - \"deploy\"\n      - \"vercel\"\n      - \"production\"\n    noneOf:\n      - \"terraform\"\n      - \"aws deploy\"\n      - \"heroku\"\n    minScore: 6\n---\n\n# Vercel CLI Skill\n\nThe Vercel CLI (`vercel` or `vc`) deploys, manages, and develops projects on the Vercel platform from the command line. Use `vercel <command> -h` for full flag details on any command.\n\n## Critical: Project Linking\n\nCommands must be run from the directory containing the `.vercel` folder (or a subdirectory of it). How `.vercel` gets set up depends on your project structure:\n\n- **`.vercel/project.json`**: Created by `vercel link`. Links a single project. Fine for single-project repos, and can work in monorepos if there's only one project.\n- **`.vercel/repo.json`**: Created by `vercel link --repo`. Links a repo that may contain multiple projects. Always a good idea when any project has a non-root directory (e.g., `apps/web`).\n\nRunning from a project subdirectory (e.g., `apps/web/`) skips the \"which project?\" prompt since it's unambiguous.\n\n**When something goes wrong, check how things are linked first** — look at what's in `.vercel/` and whether it's `project.json` or `repo.json`. Also verify you're on the right team with `vercel whoami` — linking while on the wrong team is a common mistake.\n\n## Quick Start\n\n```bash\nnpm i -g vercel\nvercel login\nvercel link              # single project\n# OR\nvercel link --repo       # monorepo\nvercel pull\nvercel dev        # local development\nvercel deploy     # preview deployment\nvercel --prod     # production deployment\n```\n\n## Decision Tree\n\nUse this to route to the correct reference file:\n\n- **Deploy** → `references/deployment.md`\n- **Local development** → `references/local-development.md`\n- **Environment variables** → `references/environment-variables.md`\n- **CI/CD automation** → `references/ci-automation.md`\n- **Domains or DNS** → `references/domains-and-dns.md`\n- **Projects or teams** → `references/projects-and-teams.md`\n- **Logs, metrics, debugging, or accessing preview deploys** → `references/monitoring-and-debugging.md`\n- **Blob storage** → `references/storage.md`\n- **Integrations (databases, storage, etc.)** → `references/integrations.md`\n- **Access a preview deployment** → use `vercel curl` (see `references/monitoring-and-debugging.md`)\n- **CLI doesn't have a command for it** → use `vercel api` as a fallback (see `references/advanced.md`)\n- **Node.js backends (Express, Hono, etc.)** → `references/node-backends.md`\n- **Monorepos (Turborepo, Nx, workspaces)** → `references/monorepos.md`\n- **Bun runtime** → `references/bun.md`\n- **Feature flags** → `references/flags.md`\n- **Advanced (API, webhooks)** → `references/advanced.md`\n- **Global flags** → `references/global-options.md`\n- **First-time setup** → `references/getting-started.md`\n\n## Anti-Patterns\n\n- **Wrong link type in monorepos with multiple projects**: `vercel link` creates `project.json`, which only tracks one project. Use `vercel link --repo` instead. When things break, check `.vercel/` first.\n- **Letting commands auto-link in monorepos**: Many commands implicitly run `vercel link` if `.vercel/` doesn't exist. This creates `project.json`, which may be wrong. Run `vercel link` (or `--repo`) explicitly first.\n- **Linking while on the wrong team**: Use `vercel whoami` to check, `vercel teams switch` to change.\n- **Forgetting `--yes` in CI**: Required to skip interactive prompts.\n- **Using `vercel deploy` after `vercel build` without `--prebuilt`**: The build output is ignored.\n- **Hardcoding tokens in flags**: Use `VERCEL_TOKEN` env var instead of `--token`.\n- **Disabling deployment protection**: Use `vercel curl` instead to access preview deploys.\n\n## Related Skills in This Plugin\n\n- **Log drains and observability vendor setup** → `⤳ skill: observability`\n- **Feature flag configuration and adapter patterns** → `⤳ skill: vercel-flags`\n"
}