web-qa-expert

Run black-box manual QA on web apps via Playwright CLI and return findings-only reports.

Updated May 3, 2026
One-click install
npx skills add https://github.com/david-nossebro/agent-commons --skill web-qa-expert
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: web-qa-expert
Source: https://github.com/david-nossebro/agent-commons/tree/main/shared/skills/web-qa-expert
Command: npx skills add https://github.com/david-nossebro/agent-commons --skill web-qa-expert

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you perform reliable manual QA on a web app and produce a findings-only report without getting pulled into code debugging or fixes.

Core Features & Use Cases

  • Black-box Playwright QA: Execute real user-flow testing through the browser, validating what users actually experience.
  • Findings-only reporting: Deliver reproduction steps, evidence, coverage notes, and open risks—without analysis of source code.
  • Depth modes: Use smoke for quick checks, standard for serious passes, or deep for exhaustive risk coverage (including edge cases like auth/session variations when reachable).

Quick Start

Ask the agent to run a standard black-box QA pass on your app route using Playwright CLI and return a findings-only report with evidence and reproduction steps.

Frequently Asked Questions about web-qa-expert

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

FAQPage Schema
How do I run black-box manual testing on a web app using Playwright?

Black-box manual testing with Playwright executes real user-flow testing through the browser to validate user experience. It returns findings-only reports containing reproduction steps, evidence, coverage notes, and open risks without analyzing source code.

What is the best way to document reproduction steps and browser evidence for web QA?

Documenting browser evidence for web QA involves running Playwright CLI to execute user flows and capturing findings-only reports. This includes explicit reproduction steps, console and network observations, and coverage gap documentation without proposing fixes.

Does this black-box QA approach work for regression testing and smoke testing?

This black-box QA approach supports regression testing and smoke testing through configurable depth modes. Smoke mode handles quick checks, standard mode covers serious passes, and deep mode performs exhaustive risk coverage including edge cases like auth and session variations.

Can I use Playwright CLI to test forms and navigation without source code access?

Playwright CLI supports testing forms and navigation without source code access by operating strictly black-box. It validates key user flows, observes console and network behavior, and documents coverage gaps while explicitly avoiding source-code analysis or fix proposals.

What happens if the web app cannot be started or reached during manual QA?

If the web app cannot be started or reached during manual QA, the process exhibits clear blocker and hand-off behavior. It stops testing and reports the accessibility issue rather than attempting to proceed with unreachable application routes.

How do I perform deep exploratory testing across key user flows in a web application?

Deep exploratory testing across key user flows uses Playwright CLI in deep mode to achieve exhaustive risk coverage. It validates forms, navigation, console and network observations, and documents coverage gaps while returning evidence-backed findings-only reports.