Deploy applications and manage projects with complete CLI reference. Commands for deployments, projects, domains, environment variables, and live documentation access.
Security Analysis
high confidenceThe skill is an instruction-only Vercel CLI reference whose required resources (vercel, curl) and instructions match its stated purpose; nothing requested appears disproportionate or unrelated.
The name/description promise (Vercel CLI reference and deployment management) aligns with the declared requirements: the vercel binary is required and curl is used for fetching docs. There are no unrelated binaries, environment variables, or config paths requested.
SKILL.md stays within the Vercel CLI domain: it documents commands for deploys, projects, domains, env vars, logs, and uses curl to fetch docs. It includes examples that manipulate environment variables (e.g., `vercel env pull .env.local`) and mentions auth token flags (`-t, --token`) — these are legitimate for Vercel usage but mean the agent running the commands could read or write sensitive data (account tokens, pulled .env files).
No install spec is present (instruction-only), so nothing is downloaded or written by the skill itself. This is the lowest-risk model for an integration that simply documents CLI usage.
The skill declares no required environment variables, which is proportional. However, the documented commands rely on Vercel authentication (login or tokens stored in CLI config or passed with -t) and can pull/write environment secrets to disk with `vercel env pull`. Users should be aware the agent's environment or existing vercel auth state will be used if available.
always:false and default model invocation are set. The skill does not request permanent/always-on inclusion and does not attempt to modify other skills or system-wide config; its privilege level is appropriate for its purpose.
Guidance
This is a documentation-only skill for the official Vercel CLI and appears coherent. Before installing: (1) ensure the vercel binary on your system is the official CLI (not a malicious replacement), (2) be careful when invoking commands that manage or pull environment variables—`vercel env pull` will write secrets to disk—and avoid running those commands in environments you don't trust, (3) remember the CLI will use any existing Vercel auth (stored tokens or config); if an agent has access to those tokens it could perform actions on your Vercel account, and (4) some examples pipe to jq or other tools not listed as required; those are optional examples and not installed by this skill. If you want tighter control, restrict autonomous invocation or run Vercel commands manually instead of allowing the agent to run them.
Latest Release
v0.1.0
Initial release of lb-vercel-skill. - Provides a complete Vercel CLI command and documentation reference. - Covers deployments, projects, domains, environment variables, authentication, teams, and more. - Includes quick reference tables and examples for common Vercel tasks. - Enables fast documentation lookup via curl commands for markdown docs and sitemap. - Specifies required binaries: vercel and curl.
More by @leonaaardob
Published by @leonaaardob on ClawHub
