Domains
Forms
Mechanism
Breaks down how the skill works and what it produces, so you can quickly judge whether it fits your scenario and value.
When a user needs browser automation inside a Vercel-deployed app (Next.js, SvelteKit, etc.), wants headless Chrome without binary limits, persistent sessions, or isolated ephemeral environments.
@agent-browser/sandbox helpers to run commands (open, snapshot, screenshot, fill, click)Headless browser automation executable from any Vercel app: screenshots, accessibility snapshots, form fills, and cron-driven tasks in isolated VMs.
Use Cases
A Next.js app owner wants to capture a daily screenshot of a competitor's pricing page and post it to Slack. They use vercel-sandbox to run headless Chrome in a microVM via a Vercel Cron Job, take the screenshot, and return base64 image. This avoids local Chrome binary limits and runs isolated, letting the team track pricing changes automatically with zero manual effort.
A SvelteKit developer needs to fill and submit a multi-step form on an external site from their app. Using vercel-sandbox, they open the URL in a persistent microVM, parse the accessibility snapshot, fill fields, click submit, and capture the result screenshot. The isolated sandbox keeps sessions stable across commands and avoids polluting the deployment with Chrome binaries.
Skill Relationships
Dependency relationships read as "the upper tier points to the lower tier." The current Skill sits in the middle tier — above are Skills that depend on it, below are Skills it depends on.
Tier 1 · These Skills Use Me
Tier 2 · Current Skill
Tier 3 · I Use These Skills
Browse this skill's relationships within its skillset. Click a node to switch the side panel; use the search box to jump to any skill.
Skill File