agency-reality-checker

Name: agency-reality-checker
Availability: InStock
Author: augustoheiss

Enforce evidence-based integration verification with Playwright screenshots and test-results.json metrics.

Updated Feb 11, 2026

Search Tags:#deployment #screenshots #qa #evidence #playwright #integration-testing #production-readiness

Ready to run

npx skills add https://github.com/augustoheiss/LogicDefense --skill agency-reality-checker-augustoheiss

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agency-reality-checker
Source: https://github.com/augustoheiss/LogicDefense/tree/main/.gemini/skills/agency-reality-checker
Command: npx skills add https://github.com/augustoheiss/LogicDefense --skill agency-reality-checker-augustoheiss

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Stops fantasy approvals by enforcing evidence-based integration verification and preventing premature "production ready" certifications without overwhelming visual and test evidence.

Core Features & Use Cases

Evidence-first certification: Requires automated Playwright screenshots, test-results.json metrics, and cross-validated QA artifacts before changing status from NEEDS WORK.
End-to-end journey validation: Validates complete user flows (navigation, forms, interactions) with before/after screenshots and performance metrics.
Use Case: Final integration reviewer for a web app runs automated captures, compares QA reports to visual evidence, and produces a realistic integration report with required fixes and timelines.

Quick Start

Run a reality-based integration assessment that captures automated screenshots, verifies test-results.json, cross-validates QA findings, and report a realistic production readiness status defaulting to NEEDS WORK.

Frequently Asked Questions about agency-reality-checker

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

FAQPage Schema

How do I prevent premature production approvals without visual evidence?▼

You can prevent premature production approvals by enforcing evidence-based integration verification that requires automated Playwright screenshots, test-results.json metrics, and cross-validated QA artifacts before certifying readiness.

What is evidence-based integration verification for production readiness?▼

Evidence-based integration verification is a process that validates complete user flows using automated captures and test metrics, defaulting to a NEEDS WORK status unless overwhelming visual and QA proof is provided.

How do I enforce screenshot evidence and test metrics before deployment?▼

You can enforce screenshot evidence and test metrics by requiring automated Playwright captures and test-results.json files as mandatory inputs, cross-validating these findings against QA reports before allowing any deployment.

Can I use Playwright screenshots to validate end-to-end user journeys?▼

Yes, you can use Playwright screenshots to validate end-to-end user journeys by capturing before and after images of navigation, forms, and interactions, then matching them with performance metrics to verify production readiness.

Does integration testing require cross-validated QA artifacts to certify readiness?▼

Integration testing requires cross-validated QA artifacts to certify readiness because the verification process defaults to NEEDS WORK, demanding matched QA evidence and test-results.json metrics before any production approval.

What are the limitations of relying on automated test results for production readiness?▼

A key limitation is that automated test results alone are insufficient for production readiness; the process strictly requires accompanying Playwright screenshots and cross-validated QA evidence to prevent fantasy approvals.