verification

Name: verification
Availability: InStock
Author: global-os

Verify end-to-end user stories by tracing data flow from UI trigger to UI response.

Updated Dec 12, 2025

Search Tags:#system validation #application testing #end-to-end verification #full story verification #flow check

Ready to run

npx skills add https://github.com/global-os/gproxy --skill verification-global-os

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/global-os/gproxy/tree/main/.agents/skills/verification
Command: npx skills add https://github.com/global-os/gproxy --skill verification-global-os

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

This Skill provides comprehensive verification of the entire user story, ensuring that every aspect of the flow from browser to API, data, and response is thoroughly checked.

Core Features & Use Cases

Full-Story Verification: Infers the complete user story and verifies every boundary in the flow with evidence.
End-to-End Story Focus: Focuses on the end-to-end story, not just any single layer.
Trigger Conditions: Triggers on dev server start and 'why isn't this working' signals.
Verification Steps: Inference of the user story, establishing evidence baseline, walking the data flow, and reporting with evidence.

Quick Start

Run the verification skill to check the full flow of your application.

Frequently Asked Questions about verification

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

FAQPage Schema

What is end-to-end verification for full user story validation?▼

End-to-end verification infers user intent and checks browser, server, runtime logs, and environment to ensure the complete data flow from UI trigger to UI response is correct with evidence.

How do I verify my application flow when something isn't working?▼

Trigger verification on dev server start or 'why isn't this working' signals to infer the user story, establish an evidence baseline, walk the data flow, and report issues with evidence.

Can I check just the API layer or do I need full-story verification?▼

Full-story verification focuses on the entire end-to-end story rather than any single layer, ensuring every boundary in the flow from browser to API to response is thoroughly checked.

Does end-to-end verification work without setting up specific dependencies?▼

Yes, end-to-end verification requires no additional dependencies, using scripts to analyze the complete application flow and verify data correctness across browser, server, and environment.

What are the limitations of using end-to-end flow checks for system validation?▼

End-to-end flow checks require inference of the complete user story and analysis of the entire application, meaning verification is triggered only by specific prompts or on server start.

What's the best way to validate data flow from UI trigger to UI response?▼

The best way is full-story verification, which walks the data flow across browser, server, runtime logs, and environment boundaries, reporting correctness with established evidence.