qa-report

Generate and publish QA reports with screenshot evidence after sign-off.

9|3|Updated Apr 14, 2026
One-click install
npx skills add https://github.com/Pythagora-io/agent-templates --skill qa-report-pythagora-io
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: qa-report
Source: https://github.com/Pythagora-io/agent-templates/tree/main/QA%20Agent/qa-report
Command: npx skills add https://github.com/Pythagora-io/agent-templates --skill qa-report-pythagora-io

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The final QA reporting process is manual and error-prone. This skill automates gathering screenshots, validates their presence on disk, uploads to S3, and generates an HTML report with embedded evidence, then shares the link in your communication channels after Tech Lead sign-off.

Core Features & Use Cases

  • Collects browser test screenshots and verifies they exist
  • Uploads evidence to S3 and renders a unified HTML QA report
  • Publishes the report link to Linear, GitHub, and Slack to close the QA cycle
  • Triggered after Tech Lead confirms sign-off in Phase 4

Quick Start

Run this skill after Tech Lead sign-off to generate and publish the final QA report with embedded screenshots.

Frequently Asked Questions about qa-report

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

FAQPage Schema
How do I automate QA report generation with screenshot evidence?

Generate HTML QA reports by validating browser test screenshots on disk, uploading evidence to S3, and embedding assets in the final report before publishing the link across communication channels.

Can I publish QA reports to Linear, GitHub, and Slack automatically?

Publish QA reports to Linear, GitHub, and Slack automatically by triggering the report generation workflow after Tech Lead sign-off to distribute the final HTML report link across production environments.

What are the prerequisites for generating an HTML QA report with screenshots?

Generating an HTML QA report requires Tech Lead sign-off in Phase 4, browser test screenshots present on disk, and S3 integration to upload and access evidence assets in the final report.

Why does my automated QA report fail validation during generation?

Automated QA report validation fails when browser tests lack corresponding screenshots, required assets are missing from disk, or files are inaccessible for embedding in the final HTML report.

Does this QA report automation work without manual screenshot collection?

QA report automation works without manual collection by automatically gathering browser test screenshots from disk and verifying their existence before uploading to S3 and generating the final HTML report.