Loading...
Loading...
Found 86 Skills
Autonomous design critique mode using the Agentation annotation toolbar. Use when the user asks to "critique this page," "add design annotations," "review the UI," "self-driving mode," "auto-annotate," or wants an AI agent to autonomously add design feedback annotations to a web page via the browser. Requires the Agentation toolbar to be installed on the target page and agent-browser skill to be available.
Launch and automate VS Code (Code OSS) using agent-browser via Chrome DevTools Protocol. Use when you need to interact with the VS Code UI, automate the chat panel, test UI features, or take screenshots of VS Code. Triggers include 'automate VS Code', 'interact with chat', 'test the UI', 'take a screenshot', 'launch Code OSS with debugging'.
Generate interactive presentation slides using React + Tailwind, and export to standalone single-file HTML. Triggers on keywords like "slides", "presentation", "PPT", "demo", "benchmark", or when user requests export. Uses agent-browser skill for browser verification before export (install with `npx skills add vercel-labs/agent-browser` if not available).
Use Tabbit with agent-browser by reading Tabbit's live DevToolsActivePort file, deriving the browser wsEndpoint, and routing browser actions through agent-browser --cdp.
agent-browser CLI로 Chrome Beta CDP에 연결하여 페이지 탐색, 데이터 확인, 요소 조작을 수행하는 스킬. "브라우저 확인", "페이지 봐줘", "DOM 확인", "데이터 점검", "클릭해줘", "화면 확인" 키워드로 트리거. E2E 시나리오 작성 중 셀렉터 확인이나 실행 실패 디버깅에도 사용한다.
Scope coverage, build a testing strategy, test the feature with agent-browser, capture screenshots/video (always mandatory), upload to S3, and create a structured test report (never skip)
Headless browser automation using Vercel's agent-browser CLI. 93% less context than Playwright MCP. Snapshot + refs workflow with element references. Use when automating browser tasks, web scraping, form filling, or content capture.
Use this skill whenever a user needs terminal-first browser automation with `steel browser`, asks to navigate/click/fill/snapshot/extract from websites, needs explicit browser session lifecycle control (`start`, `stop`, `sessions`, `live`), or wants to migrate `agent-browser` scripts. Trigger even when the user does not mention this skill by name and instead asks for multi-step web workflows, CDP attach behavior, local runtime setup, or browser automation troubleshooting.
Use this skill to triage bugs found by Antithesis using the `agent-browser` skill to control a headless Chromium browser. If you are about to check run status, read property results, inspect findings, view environment images, or extract any information from the triage report — you MUST use this skill first. Covers runs page, run metadata (title, date, run/session IDs), property statuses (passed/failed/unfound), environment source images, findings, utilization metrics, and run logs.
Automate Chrome browser tasks using agent-browser CLI. Navigate pages, fill forms, click buttons, take screenshots, extract data, and replay recorded workflows — all inside the user's real Chrome session.
Unified decision tree for web research and competitive monitoring. Auto-selects WebFetch, Tavily, or agent-browser based on target site characteristics and available API keys. Includes competitor page tracking, snapshot diffing, and change alerting. Use when researching web content, scraping, extracting raw markdown, capturing documentation, or monitoring competitor changes.
Private browser testing rules for jb workflows. Prefer playwrighter_exec with careful tab selection, fall back to agent-browser, and avoid playwright-mcp.