Agent skill · software engineering · aiskillstore
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.
Why this skill is useful
Adds a comprehensive automation script for exploratory testing that generates detailed reports with reproduction evidence.
What it needs
Requires bash installed locally. About 6k tokens when loaded. Last updated 2026-08-07. 405 stars on the source repository.
What this skill does
Dogfood Systematically explore a web application, find issues, and produce a report with full reproduction evidence for every finding. Setup 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. npx routes through Node.js and is significantly slower. Workflow 1. Initialize Copy the report template into the output directory and fill in the header fields: Start a named session: 2. Authenticate If the app requires login: For OTP/email codes: ask the user, wait for their response, then enter the code. After successful login, save state for potential reuse: 3. Orient Take an initial annotated screenshot and snapshot to understand the app structure: Identify the main navigation elements and map out the sections to visit. 4. Explore Read references/issue-taxonomy.md for the full list of what to look for and the exploration checklist. Strategy -- work through the app systematically: Start from the main navigation. Visit each top-level section. Within each section, test interactive elements: click buttons, fill forms, open dropdowns/modals. Check edge cases: empty states, error handling, boundary inputs. Try realistic end-to-end workflows (create, edit, delete flows). Check the browser console for errors periodically. …
How to use it
Reference it in AdaL, Claude Code, Cursor or any coding agent — nothing to install:
@skills aiskillstore/dogfood