agent-test:screenshot-protocol

Name: agent-test:screenshot-protocol
Availability: InStock
Author: Visual

Capture standardized UI-test screenshots with wait-before-screenshot and naming protocols.

3|1|Updated Mar 26, 2026

Search Tags:#automation #naming-conventions #screenshot #agent-testing #qa-testing #evidence-capture #dfs

Ready to run

npx skills add https://github.com/visual-z/agent-test --skill agent-test-screenshot-protocol

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: agent-test:screenshot-protocol
Source: https://github.com/visual-z/agent-test/tree/main/skills/screenshot-protocol
Command: npx skills add https://github.com/visual-z/agent-test --skill agent-test-screenshot-protocol

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consistent, verifiable evidence is essential for automated UI testing. This Skill defines a standardized screenshot protocol for agent testing, ensuring every action is captured, properly named, and traceable to its place in the test route.

Core Features & Use Cases

Enforces a mandatory wait-before-screenshot sequence to stabilize page state before capture.
Establishes decision-point snapshots and a strict screenshot-to-step correlation for reliable bug reports.
Applies standardized naming conventions for route, phase, and action, enabling easy navigation in route reports.
Defines a minimum evidence set (baseline, action results, transitions, error states, final state) to balance evidence quality and volume.
Supports integration with DFS-based route exploration to ensure full state visibility during testing.

Quick Start

Start a test run by launching the agent browser workflow and following the DFS screenshot protocol to capture decision-point screenshots.

Frequently Asked Questions about agent-test:screenshot-protocol

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

FAQPage Schema

How do I capture consistent UI test screenshots during automated agent testing?▼

Standardized screenshot protocols enforce a mandatory wait-before-screenshot sequence to stabilize the page state before capture, ensuring every action is properly named and traceable to its place in the test route.

What is a wait-before-screenshot protocol and why is it needed for decision-point snapshots?▼

A wait-before-screenshot protocol is a mandatory stabilization sequence required before capturing decision-point snapshots, ensuring the modern web application page state is fully loaded for reliable bug reports.

How do I name screenshots for traceable route reports in DFS exploration?▼

To name screenshots for traceable route reports in DFS exploration, apply standardized naming conventions for route, phase, and action, enabling easy navigation and strict screenshot-to-step correlation.

What minimum evidence set should I capture for automated QA testing?▼

The minimum evidence set for automated QA testing includes baseline, action results, transitions, error states, and final state, balancing evidence quality and volume across modern web applications.

Can I use standardized screenshot protocols for error-state capture across modern web applications?▼

Yes, standardized screenshot protocols support error-state capture across modern web applications by defining a minimum evidence set and integrating with DFS-based route exploration to ensure full state visibility during testing.