qa-only

Automate web application testing and generate health reports with screenshots and repro steps.

1|Updated Mar 24, 2026

Search Tags:#web testing #web app #bug detection #QA reporting #health checking

Ready to run

npx skills add https://github.com/greencm/gstuck --skill qa-only-greencm

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/greencm/gstuck/tree/main/output/gstack/qa-only
Command: npx skills add https://github.com/greencm/gstuck --skill qa-only-greencm

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires puppeteer, cheerio, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The QA-only skill automates the systematic testing of web applications and provides detailed reports without the ability to fix issues, helping you quickly identify problems for further action.

Core Features & Use Cases

Report Generation: Systematically tests web applications and generates structured reports.
Health Score: Provides a health score indicating the overall status of the application.
Screenshot Integration: Includes screenshots of tested pages for visual verification.
Repro Steps: Offers repro steps to replicate any detected issues.
Use Case: Use this skill to run an initial quality assurance pass on a web app before development proceeds to the fix phase.

Quick Start

Run a QA test report for your project by invoking: "qa report only"

Frequently Asked Questions about qa-only

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

FAQPage Schema

How do I automate web app testing to generate reports without applying fixes?▼

Automated web app testing reports without fixes are generated by systematically testing pages with a headless browser to identify issues. This skill provides structured health reports, complete with screenshots and repro steps, intended for initial QA passes before development proceeds to the fix phase.

What is included in a QA health report for web applications?▼

A QA health report for web applications includes a calculated health score indicating overall status, screenshots of tested pages for visual verification, and detailed repro steps to replicate detected issues. This structured report helps developers quickly identify and address problems for further action.

Can I use a headless browser to capture screenshots and repro steps for bug detection?▼

Yes, you can use a headless browser to capture screenshots and generate repro steps for bug detection. The skill leverages headless browser testing to automate web page interactions, documenting visual states and providing systematic steps to replicate any identified issues.

Do I need a working Conductor session to run automated web testing?▼

Yes, a working Conductor session or an interactive prompt is required to run automated web testing for full functionality. The skill depends on this environment to properly execute headless browser testing and generate health reports for your web application.

Does puppeteer work with this skill for web app health checking?▼

Puppeteer works with this skill as a core dependency to perform web app health checking. It drives the headless browser to automate testing of web pages, enabling the skill to capture screenshots and detect bugs systematically during the QA reporting process.

What are the limitations of using QA-only for bug detection?▼

The primary limitation of using QA-only for bug detection is that it generates reports without applying any fixes. It is strictly intended for initial quality assurance passes to identify issues, requiring a separate development phase to actually resolve the detected bugs.