Individual skill

webapp-qa

Perform scoped exploratory QA of a web application, reproduce defects, collect screenshots and console evidence, and deliver a prioritized report.

sdk/cloud/catalog/skills/webapp-qa/SKILL.md

Read pinned source

Source commit f83b859a173802a73d978197e92328ab2bf57a6e

What was checked

Matches the observed repository HEAD: Yes
Scanner rules are current: Yes
Repository scan complete: No
Skill scan complete: Yes
Observed behavior: Instructions only
Last checked: Nov 9, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings): 1,364
Repository last updated: Oct 22, 2026
License: MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

agent-communication Repository topic
agent-memory Repository topic
ai-agents Repository topic
claude Repository topic
cursor Repository topic
docker Repository topic
knowledge-base Repository topic
llm-tools Repository topic
mcp Repository topic
mcp-server Repository topic
engineering Derived category

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files

LICENSEasset · 1,070 bytes
NOTICE.mddoc · 1,991 bytes
SKILL.mdcore · 2,168 bytes
references/dogfood/GUIDE.mddoc · 6,612 bytes
references/issue-taxonomy.mddoc · 3,682 bytes
templates/dogfood-report-template.mddoc · 1,543 bytes

Read excerpt

# Web Application QA

For the full five-phase exploratory method, read references/dogfood/GUIDE.md;
its taxonomy and report-template links resolve within this bundle.

Use the user-supplied target URL, scope and existing test accounts. Inspect the
available browser tools or Playwright setup first; never invent browser tool
names. Without a working browser, report the blocker and limit claims to checks
actually performed.

1. Map the main user journeys, navigation, forms and error/empty states.
2. Exercise each journey with positive and negative inputs. Inspect console and
   network failures after navigation and significant interactions.
3. Inspect screenshots at desktop and mobile sizes for clipping, overlap,
   loading failures and keyboard accessibility.