screenshot

Generate labeled screenshots with deterministic capture context and metadata logging.

7|Updated Feb 14, 2026

Search Tags:#qa #metadata #screenshot #bug-triage #visual-evidence #reproducible-artifacts

Ready to run

npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill screenshot-kentoshimizu

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: screenshot
Source: https://github.com/KentoShimizu/sw-agent-skills/tree/main/skills/screenshot
Command: npx skills add https://github.com/KentoShimizu/sw-agent-skills --skill screenshot-kentoshimizu

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes assets (resource) components.

What problem does it solve?

Visual evidence capture for engineering and QA tasks often suffers from non-deterministic captures, inconsistent context, and missing traceability. This skill standardizes screenshot creation to produce reproducible artifacts that can be reviewed and audited.

Core Features & Use Cases

Deterministic capture conditions (viewport, theme, locale, seed data) to ensure repeatable results.
Metadata logging and consistent artifact naming to simplify triage and audits.
Use Case: when diagnosing a regression or validating a fix, generate an evidence set that clearly shows the system state before and after.

Quick Start

Instruct the agent to capture a reproducible screenshot sequence for the specified bug scenario.

Frequently Asked Questions about screenshot

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

FAQPage Schema

How do I capture reproducible screenshots for bug triage?▼

Reproducible screenshots for bug triage require enforcing deterministic capture conditions like viewport, theme, and locale. This standardizes visual evidence creation to produce stable artifacts that can be reliably reviewed and audited during development.

What is deterministic screenshot capture in QA workflows?▼

Deterministic screenshot capture in QA workflows is the process of standardizing visual evidence by logging metadata and applying consistent artifact naming. It ensures that visual proofs for regressions or fixes are traceable and repeatable across different validation environments.

How do I generate visual evidence for a regression validation?▼

To generate visual evidence for a regression validation, instruct the agent to capture a reproducible screenshot sequence for the specified bug scenario. This produces a labeled evidence set showing the system state before and after the implementation fix.

Does this screenshot skill require specific seed data or environment setup?▼

Yes, generating reproducible artifacts requires setting deterministic capture conditions including specific seed data, viewport, theme, and locale. Configuring these environment parameters beforehand ensures the captured visual evidence remains stable and consistent for audits.

Why are my QA screenshots inconsistent across different test runs?▼

QA screenshots are inconsistent across different test runs because of non-deterministic captures and missing traceability. Applying stable state capture, metadata logging, and consistent artifact naming resolves this by standardizing the capture context for every visual proof.

What is the best way to attach metadata to visual proof artifacts?▼

The best way to attach metadata to visual proof artifacts is by leveraging template assets that enforce stable state capture and consistent artifact naming. This ensures every screenshot includes the deterministic capture context needed for triage and audits.