Evidence Collector

Detect UI and functional defects through screenshot-backed QA review.

20|9|Updated Mar 10, 2026
One-click install
npx skills add https://github.com/WebWakaHub/manus-agency-skills --skill evidence-collector-webwakahub
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Evidence Collector
Source: https://github.com/WebWakaHub/manus-agency-skills/tree/main/agency-testing-evidence-collector
Command: npx skills add https://github.com/WebWakaHub/manus-agency-skills --skill evidence-collector-webwakahub

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps QA reviewers verify what a web app actually does, using visual evidence to catch broken features, layout problems, and spec mismatches that can be missed by casual testing.

Core Features & Use Cases

  • Screenshot-first validation: Compare captured screens against the specification instead of relying on claims.
  • Interactive testing: Check accordions, forms, navigation, theme toggles, and other UI behaviors for real functionality.
  • Responsive review: Inspect desktop, tablet, and mobile layouts to find usability and rendering issues.
  • Use case: Review a landing page or dashboard, capture evidence, and produce a realistic issue list with clear references to what is visible.

Quick Start

Use the Evidence Collector skill to inspect the app, compare screenshots to the spec, and report only the issues you can verify.

Frequently Asked Questions about Evidence Collector

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

FAQPage Schema
How do I catch UI and functional defects using screenshot-backed QA review?

Visual regression testing detects UI defects by comparing captured screenshots of responsive layouts against baseline specifications, ensuring interactive components like navigation and theme switching match expected behaviors.

What is the best way to verify spec-versus-reality checks for responsive layouts?

Spec-versus-reality checks for responsive layouts verify rendering across desktop, tablet, and mobile by capturing automated visual screenshots, inspecting interactive UI behaviors, and flagging verified mismatches in an evidence-based issue report.

Can I use automated screenshots to check interactive components like accordions and theme toggles?

Automated screenshots validate interactive components like accordions and theme toggles by capturing real UI states during testing, confirming that forms, navigation, and layout behaviors function correctly for evidence-based bug reporting.

Does Playwright work for capturing visual evidence during web application testing?

Playwright supports visual evidence capture during web application testing by automating browser actions, capturing screenshots of responsive layouts, and validating interactive components for functional defect detection.

How do I report QA issues with clear references to what is visible on screen?

Report QA issues with visual references by attaching captured screenshots that demonstrate broken features or layout problems, ensuring every bug report contains verified findings directly linked to observable UI defects.

What are the limitations of screenshot-first validation for bug reporting?

Screenshot-first validation for bug reporting is limited to detecting visible visual and functional defects, meaning hidden logic errors or backend failures may be missed unless they manifest as observable UI or layout problems.