verification

Infer and verify end-to-end user flows across browser, API, data, and response.

246|42|Updated Mar 4, 2026
One-click install
npx skills add https://github.com/vercel/vercel-plugin --skill verification-vercel
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: verification
Source: https://github.com/vercel/vercel-plugin/tree/main/skills/verification
Command: npx skills add https://github.com/vercel/vercel-plugin --skill verification-vercel

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inference and verification of complete end-to-end user stories across the browser, API, data sources, and response, coordinating multiple layers to ensure a reliable flow.

Core Features & Use Cases

  • Infers the user story from context and guides end-to-end verification across UI, API, and data sources.
  • Generates a structured verification report covering each boundary and captures evidence for failures.
  • Coordinates with agent-browser-verify, investigation-mode, and observability to diagnose and fix issues quickly.

Quick Start

Start verification during dev server startup to generate the end-to-end flow report.

Frequently Asked Questions about verification

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

FAQPage Schema
How do I verify end-to-end user flows from browser to API to data response?

End-to-end verification infers the complete user story and validates the full flow from browser UI entry through API routes to data sources and response rendering. It generates a structured report covering each boundary and captures evidence for failures across all layers.

What is the best way to debug full stack feature flows during dev server startup?

Debugging full stack flows during dev server startup involves inferring the user story from context and guiding verification across UI, API, and data sources. This coordinates observability and structured logging to validate boundaries and quickly diagnose issues.

Can I use observability and browser tools to diagnose API and UI boundaries?

Observability and browser verification tools coordinate to diagnose API and UI boundaries by applying structured logging and environment awareness. This combination validates the complete flow and captures failure evidence across the browser, API, and data layers.

When do I need end-to-end feature flow verification?

End-to-end feature flow verification is needed when users report issues or during dev server startup. It applies environment awareness to validate boundaries across UI entry, API routes, data sources, and response rendering to ensure a reliable flow.