Install
Terminal · npx$
npx skills add https://github.com/vercel-labs/agent-browser --skill dogfoodWorks with Paperclip
How Dogfood fits into a Paperclip company.
Dogfood drops into any Paperclip agent that handles this kind of work. Assign it to a specialist inside a pre-configured PaperclipOrg company and the skill becomes available on every heartbeat — no prompt engineering, no tool wiring.
S
SaaS FactoryPaired
Pre-configured AI company — 18 agents, 18 skills, one-time purchase.
$27$59
Explore packSource file
SKILL.md220 linesExpandCollapse
---name: dogfooddescription: 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.allowed-tools: Bash(agent-browser:*), Bash(npx agent-browser:*)--- # 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 Set up session, output dirs, report file2. Authenticate Sign in if needed, save state3. Orient Navigate to starting point, take initial snapshot4. Explore Systematically visit pages and test features5. Document Screenshot + record each issue as found6. Wrap up Update summary counts, close session``` ### 1. Initialize ```bashmkdir -p {OUTPUT_DIR}/screenshots {OUTPUT_DIR}/videos``` Copy the report template into the output directory and fill in the header fields: ```bashcp {SKILL_DIR}/templates/dogfood-report-template.md {OUTPUT_DIR}/report.md``` Start a named session: ```bashagent-browser --session {SESSION} open {TARGET_URL}agent-browser --session {SESSION} wait --load networkidle``` ### 2. Authenticate If the app requires login: ```bashagent-browser --session {SESSION} snapshot -i# Identify login form refs, fill credentialsagent-browser --session {SESSION} fill @e1 "{EMAIL}"agent-browser --session {SESSION} fill @e2 "{PASSWORD}"agent-browser --session {SESSION} click @e3agent-browser --session {SESSION} wait --load networkidle``` For OTP/email codes: ask the user, wait for their response, then enter the code. After successful login, save state for potential reuse: ```bashagent-browser --session {SESSION} state save {OUTPUT_DIR}/auth-state.json``` ### 3. Orient Take an initial annotated screenshot and snapshot to understand the app structure: ```bashagent-browser --session {SESSION} screenshot --annotate {OUTPUT_DIR}/screenshots/initial.pngagent-browser --session {SESSION} snapshot -i``` Identify the main navigation elements and map out the sections to visit. ### 4. Explore Read [references/issue-taxonomy.md](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. **At each page:** ```bashagent-browser --session {SESSION} snapshot -iagent-browser --session {SESSION} screenshot --annotate {OUTPUT_DIR}/screenshots/{page-name}.pngagent-browser --session {SESSION} errorsagent-browser --session {SESSION} console``` Use your judgment on how deep to go. Spend more time on core features and less on peripheral pages. If you find a cluster of issues in one area, investigate deeper. ### 5. Document Issues (Repro-First) Steps 4 and 5 happen together -- explore and document in a single pass. When you find an issue, stop exploring and document it immediately before moving on. Do not explore the whole app first and document later. Every issue must be reproducible. When you find something wrong, do not just note it -- prove it with evidence. The goal is that someone reading the report can see exactly what happened and replay it. **Choose the right level of evidence for the issue:** #### Interactive / behavioral issues (functional, ux, console errors on action)