Evidence Collector

Generate Playwright screenshots and analyze visual evidence against specifications.

Updated Apr 16, 2026

Search Tags:#screenshots #validation #playwright #qa-testing #testing-automation #visual-evidence #spec-comparison

Ready to run

npx skills add https://github.com/jc180105/.opencode --skill evidence-collector-jc180105

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: Evidence Collector
Source: https://github.com/jc180105/.opencode/tree/main/.opencode/skills/testing-evidence-collector
Command: npx skills add https://github.com/jc180105/.opencode --skill evidence-collector-jc180105

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill ensures QA teams have rigorous, visually backed verification by demanding concrete screenshots and evidence for every claim.

Core Features & Use Cases

Automated visual evidence generation using Playwright to capture screenshots of UI states.
Reality-check driven analysis: compare actual visuals to expected specifications and document gaps.
Testing protocol coverage for accordions, forms, navigation, and responsive/mobile layouts.

Quick Start

Run automated Playwright-based visual captures of the running app and review the resulting screenshots to verify against the spec.

Frequently Asked Questions about Evidence Collector

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

FAQPage Schema

How do I validate software behavior using visual evidence?▼

Validate software behavior by generating Playwright screenshots of UI states and comparing them against expected specifications. This visual evidence protocol covers forms, accordions, navigation, and theme states, documenting gaps to ensure alignment.

Can I use Playwright to capture screenshots for QA testing automation?▼

Yes, Playwright captures automated screenshots of running web applications to support QA testing automation. The resulting visual evidence is inspected to verify actual UI states against specifications and document discrepancies.

What is the best way to compare actual UI states against expected specifications?▼

The best way to compare actual UI states against expected specifications is through a reality-check driven analysis. It generates visual evidence using Playwright, inspects the captures, and documents a gap analysis to enforce alignment.

Does visual evidence validation work for mobile layouts and responsive interfaces?▼

Visual evidence validation works for mobile layouts and responsive interfaces. The testing protocol explicitly covers capturing and inspecting these layouts alongside forms, navigation, and accordions to verify spec compliance.

What testing protocol do I need to verify accordions, forms, and navigation states?▼

You need a testing protocol that generates visual evidence for accordions, forms, and navigation states. It enforces capturing concrete screenshots, reviewing logs, and documenting a gap analysis to ensure alignment with specifications.

Why does my QA validation lack rigorous proof when checking UI states?▼

QA validation lacks rigorous proof when it does not demand concrete screenshots and evidence for every claim. Enforcing a clear protocol with visual captures, logs, and documented gap analysis ensures visually backed verification.