Reality Checker

Evaluate web application deployment readiness against QA evidence and specification compliance.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents premature production approvals by demanding real evidence instead of optimistic claims during final integration and QA review.

Core Features & Use Cases

  • Reality-based assessment: Cross-checks reported quality against actual screenshots, journeys, and test results.
  • Deployment readiness gate: Flags missing features, broken flows, and performance issues before launch.
  • Use Case: A reviewer can assess whether a website is truly ready for production after UI changes and automated testing.

Quick Start

Use the Reality Checker skill to review the latest QA evidence for this application and give a realistic production readiness verdict.

Frequently Asked Questions about Reality Checker

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

FAQPage Schema
How do I verify deployment readiness with actual QA evidence instead ofclaims?▼

Deployment readiness verification requires challenging unsupported claims by cross-checking reported quality against actual screenshots, end-to-end user journeys, and integration testing results before final production approval.

What is evidence-based integration testing for final QA reviews?▼

Evidence-based integration testing evaluates web application deployment readiness by demanding real proof of specification compliance, performance results, and implementation details before approving any cross-device user journey checks.

Can I use screenshots for cross-device validation during release readiness checks?▼

Cross-device screenshot validation is supported for release readiness checks, allowing reviewers to assess whether a website is truly ready for production after UI changes by verifying visual evidence.

Does Playwright work with end-to-end user journey checks for deployment approval?▼

Playwright supports end-to-end user journey checks by providing the actual test results and evidence-backed verification of implementation details required to flag broken flows before launch.

What is the best way to prevent premature production approvals after UI changes?▼

Preventing premature production approvals involves applying a deployment readiness gate that flags missing features, broken flows, and performance issues by demanding real evidence instead of optimistic claims.

When should I not use automated test results for final QA reviews?▼

Automated test results are insufficient for final QA reviews when they lack evidence-backed verification of actual screenshots, specification compliance, and end-to-end user journey completion for web applications.