Third-Party Agent Skills · Browse by Task

Agent Skills for Deployment and Browser Work

Shipping and checking a web app involves different permissions. Separate preview deployment, token handling, optimization audits, and browser-driven verification before choosing a Skill.

These instructions do not grant Vercel access, supply tokens, or install a browser CLI. Confirm the project, account, and approval boundary before any operation that changes remote state.

Selected Skills and Original Sources

Local GuideVercel Labs

Deploy to Vercel

The original workflow starts with read-only checks for Git remote, project linkage, CLI authentication, and teams. It then selects a deployment route. A linked Git project may use a push, but the source requires asking before pushing.

Local GuideVercel Labs

Vercel CLI with Tokens

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.

Local GuideVercel Labs

Vercel Optimize

The source prescribes an observability-first audit, not a repository-wide optimization sweep. Its scripts collect and merge Vercel signals, gate investigations, and produce ranked recommendations; route-level advice depends on access and observability prerequisites.

Local GuideVercel Labs

agent-browser Skill

The repository's primary product is the agent-browser CLI, not this SKILL.md. The Skill points the agent to `agent-browser skills get core` and specialized workflows, keeping detailed instructions aligned with the installed tool version.

This is an independent directory. Check the publisher's source for installation, tools, and availability.

Choose by the Job

A Preview Needs Deployment

Deploy to Vercel is about checking project linkage and creating a reviewable deployment.

A Token Is Involved

CLI with Tokens focuses on authentication boundaries and avoiding accidental exposure of secrets.

The Running Site Needs Checking

Use browser or webapp testing guidance to inspect actual behavior; use Optimize for an evidence-led performance and cost audit.

Explore Other Skill Categories

Choose the next task, not just the next publisher.

Frequently Asked Questions

Does a deployment Skill deploy without approval?
No. It must operate within the user's account permissions and approval process. Read the original source for its exact workflow.
Is agent-browser only a Skill?
No. The repository's primary product is a browser automation CLI; its companion Skill is an instruction entry point.
Do token instructions include a usable API key?
No. They describe safer handling of credentials the user has already approved; they do not supply credentials.
What is the difference between browser automation and webapp testing?
Browser automation controls a browser for a task. Webapp testing applies it to inspecting and checking an application's behavior.

From Preview to Check

Keep Deployments and Checks Traceable

Review the target, permissions, browser evidence, and next action in one workspace.