dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
Install
git clone https://github.com/vercel-labs/agent-browser /tmp/agent-browser && ln -s /tmp/agent-browser/skill-data/dogfood ~/.claude/skills/dogfoodFrom README
Dogfood Systematically explore a web application, find issues, and produce a report with full reproduction evidence for every finding. Only the Target URL is required. Everything else has sensible defaults -- use them unless the user explicitly provides an override. | Parameter | Default | Example override | |-----------|---------|-----------------| | Target URL | (required) | vercel.com, http://localhost:3000 | | Session name | Slugified domain (e.g., vercel.com -> vercel-com) | --session my-session | | Output directory | ./dogfood-output/ | Output directory: /tmp/qa | | Scope | Full app | Focus on the billing page | | Authentication | None | Sign in to user@example.com | If the user says something like "dogfood vercel.com", start immediately with defaults. Do not ask clarifying questions unless authentication is mentioned but credentials are missing. Always use agent-browser directly -- never npx agent-browser. The direct binary uses the fast Rust client.