A non-interactive environment needs Vercel access
Use an existing secret-managed token without relying on an interactive vercel login session.
Vercel CLI with Tokens by Vercel Labs
Use Vercel CLI with Tokens by Vercel Labs to guide deployment and project management with token-based authentication. Identify the approved credential source, confirm the project and team, and carry out the requested CLI task without depending on an interactive login or exposing token values in reports.
Install and get started
Choose your agent to see how to get started. In Floatboat, copy a request that asks the agent to read the original instructions. Other options show the Skill installation command or the publisher’s native setup steps.
Choose an agent
Start in Floatboat
Copy the request into a Floatboat conversation
Read the original Vercel CLI with Tokens instructions at https://github.com/vercel-labs/agent-skills/blob/main/skills/vercel-cli-with-tokens/SKILL.md. Explain its purpose, required tools, and installation options, then help me use it.Let the agent read the original instructions and check how to use them in your environment.
Download Floatboat ↗Try this request
Use the approved Vercel token to inspect this project's environment settings. Confirm project and team IDs first; never print the token.
About Vercel CLI with Tokens
Vercel CLI with Tokens is an Agent Skill for Vercel CLI work where an access token is the chosen authentication method. It guides the agent to locate the existing credential source, resolve project and organization identifiers, and perform the requested deployment or management task in the intended scope. This is useful in non-interactive environments or when project access is supplied through managed secrets. Authentication alone does not identify which project an action should affect. The source also warns against putting tokens in command-line arguments. Installing the Skill does not create a token or grant access; those remain account and environment prerequisites.
Use Cases for Vercel CLI with Tokens
Explore CLI tasks in environments that already use an authorized Vercel token. Connect a CI job, target the right project when one credential reaches several scopes, or review credential handling before deployment and environment-variable management in a non-interactive workflow.
One token can reach multiple projects
Confirm project and organization identifiers before changing environment variables or deploying.
A command could expose a secret
Keep tokens out of pasted commands, logs, and review comments; use the approved environment mechanism.
How to Use Vercel CLI with Tokens
Identify the approved token source without exposing its value, then verify the target project and organization. Ask the agent to perform only the requested CLI operation in that scope, and check the resulting deployment or configuration while keeping credentials out of the report.
- 01
Confirm the credential source
Identify the approved environment or secret store used for authentication. Keep the token value out of prompts, copied commands, and reports.
- 02
Resolve project and organization
Check project identifiers and team scope before any change. Compare them with the Vercel project the user intends to manage.
- 03
Run and verify the operation
Ask the agent to carry out the requested CLI task in the confirmed scope. Verify the result without including secrets in logs or summaries.
Explore More Agent Skills
Read another Skill guide and check its original source before using it.
Vercel CLI with Tokens FAQ
Does the Skill give me a Vercel token?
No. It guides use of an existing, authorized token. Creating or granting access is separate account work.
Can I paste a token into the prompt?
Avoid it. Use your approved secret-management environment and keep token values out of chat, commands, and reports.
Why check both project and organization?
A valid token may cover multiple scopes. Authentication alone does not prove that a CLI command points to the intended project.
Is interactive login required?
No. The Skill is specifically for token-based CLI work instead of depending on an interactive vercel login session.
Where should a CI job obtain its token?
Use the CI platform’s secret storage and expose the credential only to the authorized job. Keep it out of source files, printed commands, generated artifacts, and copied troubleshooting logs.
What should I do if a token may have leaked?
Revoke the exposed credential and replace it through the account’s normal credential controls. Update the affected secret store and check which project actions may have used the old token.
How do I check that the CLI operation used the intended project?
Compare the resolved project and organization identifiers with your known Vercel project before the operation. Afterward, verify the deployment or configuration in that same project rather than relying on authentication success alone.