e2e-flow-verifier

Automate end-to-end user flow verification with browser automation and state assertions.

Updated Jun 15, 2026
One-click install
npx skills add https://github.com/CENKSSS/valocase-backend --skill e2e-flow-verifier
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: e2e-flow-verifier
Source: https://github.com/CENKSSS/valocase-backend/tree/main/.claude/skills/e2e-flow-verifier
Command: npx skills add https://github.com/CENKSSS/valocase-backend --skill e2e-flow-verifier

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires vibium, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

This Skill automates the verification of complete user flows, recording session evidence, and asserting state at each step, ensuring product verification with real browser automation.

Core Features & Use Cases

  • End-to-End Flow Verification: Automates user flows with the qe-browser skill, recording evidence, and asserting state at each step.
  • Real Browser Automation: Uses the qe-browser fleet skill for browser automation, capturing screenshots and DOM snapshots.
  • Use Case: For product verification, use this Skill to drive user flows, assert state, and record evidence for a thorough end-to-end test.

Quick Start

Verify a user flow by running: /e2e-flow-verifier [flow-name]

Frequently Asked Questions about e2e-flow-verifier

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

FAQPage Schema
How do I automate end-to-end user flow verification with real browser testing?

End-to-end user flow verification is automated by running a JSON batch plan through real browser automation, which drives each flow step, asserts state changes, and records session evidence like screenshots and DOM snapshots.

What is captured as evidence during end-to-end flow verification?

During end-to-end flow verification, the tool captures session evidence by taking screenshots and DOM snapshots at each step to assert state changes and ensure thorough product verification.

Do I need a JSON batch plan to define user flows for browser automation?

Yes, you need a JSON batch plan to define the user flows for browser automation. The plan structures the execution sequence, allowing the verifier to drive the flows and assert state changes.

Can I use this for product verification without manual browser interaction?

Yes, you can use this for product verification without manual browser interaction. It automates complete user flows using real browser automation, driving the application, asserting state, and recording evidence automatically.

What is the best way to verify state changes during an automated web application flow?

The best way to verify state changes during an automated web application flow is to use a verifier that asserts state at each step while capturing screenshots and DOM snapshots as evidence.

Why does end-to-end testing require Vibium for browser automation?

End-to-end testing requires Vibium because it provides the underlying browser automation capabilities needed to drive the qe-browser fleet, execute the JSON batch plan, and capture DOM snapshots during flow verification.