qa-explore
Skill0 starsChanged 28 days agoMITView on GitHub
Run a charter-based exploratory testing session against the RUNNING app (URL, localhost, CLI or API) — the agent drives a real browser, attacks with heuristics, and returns reproducible findings with screenshots, console and network evidence.
4 other projects use a version of this.
Adopted by
Most recently taken up by
- willcoliveira/qualiow-exploratory-testing-skillstheir own version, first seen Oct 25, 2026
- ZSeven-W/dsh-qatheir own version, first seen Oct 8, 2026
- victoraguilarsantamariadev/qa-exploretheir own version, first seen Sep 28, 2026
- QAtools-tech/qa-investigation-harnesstheir own version, first seen Aug 18, 2026
Other versions4 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 4
- willcoliveira/qualiow-exploratory-testing-skills★ 15same name
- QAtools-tech/qa-investigation-harness★ 4same name
- ZSeven-W/dsh-qa★ 4same name
- victoraguilarsantamariadev/qa-explore★ 2same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- qa-auditSkill
- qa-automateSkill
- qa-bugSkill
- qa-casesSkill
- qa-diffSkill
- qa-flakySkill
- qa-initSkill
- qa-planSkill
- qa-releaseSkill
- qaSkill
The file
We split this skill into the rules it gives an agent
2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.
0
Common
Most of the 3 edited versions we read keep these.
1
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 10
Browser check: if no browser tool is available (Playwright MCP, Claude in Chrome), tell the user they can add one with claude mcp add …
- Distinctive: line 13
Charters: if the user gave a broad area ("the whole app"), split it into 2–3 charters (e.g., money path, input attacks, roles/permissions) …
“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Delegate to the qa-explorer subagent (it may appear as argus-qa:qa-explorer).
- Target: $ARGUMENTS. If no URL is given, get it from
.qa/context.md. Failing that, detect the dev server command (don't start anything against production). If it's still unclear, ask. - Browser check: if no browser tool is available (Playwright MCP, Claude in Chrome), tell the user they can add one with
claude mcp add playwright -- npx @playwright/mcp@latest. Meanwhile, the explorer can fall back to scripted Playwright runs. - Charters: if the user gave a broad area ("the whole app"), split it into 2–3 charters (e.g., money path, input attacks, roles/permissions) and run them as parallel explorer subagents with distinct charters. Run accessibility in parallel too, via
qa-accessibility-auditor, when it's a UI. - Merge the findings, ranked by severity. Offer
/qa-bugto turn ✅ findings into tracker-ready reports, and/qa-automateto lock in regression tests.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.