Vercel Platform

v1.0.1

Deploy applications and manage projects with complete CLI reference. Commands for deployments, projects, domains, environment variables, and live documentation access.

22· 9.1k·95 current·97 all-time
bySeth Rose@thesethrose
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
VirusTotalVirusTotal
Benign
View report →
OpenClawOpenClaw
Benign
high confidence
Purpose & Capability
Name/description match the requested binaries and the documented actions. Requiring the vercel CLI and curl is appropriate for a Vercel CLI reference and documentation fetcher.
Instruction Scope
SKILL.md stays on-topic, listing vercel and curl commands for deployments, projects, domains, env vars and docs. Note: it documents commands that can read or write secrets (e.g., `vercel env pull .env.local` and use of `-t, --token`), so running commands could expose or persist credentials/secrets — this is expected for the tool but worth caution.
Install Mechanism
No install spec (instruction-only), so nothing is fetched or written by the skill itself. This minimizes install risk; the skill assumes the vercel binary is already installed.
Credentials
The skill declares no required environment variables or credentials. The documentation mentions how the CLI uses tokens and login flows (expected), but the skill itself does not request or store secrets.
Persistence & Privilege
always:false and default model-invocation settings are appropriate. The skill does not request persistent presence or attempt to modify other skills or system-wide settings.
Assessment
This skill is an on-topic CLI reference for the Vercel tool and is coherent with what it asks for. Before using it, ensure you actually have the vercel binary from a trusted source installed; be cautious when running commands that handle environment variables or tokens (for example, `vercel env pull .env.local` will write secret values to a local file and `-t/--token` exposes an auth token on the command line). If you do not want an agent to perform operations that might expose secrets, run the commands yourself in a terminal instead of letting an automated agent execute them.

Like a lobster shell, security has layers — review code before you run it.

clivk975e14jcnnyj4vhq4se3zwkvs7z7437deploymentvk975e14jcnnyj4vhq4se3zwkvs7z7437latestvk975e14jcnnyj4vhq4se3zwkvs7z7437vercelvk975e14jcnnyj4vhq4se3zwkvs7z7437

License

MIT-0
Free to use, modify, and redistribute. No attribution required.

Runtime requirements

Clawdis
Binsvercel, curl

Comments