All skills
vercel-labs avatar

/dogfood

@8c15ff9 official
by Vercel Labsvercel-labs/agent-browser43k stars
2,928

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.

  • 3 files
  • 15.6 KB
  • Updated 3 weeks ago
  • GitHub

Use this Skill: https://skilld.dev/gh/vercel-labs/agent-browser/dogfood

This session only. Nothing lands on disk.

referencesissue-taxonomy.md

≈907 tokens on demand. Your agent reads this file only when SKILL.md points to it.

Issue Taxonomy

Reference for categorizing issues found during dogfooding. Read this at the start of a dogfood session to calibrate what to look for.

Contents

Severity Levels

Severity Definition
critical Blocks a core workflow, causes data loss, or crashes the app
high Major feature broken or unusable, no workaround
medium Feature works but with noticeable problems, workaround exists
low Minor cosmetic or polish issue

Categories

Visual / UI

  • Layout broken or misaligned elements
  • Overlapping or clipped text
  • Inconsistent spacing, padding, or margins
  • Missing or broken icons/images
  • Dark mode / light mode rendering issues
  • Responsive layout problems (viewport sizes)
  • Z-index stacking issues (elements hidden behind others)
  • Font rendering issues (wrong font, size, weight)
  • Color contrast problems
  • Animation glitches or jank

Functional

  • Broken links (404, wrong destination)
  • Buttons or controls that do nothing on click
  • Form validation that rejects valid input or accepts invalid input
  • Incorrect redirects
  • Features that fail silently
  • State not persisted when expected (lost on refresh, navigation)
  • Race conditions (double-submit, stale data)
  • Broken search or filtering
  • Pagination issues
  • File upload/download failures

UX

  • Confusing or unclear navigation
  • Missing loading indicators or feedback after actions
  • Slow or unresponsive interactions (>300ms perceived delay)
  • Unclear error messages
  • Missing confirmation for destructive actions
  • Dead ends (no way to go back or proceed)
  • Inconsistent patterns across similar features
  • Missing keyboard shortcuts or focus management
  • Unintuitive defaults
  • Missing empty states or unhelpful empty states

Content

  • Typos or grammatical errors
  • Outdated or incorrect text
  • Placeholder or lorem ipsum content left in
  • Truncated text without tooltip or expansion
  • Missing or wrong labels
  • Inconsistent terminology

Performance

  • Slow page loads (>3s)
  • Janky scrolling or animations
  • Large layout shifts (content jumping)
  • Excessive network requests (check via console/network)
  • Memory leaks (page slows over time)
  • Unoptimized images (large file sizes)

Console / Errors

  • JavaScript exceptions in console
  • Failed network requests (4xx, 5xx)
  • Deprecation warnings
  • CORS errors
  • Mixed content warnings
  • Unhandled promise rejections

Accessibility

  • Missing alt text on images
  • Unlabeled form inputs
  • Poor keyboard navigation (can't tab to elements)
  • Focus traps
  • Insufficient color contrast
  • Missing ARIA attributes on dynamic content
  • Screen reader incompatible patterns

Exploration Checklist

Use this as a guide for what to test on each page/feature:

  1. Visual scan -- Take an annotated screenshot. Look for layout, alignment, and rendering issues.
  2. Interactive elements -- Click every button, link, and control. Do they work? Is there feedback?
  3. Forms -- Fill and submit. Test empty submission, invalid input, and edge cases.
  4. Navigation -- Follow all navigation paths. Check breadcrumbs, back button, deep links.
  5. States -- Check empty states, loading states, error states, and full/overflow states.
  6. Console -- Check for JS errors, failed requests, and warnings.
  7. Responsiveness -- If relevant, test at different viewport sizes.
  8. Auth boundaries -- Test what happens when not logged in, with different roles if applicable.

Source: SKILL.md on GitHub

No third-party reports yet.

Signed by skilld at 8c15ff9. This ties the file your Agent reads to that commit on GitHub. It does not review the instructions.

Last checked against GitHub 4 hours ago.

Activeupdated 3 weeks ago
What it can do
Runs commands
All 2 allowed tools
Bash(agent-browser:*)Bash(npx agent-browser:*)
  • Testing
  • qa
  • browser-automation
  • exploratory-testing
  • bug-hunting
  • agent-browser
  • web-testing

README badge

README badge for vercel-labs/agent-browser/dogfood

Systematically explores a web application to identify bugs, UX issues, and other problems, then produces a structured report with step-by-step screenshots, repro videos, and detailed reproduction steps for each finding. Uses the agent-browser tool to navigate, interact with the app, and document issues with full evidence so teams can reproduce and fix them.

Generated from the current SKILL.md.

What is the difference between a static issue and an interactive issue?
Static issues (typos, placeholder text, misalignment, console errors on load) are visible without user interaction and only need a single annotated screenshot. Interactive issues (functional bugs, UX problems, console errors triggered by actions) require user interaction to reproduce and must include a repro video plus step-by-step screenshots.
Do I need to ask for clarification before starting the dogfood session?
No. If the user provides a target URL, start immediately with defaults for session name, output directory, scope, and authentication. Only ask clarifying questions if authentication is mentioned but credentials are missing.
Should I use `npx agent-browser` or `agent-browser` directly?
Always use `agent-browser` directly. The direct binary uses a fast Rust client, while `npx` routes through Node.js and is significantly slower.
When should I document issues — as I find them or after exploring the whole app?
Document each issue immediately as you find it before moving on. Append to the report right away so findings are preserved if the session is interrupted. Never batch all issues for the end.
How many issues should I aim to find before wrapping up?
Aim for 5-10 well-documented issues. Depth and quality of evidence matter more than total count — 5 issues with full repro is better than 20 with vague descriptions.

Generated from the current SKILL.md. These answers refresh after source changes.