capture

Captures page-by-page screenshots and interaction states for product analysis workflows.

1|Updated May 19, 2026
One-click install
npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill capture-edonghyun
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: capture
Source: https://github.com/edonghyun/donghyuns-agent-tools/tree/main/plugins/feature-intake/skills/capture
Command: npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill capture-edonghyun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill removes the manual burden of collecting visual proof for product analysis, so teams can review pages, controls, dialogs, and state changes with consistent evidence instead of memory or screenshots taken ad hoc.

Core Features & Use Cases

  • Page and route traversal: Walk a runnable app or supplied prototype and capture stable screenshots for each reachable view.
  • Interaction evidence: Record what happens after clicks, tabs, menus, dialogs, uploads, exports, loading states, errors, and disabled guards.
  • Parity and comparison work: Separate baseline and current evidence for PoC-to-product checks, UI iteration review, and before/after comparisons.
  • Output packaging: Write organized screenshot folders, indexes, README notes, and contact sheets so downstream analysis can cite the evidence reliably.

Quick Start

Ask the capture skill to traverse the target app and collect page-by-page screenshots, interaction states, and contact sheets for the specific feature intake slug you want analyzed.

Frequently Asked Questions about capture

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

FAQPage Schema
How do I automatically capture screenshots for feature intake and UI analysis?

To automatically capture screenshots for feature intake, this Skill traverses runnable apps or prototypes to record stable full-page captures of each view, interaction state, and dialog without modifying the application source.

What is the best way to record interaction states like loading and error dialogs during page traversal?

Recording interaction states during page traversal requires capturing screenshots after clicks, uploads, and menu toggles. This Skill systematically documents loading, errors, and disabled guards to provide consistent visual proof.

Can I use this for PoC-to-product parity checks and before/after UI comparisons?

Yes, you can use this for PoC-to-product parity checks by separating baseline and current evidence. It captures consistent visual proof to support UI iteration review and before/after comparisons reliably.

How do I package screenshot indexes and contact sheets for downstream product analysis?

Packaging screenshot indexes and contact sheets involves writing organized screenshot folders alongside README notes. This Skill outputs structured evidence packages so downstream product analysis can cite the captured UI states reliably.

Does capturing screenshot evidence work with mobile and desktop browser-visible apps?

Yes, capturing screenshot evidence works with browser-visible apps, mobile, and desktop page flows. The Skill applies to various platforms, capturing controls and state changes as long as the application source remains unmodified.

What are the limitations of using automated screenshot capture for feature intake?

A key limitation of automated screenshot capture is that it requires a stable, runnable app or supplied prototype to traverse. It records visual evidence and blockers without modifying application source code or executing functional tests.