agency-evidence-collector

Analyze Playwright screenshot captures to identify visual and interactive UI defects.

Updated Apr 11, 2026
One-click install
npx skills add https://github.com/omeraltn/ice_cream_website_testing --skill agency-evidence-collector-omeraltn
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agency-evidence-collector
Source: https://github.com/omeraltn/ice_cream_website_testing/tree/main/.antigravity/agency-evidence-collector
Command: npx skills add https://github.com/omeraltn/ice_cream_website_testing --skill agency-evidence-collector-omeraltn

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates unfounded QA reports by insisting that every claim about UI behavior and quality be backed by visual evidence, preventing fantasy reporting and catching visual and interaction defects early.

Core Features & Use Cases

  • Evidence-first QA: Orchestrates automated Playwright screenshot captures and ties every finding to concrete images.
  • Structured interactive checks: Provides protocols for testing accordions, forms, navigation, responsive layouts, and theme toggles with before/after evidence expectations.
  • Use Case: Run this against a deployed or local frontend to collect desktop/tablet/mobile captures, inspect test-results.json, and produce an evidence-backed QA report that quotes specifications.

Quick Start

Capture Playwright screenshots to public/qa-screenshots and generate a QA Evidence-Based Report referencing public/qa-screenshots/test-results.json.

Frequently Asked Questions about agency-evidence-collector

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

FAQPage Schema
How do I collect visual evidence for QA reports using Playwright screenshots?

Collect visual evidence for QA reports by orchestrating automated Playwright screenshot captures across responsive layouts, tying every UI defect claim to concrete images. This prevents unfounded reporting by requiring test-results.json and image references to back findings.

What is evidence-first QA testing for web user interfaces?

Evidence-first QA testing for web user interfaces is a defect identification process that analyzes automated screenshot captures. It insists every claim about UI behavior and quality be backed by visual evidence, preventing fantasy reporting and catching visual and interaction defects early.

How do I test responsive layouts and theme toggles with automated screenshots?

Test responsive layouts and theme toggles by applying structured interactive check protocols that capture automated Playwright screenshots. The process generates before and after visual evidence expectations for desktop, tablet, and mobile views to verify UI behavior.

Do I need Playwright test-results.json to generate evidence-backed QA reports?

Yes, you need Playwright test-results.json to generate evidence-backed QA reports. The skill requires access to this file and automated captures stored in your screenshots directory to inspect results and produce reports that quote specifications.

Can I use automated screenshot captures to find interactive defects in frontend forms and navigation?

Yes, you can use automated screenshot captures to find interactive defects in frontend forms and navigation. The skill provides structured protocols for testing these interactive elements, ensuring every identified defect is supported by concrete visual proof.

What is the best way to prevent unfounded QA findings for web user interfaces?

The best way to prevent unfounded QA findings for web user interfaces is demanding visual proof for every claim. By analyzing automated Playwright captures and referencing specifications, you ensure all reported visual and interaction defects are backed by concrete evidence.