agency-evidence-collector

Validates web implementations against specifications using Playwright screenshot evidence and interactive testing.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-evidence-collector-immamdouhaboammar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-evidence-collector
Source: https://github.com/imMamdouhaboammar/Mimera/tree/main/.agents/skills/testing-evidence-collector
Command: npx skills add https://github.com/imMamdouhaboammar/Mimera --skill agency-evidence-collector-immamdouhaboammar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It prevents unverified or exaggerated QA claims by requiring screenshot-based proof for every assessment, catching broken functionality and specification mismatches before approval. ## Core Features & Use Cases - Visual Evidence Capture: Runs Playwright-based screenshot collection across desktop, tablet, and mobile viewports, including dark mode and interaction states. - Interactive Element Testing: Verifies accordions, forms, navigation, mobile menus, and theme toggles with before/after screenshot comparisons. - Specification Compliance Auditing: Quotes the original spec and maps each requirement to what screenshots actually show, flagging gaps and fantasy claims. - Use Case: After a developer claims a landing page is complete, run this Skill to capture responsive screenshots, test all interactive elements, and produce an evidence-backed report listing concrete issues with priorities. ## Quick Start Run the QA evidence collector against my local site at http://localhost:8000 and produce a screenshot-backed report of all issues found.

Frequently Asked Questions about agency-evidence-collector

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

FAQPage Schema
How do I verify a web implementation matches its specification?▼

Capture screenshots across desktop, tablet, and mobile viewports, then compare each visual result against quoted specification text. Document matches and mismatches explicitly, and test interactive elements like accordions and forms with before/after captures.

How to test accordions and forms with Playwright screenshots?▼

Capture a screenshot before interacting, trigger the click or form submission via Playwright, then capture an after screenshot. Identical before/after images for an accordion indicate the toggle is broken; form tests should confirm submission, validation, and error messages.

What screenshots are needed for mobile responsive testing?▼

Capture at three standard viewports: 1920x1080 desktop, 768x1024 tablet, and 375x667 mobile. Also verify the mobile hamburger menu opens and closes, and capture dark mode variants if the site supports theme switching.

Why is 'zero issues found' a red flag in QA reviews?▼

First implementations almost always contain 3-5 or more issues, so a clean report usually means insufficient testing rather than perfect code. Skeptical re-examination of screenshots and interactions typically surfaces layout, responsiveness, or functionality problems.

What are the limitations of screenshot-based QA testing?▼

Screenshot comparison cannot verify backend logic, data persistence, accessibility semantics, or performance under load. It should be combined with functional and integration testing for complete coverage.