Dogfood
Exploratory QA of web apps: find bugs, evidence, reports.
Install
npx skills add Lord1Egypt/RA-Skills --skill dogfoodgit clone --depth 1 https://github.com/Lord1Egypt/RA-Skills.git /tmp/RA-Skills
mkdir -p ~/.claude/skills
cp -r /tmp/RA-Skills/skills/built-in/dogfood ~/.claude/skills/dogfoodPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Dogfood: Systematic Web Application QA Testing
## Overview
This skill guides you through systematic exploratory QA testing of web applications using the browser toolset. You will navigate the application, interact with elements, capture evidence of issues, and produce a structured bug report.
## Prerequisites
- Browser toolset must be available (`browser_navigate`, `browser_snapshot`, `browser_click`, `browser_type`, `browser_vision`, `browser_console`, `browser_scroll`, `browser_back`, `browser_press`)
- A target URL and testing scope from the user
## Inputs
The user provides:
1. **Target URL** — the entry point for testing
2. **Scope** — what areas/features to focus on (or "full site" for comprehensive testing)
3. **Output directory** (optional) — where to save screenshots and the report (default: `./dogfood-output`)
## Workflow
Follow this 5-phase systematic workflow:
### Phase 1: Plan
1. Create the output directory structure:
```
{output_dir}/
├── screenshots/ # Evidence screenshots
└── report.md # Final report (generated in Phase 5)
```
2. Identify the testing scope based on user input.
3. Build a rough sitemap by planning which pages and features to test:
- Landing/home page
- Navigation links (header, footer, sidebar)
- Key user flows (sign up, login, search, checkout, etc.)
- Forms and interactive elements
- Edge cases (empty states, error pages, 404s)
### Phase 2: ExploreDetails
- Skill name
dogfood- Repository
- Lord1Egypt/RA-Skills
- Path
skills/built-in/dogfood/SKILL.md- Repo updated
- 17 November 2026
FAQ
What does the Dogfood skill do?
Exploratory QA of web apps: find bugs, evidence, reports.
How do I install the Dogfood skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add Lord1Egypt/RA-Skills --skill dogfood. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Dogfood popular?
It lives in Lord1Egypt/RA-Skills, which has 9 GitHub stars and 2 forks.
Related skills
Account Management
9Lord1Egypt/RA-Skills
Reach the Plug&Pay Customer Portal (portal.plugandpay.com/login/{merchant-slug}) where a customer manages their account: view subscriptions, download invoices, edit billing details, change payment term, and cancel/resume a subscription. Documents the passwordless magic-link lo…
Add Items to Cart
9Lord1Egypt/RA-Skills
Resolve a free-text grocery list to specific King Soopers products (UPC, brand, size, price), ask follow-up questions for ambiguous items, then add the confirmed products to the signed-in user's cart for pickup or delivery.
Add to Cart
9Lord1Egypt/RA-Skills
Find a product on kmart.com.au by natural-language query, navigate to the product detail page, capture title/price/SKU/availability, and drive the read-only pre-checkout flow up to the bag (/checkout/bag). Never submits an order — stops at the bag review screen. Documents the …
Replay Demo
9Lord1Egypt/RA-Skills
Synthetic localhost skill for testing Browserbase session replay playback.
User Test Memory
5Magnus-Gille/claude-skills
Spawn independent AI agents across one or more ecosystems (Claude, Codex, Antigravity) to user-test the Munin memory system. Each explores with minimal pre-knowledge and returns structured feedback on what works, what's broken, and what's missing.
Art of Unit Testing
5vnovakovits/claude-skills
Apply Roy Osherove's "The Art of Unit Testing" (Manning — 2nd ed. 2013 in C#/.NET, 3rd ed. 2024 in JavaScript) — the practitioner's guide to writing trustworthy, maintainable, readable unit tests. Centers on Osherove's broad unit-of-work definition (entry point → observable exit point), his three-part test-naming convention (UnitOfWork_StateUnderTest_ExpectedBehavior), the stub-vs-mock distinction by whether you assert against the double, the one-mock-per-test rule, designing for testability via seams (dependency injection, Extract-and-Override), and getting legacy code under test. Use when wr
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.