Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →vercel-labs/dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems.
Passed 17 of 21 test cases with the skill, and 4 of 21 without it.
and 15 more in the full report
14 fixed5 passed either way5 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 14 test cases the skill fixed. Same model, same prompt, with and without the skill.
What is the exact CLI command sequence to initialize a named session 'my-check' and navigate to https://dashboard.example.com while waiting for initial DOM loading?
| Checked | Without skill | With skill |
|---|---|---|
| Runs agent-browser --session my-check open https://dashboard.example.com. | Missed | Passed |
| Runs agent-browser --session my-check wait --load domcontentloaded. | Missed | Passed |
The instructions your model reads when the skill loads.
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 [email protected] |
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.
1. Initialize Set up session, output dirs, report file
2. Authenticate Sign in if needed, save state
3. Orient Navigate to starting point, take initial snapshot
4. Explore Systematically visit pages and test features
5. Document Screenshot + record each issue as found
6. Wrap up Update summary counts, close session
mkdir -p {OUTPUT_DIR}/screenshots {OUTPUT_DIR}/videos
Copy the report template into the output directory and fill in the header fields:
test cases passed, vs 4 / 21 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.