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.
npx skills add ECNU-ICALK/AutoSkill --skill dogfood --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# 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 file 2. Authenticate Sign in if needed, save
- Setup
- Workflow
- 1. Initialize
- 2. Authenticate
- 3. Orient
- 4. Explore
- 5. Document Issues (Repro-First)
- 6. Wrap Up
- Guidance
- References
- Templates
mkdir -p {OUTPUT_DIR}/screenshots {OUTPUT_DIR}/videos
cp {SKILL_DIR}/templates/dogfood-report-template.md {OUTPUT_DIR}/report.md
agent-browser --session {SESSION} open {TARGET_URL}
agent-browser --session {SESSION} wait --load networkidle
agent-browser --session {SESSION} snapshot -i
Identify login form refs, fill credentials
agent-browser --session {SESSION} fill @e1 "{EMAIL}"
agent-browser --session {SESSION} fill @e2 "{PASSWORD}"
agent-browser --session {SESSION} click @e3
agent-browser --session {SESSION} state save {OUTPUT_DIR}/auth-state.jsonWhat does the dogfood skill do?
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.
How do I install it?
Run `npx skills add ECNU-ICALK/AutoSkill --skill dogfood --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From ECNU-ICALK/AutoSkill, a repository with 539 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.