CI
A non-interactive environment needs Vercel access
Use an existing secret-managed token without relying on an interactive vercel login session.
01 / The skill · Deployment · Token authentication
Vercel CLI with Tokens: scope the account before the command
A Skill for Vercel CLI work when an access token, rather than interactive login, is the authentication path. It emphasizes token handling and project/team targeting.
Publisher, source, and installation
Published by Vercel Labs · Type: Authenticated CLI workflow Skill
Independent guide. Vercel Labs has not endorsed Floatboat.
Upstream installation
npx skills add vercel-labs/agent-skills --skill vercel-cli-with-tokensInstalls instructions only. A Vercel token and correctly scoped project access are separate prerequisites.
A realistic request
The source first checks where the token and project identifiers come from. It warns against placing tokens in command-line arguments and distinguishes authentication from knowing which project and organization a command will affect.
Ask the agent
“Use the approved Vercel token to inspect this project's environment settings. Confirm project and team IDs first; never print the token.”
A useful result
A useful answer reports the confirmed target and requested settings while redacting secrets and avoiding unrelated account changes.
When token-based CLI guidance helps
Use it when a Vercel access token is the approved authentication mechanism for deployment or management.
Scope
One token can reach multiple projects
Confirm project and organization identifiers before changing environment variables or deploying.
Security
A command could expose a secret
Keep tokens out of pasted commands, logs, and review comments; use the approved environment mechanism.
What the Skill will not provide
- Obtaining a token or permission you do not already have.
- Treating any authenticated account as the correct deployment target.
How it scopes a token-based operation
Locate auth, identify project and organization, then execute a bounded Vercel CLI task.
- 01
Identify the approved token source
Use the environment or secret store without revealing the token value in chat or commands.
- 02
Resolve project and team
Verify IDs or linked configuration instead of assuming the current CLI context.
- 03
Run the authorized operation
Limit commands to the requested project and keep secret-bearing output out of reports.
02 / Practical guide
Authentication is not project selection
A valid token can access several projects or teams. Confirm the target before any command that changes Vercel state.
Why avoid passing a Vercel token on the command line?
The source warns that command arguments can appear in shell history and process listings. Its workflow uses the CLI's environment-based token handling and requires care with outputs and logs.
How does this differ from Deploy to Vercel?
Deploy to Vercel begins with selecting an overall deployment path and preview environment. This Skill is narrower: operating Vercel CLI securely when token-based authentication is already the chosen path.
What you can take away
- A confirmed Vercel project and organization
- A bounded CLI action
- A report with secrets omitted
What to check first
- Is the token source approved?
- Do project and team identifiers match the request?
- Could command or log output reveal a secret?
Explore More Agent Skills
Read another Skill guide and check its original source before using it.
Frequently Asked Questions
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.
03 / Put it to work · Keep control
Review the target before running deployment commands
Use Floatboat to keep the task and target-project decision explicit. Handle secret tokens only through your approved environment.