skilld
All skills
vercel-labs avatar

/vercel-cli

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

Vercel CLI expert guidance. Use when deploying, managing environment variables, linking projects, viewing logs, querying metrics, managing domains, managing feature flags with vercel flags, or interacting with the Vercel platform from the command line.

  • 57 files
  • 222.1 KB
  • Updated 2 weeks ago
  • GitHub

Ask your Agent

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

This session only. Nothing lands on disk.

referencescomments.md

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

Vercel Toolbar Comments

vercel comments reviews and manages existing Vercel Toolbar comment threads from the terminal. Create new threads with the Vercel Toolbar.

Review comment threads

Without a subcommand, vercel comments runs list and returns unresolved threads for the linked project. It filters by the current Git branch when the project resolves through the current checkout and a branch can be inferred.

vercel comments --json
vercel comments inspect <thread> --json

list has the alias ls, while inspect has the alias get. Commands that act on a thread accept its ID or full vercel.com comment URL. A URL supplies its team unless --scope or --project overrides it.

Use --branch <branch> or --all-branches to set branch scope explicitly. Other list filters include --status, --page-path, --author, --content-id, and --search. The --author option accepts user IDs or me, but not usernames. Resolving me requires user authentication.

Reply and update threads

vercel comments reply <thread> -m 'Fixed in **main**.'
vercel comments resolve <thread> -m 'Fixed in the latest deployment.'
vercel comments resolve <thread-1> <thread-2> --yes
vercel comments reopen <thread> --yes

reply accepts Markdown from --message, --file, or standard input. Use --attach <url> repeatedly to add up to 10 HTTPS attachments. Attachments can form a reply without message text; local file uploads are not supported.

resolve and reopen accept multiple threads. Pass --yes for bulk operations in non-interactive or JSON mode. A closing --message is supported only when resolving one thread. Bulk operations continue after an individual failure and return a nonzero exit status if any operation fails.

Edit or delete messages

Inspect a thread to find its message IDs before editing or deleting a message.

vercel comments edit <thread> <message-id> -m 'Updated wording'
vercel comments delete <thread> <message-id> --yes

Editing message content preserves its attachments. Deleting a message cannot be undone and requires --yes in non-interactive or JSON mode.

Use JSON output

Both --json and --format json produce JSON with every subcommand except open. JSON mode never prompts for missing input or confirmation.

vercel comments --json | jq '.threads[].id'
vercel comments inspect <thread> --format json

Use vercel comments open <thread> to open a thread on vercel.com; this subcommand does not support JSON output.

Source: SKILL.md on GitHub

Third-party checks

No third-party reports yet.

Provenance

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

Last checked against GitHub 7 hours ago.

Activeupdated 2 weeks ago

Capability

Other metadata
metadata
{
  "priority": 4,
  "docs": [
    "https://vercel.com/docs/cli"
  ],
  "sitemap": "https://vercel.com/sitemap.xml",
  "pathPatterns": [
    "vercel.json",
    "vercel.ts",
    ".vercel/**",
    ".vercelignore",
    "now.json"
  ],
  "bashPatterns": [
    "^\\s*vercel(?:\\s|$)",
    "^\\s*vc(?:\\s|$)",
    "\\bnpx\\s+vercel\\b",
    "\\bpnpm\\s+dlx\\s+vercel\\b",
    "\\bbunx\\s+vercel\\b",
    "\\byarn\\s+dlx\\s+vercel\\b",
    "\\bnpx\\s+@vercel/config\\b"
  ],
  "promptSignals": {
    "phrases": [
      "check deployment",
      "check deploy",
      "deployment status",
      "deploy status",
      "vercel logs",
      "vercel metrics",
      "deployment logs",
      "deploy logs",
      "vercel inspect",
      "is it deployed",
      "deploy failing",
      "deploy failed",
      "deployment error",
      "check vercel",
      "vercel status"
    ],
    "allOf": [
      [
        "check",
        "deployment"
      ],
      [
        "check",
        "deploy"
      ],
      [
        "vercel",
        "status"
      ],
      [
        "vercel",
        "logs"
      ],
      [
        "vercel",
        "metrics"
      ],
      [
        "deploy",
        "error"
      ],
      [
        "deploy",
        "failed"
      ],
      [
        "deploy",
        "stuck"
      ]
    ],
    "anyOf": [
      "deployment",
      "deploy",
      "vercel",
      "production"
    ],
    "noneOf": [
      "terraform",
      "aws deploy",
      "heroku"
    ],
    "minScore": 6
  }
}
retrieval
{
  "aliases": [
    "vercel command line",
    "vc cli",
    "deploy command",
    "vercel terminal"
  ],
  "intents": [
    "deploy from cli",
    "link project",
    "manage domains",
    "view logs from terminal"
  ],
  "entities": [
    "vercel CLI",
    "vercel deploy",
    "vercel env",
    "vercel link",
    "vercel logs",
    "vercel metrics"
  ]
}
chainTo
[
  {
    "pattern": "\"functions\"\\s*:\\s*\\{|\"maxDuration\"\\s*:|\"memory\"\\s*:",
    "targetSkill": "vercel-functions",
    "message": "Functions configuration detected in vercel.json — loading Vercel Functions guidance for runtime options, streaming, and Fluid Compute.",
    "skipIfFileContains": "\"crons\"\\s*:"
  },
  {
    "pattern": "\"redirects\"\\s*:\\s*\\[|\"rewrites\"\\s*:\\s*\\[|\"headers\"\\s*:\\s*\\[",
    "targetSkill": "routing-middleware",
    "message": "Routing rules in vercel.json — loading Routing Middleware guidance for platform-level request interception patterns."
  }
]

README badge

README badge for vercel-labs/vercel-plugin/vercel-cli