verification

Name: verification
Availability: InStock
Author: arth

Traces a feature from browser to server to data and reports the first broken layer.

1|Updated Apr 19, 2026

Search Tags:#debugging #api #verification #environment #end-to-end #browser #runtime logs

Ready to run

npx skills add https://github.com/arthtyagi/onloop --skill verification-arthtyagi

💬 Prompt for ChatGPT / Claude Chat▼

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you confirm whether a feature truly works by tracing the complete user story across browser behavior, server logic, data access, and the final rendered response.

Core Features & Use Cases

End-to-End Verification: Follows the flow from UI trigger to API call to data source to response so you can catch broken boundaries early.
Evidence-Based Debugging: Collects visible browser output, server logs, runtime signals, and environment clues before drawing conclusions.
Practical Use Cases: Use it when a dev server starts, when a feature “almost works,” or when you need to validate that a change is functioning beyond unit-level checks.

Quick Start

Use the verification skill to trace the feature from its browser entry point through the API and data layers, then report the first broken boundary with evidence and a specific fix.

Frequently Asked Questions about verification

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

FAQPage Schema

How do I debug an end-to-end feature failure across UI, API, and data layers?▼

End-to-end verification traces the feature from browser interaction through server handling to data access, collecting visible browser output, server logs, and environment clues to isolate the first broken boundary and provide a specific fix.

What is the best way to verify a full-stack user flow on a live development server?▼

Full-stack flow verification follows the user story from UI trigger to API call to data source and rendered response, requiring evidence at each boundary to confirm the feature works beyond unit-level checks.

Why does my feature almost work but fail with ambiguous errors in the browser?▼

Ambiguous failures often stem from broken boundaries between the UI, API, or data layers; tracing runtime logs and environment configuration from the browser entry point identifies the exact layer where the flow breaks.

Can I use end-to-end verification to check environment configuration and runtime logs together?▼

Yes, end-to-end verification gathers runtime signals, server logs, and environment configuration clues alongside browser output to validate that a change is functioning correctly across all interacting layers.

How do I produce a structured report for a broken feature boundary?▼

Tracing the flow from the browser entry point through the API and data layers stops at the first broken layer, generating a structured verification report that includes specific evidence and targeted fixes.