Automation and verification guide for running Native SDK apps. Use when the user asks to test a running app, inspect runtime state, list windows, wait for readiness, drive widgets, take deterministic screenshots, send bridge commands, debug why automation is not connected, create smoke tests, or verify a Native SDK example in a GUI-capable session.
How to install automation?
vercel-labs/native/automation
$npx -y skills add vercel-labs/native --skill automationInstalls into the current project.
›Prefer a prompt? Paste this to your agent
Run `npx skills use "https://github.com/vercel-labs/native" --skill "vercel-labs/native/automation"` and follow the generated skill instructions now. Read its complete output, redirecting it to a temporary file first if necessary. Resolve relative paths from the supporting-files directory it provides.
Use the skills in "https://github.com/vercel-labs/native" that are relevant to the current task. Run `npx skills add "https://github.com/vercel-labs/native"` and select the relevant skills, then follow their instructions.
Related
6 picksType
- agent-browserBrowser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…Jul 2026
- just-scrapeSearch, scrape, crawl, extract structured data, and monitor web pages via the ScrapeGraph AI CLI.Jul 2026
- browser-actBrowser automation CLI for AI agents. NEVER run browser-act commands directly via Bash — always invoke this skill first.Jul 2026
- playwright-cliAutomate browser interactions, test web pages and work with Playwright tests.Jul 2026
- browser-useDirect browser control via CDP for web interaction: automation, scraping, testing, screenshots, and site/app work.Jul 2026
- browser-act-skill-forgeForges reusable Skill packages (SKILL.md + scripts) from website exploration via browser-act — no re-exploration later.Jul 2026
