dogfood

Explore web applications end-to-end and generate structured dogfood reports with evidence.

40.3k|2.6k|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/vercel-labs/agent-browser --skill dogfood-vercel-labs
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/vercel-labs/agent-browser/tree/main/skills/dogfood
Command: npx skills add https://github.com/vercel-labs/agent-browser --skill dogfood-vercel-labs

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematically exposes UX and QA issues in a web application by guiding a structured manual exploration and producing a ready-to-share report with full reproduction evidence.

Core Features & Use Cases

  • Guided, repeatable QA exploration that maps app flow and surfaces bugs, usability issues, and edge cases.
  • Generates a structured dogfood report including step-by-step repro data, screenshots, and reproducible steps for handoff.
  • Use cases include quick QA cycles, exploratory testing after releases, and quality reviews for stakeholder demos.

Quick Start

Launch a dogfood session against your target URL and start collecting issues with automatic evidence generation.

Frequently Asked Questions about dogfood

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I systematically perform exploratory testing on a web application?

Exploratory testing of a web application involves guiding a structured manual exploration to map app flows, uncover UI and UX issues, and capture reproducible evidence like screenshots for a structured dogfood report.

What is the best way to capture bug reproduction evidence during a QA cycle?

Capturing bug reproduction evidence during a QA cycle requires orchestrating session-scoped operations to document step-by-step repro data and screenshots, generating a ready-to-share report for stakeholder handoff.

How do I report UI and UX issues found during web application testing?

Report UI and UX issues found during web application testing by producing a structured dogfood report that includes step-by-step reproduction data and screenshots for quick QA cycles and stakeholder quality reviews.

Do I need a specific target URL to start a dogfood QA session?

Yes, you need an accessible target URL and a session name to initialize the dogfood workflow scripts that orchestrate session-scoped operations and evidence collection for your exploratory testing.

Can I use this for quality reviews before a stakeholder demo?

Yes, you can use this for quality reviews before a stakeholder demo because the structured dogfood workflow surfaces usability issues and edge cases while producing a ready-to-share report with full reproduction evidence.

What limitations exist when using agent-browser for end-to-end exploratory testing?

End-to-end exploratory testing using agent-browser requires an accessible target URL and dogfood workflow scripts to function, meaning it cannot operate without a valid, reachable web application URL to initialize the session.