dogfood

Identify and document web application bugs through structured exploratory QA.

Updated Apr 30, 2026
One-click install
npx skills add https://github.com/photonics-dhl/Hermes --skill dogfood-photonics-dhl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: dogfood
Source: https://github.com/photonics-dhl/Hermes/tree/main/hermes-home/skills/dogfood
Command: npx skills add https://github.com/photonics-dhl/Hermes --skill dogfood-photonics-dhl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Systematic exploratory QA testing of web applications to uncover bugs, collect evidence, and generate structured reports.

Core Features & Use Cases

  • Guided exploration of web apps using a browser toolset to navigate, interact, and observe behavior.
  • Evidence collection including screenshots, console data, and a final structured report.
  • Use case: verify critical web workflows (login, form submissions, navigation) and produce a report detailing issues for fix prioritization.

Quick Start

Observe a target web app, run the QA workflow, and generate a structured bug report.

Frequently Asked Questions about dogfood

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

FAQPage Schema
How do I find and document bugs in a web application through exploratory QA?

Exploratory web QA identifies and documents bugs in browser-based interfaces through structured testing. It applies browser toolset commands to navigate pages, interact with forms, and collect console data, generating evidence-rich reports for fix prioritization.

What's the best way to collect evidence like screenshots when testing web interfaces?

Collect evidence during web QA by using browser toolset commands such as browser_vision and browser_console. These tools capture screenshots and console output while you interact with interactive elements, producing a final structured bug report with verifiable findings.

Can I test critical web workflows like login and form submissions without writing test scripts?

Yes, you can verify critical web workflows including login, form submissions, and navigation without scripts. Guided exploratory QA uses browser toolset commands to click, type, and observe behavior dynamically across target URLs, documenting issues as they appear.

What is structured exploratory QA testing and when do I need it for my web app?

Structured exploratory QA testing is a systematic approach to uncovering bugs in web applications by navigating and interacting with pages dynamically. You need it when evaluating browser-based interfaces, forms, and navigation to produce evidence-rich reports for fix prioritization.

Does web QA testing work with browser toolset commands like browser_navigate and browser_click?

Web QA testing requires browser toolset commands like browser_navigate, browser_click, browser_type, browser_vision, and browser_console to interact with pages. These commands enable you to observe target URLs, trigger interactive elements, and collect findings for structured reports.

What are the limitations of exploratory QA for evaluating browser-based interfaces?

Exploratory QA is limited to evaluating browser-based interfaces and interactive elements across target URLs. It relies on browser toolset commands to observe behavior and collect findings, meaning it cannot test backend APIs or non-web application layers.