qa-only

Test web applications and generate reports with health scores, screenshots, and repro steps.

2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/az9713/paperclip-gstack-company --skill qa-only-az9713
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-only
Source: https://github.com/az9713/paperclip-gstack-company/tree/main/gstack/qa-only
Command: npx skills add https://github.com/az9713/paperclip-gstack-company --skill qa-only-az9713

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a systematic way to test web applications, generating a detailed report with health scores, screenshots, and repro steps, without making any fixes.

Core Features & Use Cases

  • Systematic Testing: Tests a web application thoroughly, ensuring all aspects are covered.
  • Structured Report: Delivers a report with a health score, screenshots, and repro steps.
  • Use Case: When you need to perform a QA check on a web application but do not want to fix any issues.

Quick Start

Run the qa-only skill to generate a QA report for your web application.

Frequently Asked Questions about qa-only

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

FAQPage Schema
How do I generate a QA report for a web application without modifying any code?

Automated QA testing can generate a detailed report with health scores, screenshots, and repro steps without applying fixes, making it ideal for identifying issues in a read-only workflow.

What is the best way to perform automated web application testing focused only on bug identification?

Automated web application testing focused on bug identification systematically tests the application and outputs a structured report with health scores and reproduction steps, leaving the actual fixes to the developers.

Can I get health scores and screenshots from a web app QA check?

Yes, a comprehensive QA check evaluates the web application and generates a structured report that includes health scores, screenshots, and detailed reproduction steps for identified issues.

Does this automated testing approach work for web applications where I need strict read-only validation?

This automated testing approach is designed specifically for web applications requiring strict read-only validation, thoroughly testing the application while ensuring no underlying issues are fixed or code is modified.

What limitations should I expect when using a QA tool that only identifies issues?

The primary limitation of a QA tool that only identifies issues is that it does not resolve or fix any detected bugs; it solely generates a comprehensive report with health scores and reproduction steps for your development team.