Produce report-only QA evidence with reproduction steps and screenshots.
npx skills add https://github.com/Haohao-end/openagent --skill qa-only-haohao-end
Please help me install this Agent Skill. Skill: qa-only Source: https://github.com/Haohao-end/openagent/tree/main/api/internal/core/skills/catalog/qa-only Command: npx skills add https://github.com/Haohao-end/openagent --skill qa-only-haohao-end
It helps teams validate whether a page or workflow has issues by producing an organized QA report with clear evidence, without attempting to change or repair anything.
Ask the AI to run a report-only QA pass on the target page and produce a structured issue report with reproduction steps, screenshots, and a problem checklist.
High-intent search queries and answers about installing and using this skill.
Report-only QA testing is an exploratory browser testing process that discovers UI or workflow defects and compiles a structured findings document. You need it when you want bug evidence and impact assessment without applying automated fixes or code changes.
To document reproduction steps for a suspected UI defect, run an exploratory browser testing pass that records the exact actions taken, captures screenshots, and compiles a structured QA report detailing the problem checklist and affected scope.
Yes, you can use this for exploratory browser testing because it follows a strict no-fix workflow. It validates pages, captures bug evidence like screenshots and reproduction steps, and outputs a structured QA report without attempting any remediation.
The best way to compile bug evidence for a structured QA report is to run a report-only QA pass that discovers problems, records reproduction steps, captures screenshots, and assesses the affected scope into a single deliverable for investigation.
Browser testing for bug evidence requires no specific testing frameworks or dependencies. It operates as a standalone exploratory testing session to validate pages and produce a structured findings document with reproduction steps and screenshots.
Collecting screenshots and reproduction steps instead of fixing bugs directly speeds up investigation by providing clear, structured bug evidence. This report-only approach assesses impact scope and documents defects without the risk of introducing automated remediation errors.
skkeoriwAutomate exploratory QA testing of web applications through a 5-phase workflow.
yahav123147Run report-only QA testing on web applications and generate health score reports with screenshots and reproduction steps.
jordanhubbardAutomate exploratory QA testing of web applications with browser interactions and bug reports.
soyasisSimulate user interactions to produce a structured defect report with screenshots and reproduction steps.
