evidence-collection

Capture annotated screenshot evidence and generate a reproducible QA report.

116|9|Updated Feb 18, 2026
One-click install
npx skills add https://github.com/elophanto/EloPhanto --skill evidence-collection-elophanto
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: evidence-collection
Source: https://github.com/elophanto/EloPhanto/tree/main/skills/evidence-collection
Command: npx skills add https://github.com/elophanto/EloPhanto --skill evidence-collection-elophanto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Visual QA is often inconsistent and hard to prove; this skill provides a structured approach to collect and verify evidence via screenshots.

Core Features & Use Cases

  • Visual evidence capture across devices and viewports, with annotations and timestamps.
  • Evidence management and reporting to support traceability and auditability.
  • Use Case: Validate UI consistency during design reviews or regression testing by compiling a screenshot-based evidence package.

Quick Start

Capture a representative set of screenshots across key flows and generate an evidence-based QA report for review.

Frequently Asked Questions about evidence-collection

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

FAQPage Schema
How do I collect screenshot evidence for visual QA regression testing?

To collect screenshot evidence for visual QA, you can capture screenshots across web and mobile viewports. This skill annotates and timestamps these images to document visual issues and generate a reproducible QA report.

What is screenshot-based evidence reporting for design reviews?

Screenshot-based evidence reporting is a structured approach to verify UI consistency. It captures visual proof across devices, manages the evidence for traceability, and compiles a standardized package to validate design fidelity.

Can I use browser automation to capture visual QA issues on mobile interfaces?

Yes, you can use browser automation to capture visual QA issues on mobile interfaces. The skill applies browser automation alongside image comparison to identify and document visual discrepancies across key user flows.

Do I need a standardized evidence template to generate a reproducible QA report?

Yes, a standardized evidence template is required to generate a reproducible QA report. It ensures visual issues are documented consistently with annotations and timestamps to support auditability and traceability.

What is the best way to document UI inconsistencies across multiple viewports?

The best way to document UI inconsistencies is to capture a representative set of screenshots across key flows and viewports. Applying image comparison standardizes this visual evidence into a structured QA report for review.