agency-evidence-collector

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

Updated Sep 10, 2026
One-click install
npx skills add https://github.com/sammysparks000/skillshare --skill agency-evidence-collector-sammysparks000
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-evidence-collector
Source: https://github.com/sammysparks000/skillshare/tree/main/skills/testing-evidence-collector
Command: npx skills add https://github.com/sammysparks000/skillshare --skill agency-evidence-collector-sammysparks000

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? QA reviews often produce fantasy reports claiming zero issues or perfect scores without proof. This Skill enforces evidence-based quality assurance by requiring screenshot verification for every claim about a web implementation. ## Core Features & Use Cases - Screenshot-Based Verification: Captures desktop, tablet, mobile, and dark-mode screenshots via Playwright to prove what is actually built. - Interactive Element Testing: Tests accordions, forms, navigation, mobile menus, and theme toggles with before/after visual evidence. - Specification Compliance Checking: Quotes the original spec and compares it against visual reality to catch mismatches and unimplemented features. - Use Case: After a developer claims a landing page is production-ready, run this Skill to capture responsive screenshots, test all interactive elements, and produce a report listing 3-5 concrete issues with screenshot references. ## Quick Start Ask the agent to QA the site running at localhost:8000 and produce an evidence-based report with Playwright screenshots.

Frequently Asked Questions about agency-evidence-collector

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

FAQPage Schema
How do I QA a website with screenshot evidence?▼

Run the Playwright capture script against the local server URL to generate responsive, dark-mode, and interaction screenshots. Then compare each screenshot against the original specification and document every mismatch with image references.

How to test accordions and forms with Playwright screenshots?▼

Capture before and after screenshots of each interactive element using the automated Playwright script. If the before and after images are identical, the interaction is broken; record the result with the TESTED or ERROR status from test-results.json.

Does this QA approach work with Laravel Blade templates?▼

Yes, the reality-check commands inspect resources/views directories and grep Blade files alongside HTML and CSS. Screenshots are taken from the running local server regardless of the templating engine used.

Why does the QA report default to finding 3-5 issues?▼

First implementations almost always contain defects, so a zero-issue claim signals insufficient inspection. Defaulting to 3-5 findings forces deeper visual review and prevents fantasy reporting where broken work gets approved.

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

Screenshots verify visual and interactive states but cannot confirm backend logic, security, or performance under load. It also requires a running local server and the Playwright capture script to be present in the project.