Load the Vercel CLI skill and help with Vercel project deployment, management, inspection, and troubleshooting.
Workflow
Step 1: Identify task type from user request
Use the decision tree in SKILL.md to select the relevant reference file.
Step 2: Read the reference file
Based on task type, read references/<topic>.md. Use vercel <command> --help for full flag details before using uncommon or risky flags.
Step 3: Execute task
Key things to verify:
- Run
vercel project inspect --non-interactivefrom the intended working directory and confirm the owner and project; stop onlink_requiredor a mismatch instead of treating.vercel/existence as proof - Use
vercel pullfor project settings and environment data under.vercel/; usevercel env pullfor.env.localor another file that is already excluded from source control - If login or team SAML re-authentication opens a browser/device flow, wait for deliberate user completion before continuing
- Use
--non-interactivefor prompt-free runs and--yesonly when confirmation is required - Use
VERCEL_TOKENenv var for auth (not--token) - Use first-class CLI commands before
vercel api - Use
vercel curlto access preview deployments; don't disable protection
Step 4: Summarize
Report the commands run, meaningful outputs, and any remaining permission, scope, or subscription limits.
<user-request> $ARGUMENTS </user-request>