agency-evidence-collector

Capture screenshots and review test results for visual QA evidence.

1|Updated May 5, 2026
One-click install
npx skills add https://github.com/bomberoxenviosdosruedas/01EnviosDosRueda --skill agency-evidence-collector-bomberoxenviosdosruedas
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: agency-evidence-collector
Source: https://github.com/bomberoxenviosdosruedas/01EnviosDosRueda/tree/main/.agents/workflows/agency-evidence-collector
Command: npx skills add https://github.com/bomberoxenviosdosruedas/01EnviosDosRueda --skill agency-evidence-collector-bomberoxenviosdosruedas

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill provides a reality-check approach to quality assurance by focusing on visual evidence, ensuring issues are identified and documented accurately.

Core Features & Use Cases

  • Visual Evidence-Driven QA: Requires visual proof for all claims to ensure accuracy.
  • Default to Finding Issues: Assumes that first implementations have at least 3-5 issues, looking for discrepancies between built and specified features.
  • Process Automation: Automates steps like generating screenshots, checking feature implementation, and reviewing test results.

Quick Start

Run the 'qa-playwright-capture.sh' script to generate visual evidence and then execute the reality check commands to identify issues.

Frequently Asked Questions about agency-evidence-collector

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

FAQPage Schema
How do I collect visual evidence for QA issue identification in web applications?▼

To collect visual evidence for QA issue identification, run the qa-playwright-capture.sh script to generate automated screenshots and execute reality check commands to document discrepancies against specifications.

What is a reality-check approach in web application testing?▼

A reality-check approach in web application testing requires visual proof for all claims to ensure accuracy, assuming first implementations have at least 3-5 issues and actively looking for discrepancies between built and specified features.

How do I automate screenshot generation for testing feature implementation?▼

You automate screenshot generation for testing feature implementation by running the provided qa-playwright-capture.sh script, which captures visual proof and feeds it into the review process for test results.

Does visual evidence-driven QA work for reviewing test results and compliance?▼

Yes, visual evidence-driven QA works for reviewing test results and compliance by automating screenshot generation and requiring visual proof to verify that implementations match the specified features accurately.

Why does visual evidence-driven QA assume there are issues in first implementations?▼

Visual evidence-driven QA assumes first implementations have 3-5 issues to proactively identify discrepancies between built and specified features, ensuring a rigorous reality check rather than assuming initial correctness.

What is the best way to identify discrepancies between built and specified web application features?▼

The best way to identify discrepancies is using a visual evidence-driven QA process that automates screenshots and performs reality checks, comparing built features against specifications to find at least 3-5 issues.