# Manage Vercel Deployments and CLI Workflows

Vercel operations can target the wrong project or confuse incomplete telemetry with successful execution. This skill guides scoped CLI workflows with credential safeguards and explicit verification.

## Install

```bash
npx skillstore add vercel/vercel-cli
```

## Metadata

- Status: approved
- Slug: vercel-vercel-cli
- Skillstore revision: r1
- Version status: missing
- Tree hash: dc770c65242ddaf47150474ec5c9a64f630926f89f3dad95ecdb30bb9bfa6d9e
- Author: vercel
- GitHub username: vercel
- Repository: https://github.com/vercel/vercel/tree/84878e532142f0ac584953695658b324eb9e5b80/skills/vercel-cli
- Ref: c993c6abcbffafea2683d7748b53b3dfaf438415
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem, network, external\_commands
- Quality score: 71
- Public page: https://skillstore.pages.dev/skills/vercel-vercel-cli
- Manifest: https://skillstore.pages.dev/api/skills/vercel-vercel-cli/manifest

## Capabilities

- Guide source, prebuilt, and redeployment workflows while preserving deployment identity through verification and promotion.
- Explain local project links, repository mappings, and explicit project or team targeting.
- Structure build investigations using deployment metadata, logs, source inputs, and cache evidence.
- Guide bounded log, metric, and trace queries with pagination and coverage checks.
- Explain environment pulls, secret redaction, Blob authentication precedence, and storage connection changes.
- Select task-specific references and use installed CLI help or scoped API discovery for command details.

## Use Cases

- Validate an Application Deployment: Choose the correct source or prebuilt path, verify the target project, and check the deployment state before promotion.
- Investigate a Production Regression: Inspect the supplied deployment, query the affected time window, and distinguish observed failures from telemetry gaps.
- Configure Monorepo Delivery: Check repository mappings, align build and deployment environments, and verify artifact completeness across CI jobs.

## Prompt Templates

### Check CLI Readiness

```
Check the installed Vercel CLI and explain its help for inspecting a deployment. Do not install, upgrade, authenticate, or change resources.
```

### Prepare a Preview Deployment

```
Prepare a preview deployment from [app directory]. Verify the resolved team and project first. Explain the source choice and request approval before deploying.
```

### Diagnose a Failed Deployment

```
Investigate [deployment URL] during [time window]. Inspect metadata and build logs, then relevant telemetry. Separate proven causes from hypotheses. Do not mutate resources.
```

### Review a Monorepo CI Workflow

```
Review [app directory] for a split build/deploy CI workflow. Verify mappings, environment consistency, and artifact completeness. Propose changes without applying them or revealing credentials.
```

## Limitations

- This skill provides workflow guidance, not a bundled Vercel CLI installation or authenticated account.
- Available commands and output formats depend on the installed CLI version.
- Telemetry access depends on permissions, subscription features, retention, and network reachability.
- Authentication, purchases, and destructive operations can require user interaction or explicit authorization.

## Best Practices

- Verify the resolved team, project, and environment before pulling data or changing resources.
- Use installed CLI help, preserve the chosen version, and keep credentials out of arguments and output.
- Check final deployment states, pagination, and telemetry coverage before reporting success or absence.

## Anti Patterns

- Assuming an application directory name or successful login proves the intended project target.
- Treating non-interactive mode, suggested commands, or API access as permission to mutate resources.
- Disabling deployment protection or bypassing confirmation to work around access limitations.

## Security Audit

- Audited at: 2026-11-06T15:33:27.34\+00:00
- Summary: All 28 static findings are false positives involving documentation links, Markdown formatting, or legitimate Vercel workflows with explicit safeguards. No evidence found of credential exfiltration, unauthorized reconnaissance, or prompt injection in the reviewed files. Actual operations still require appropriate credentials, verified targets, and user authorization.

## Stats

- Views: 0
- Downloads: 0
- Favorites: 0
- Popularity score: 0