Verified:GitHub

inspect

Map artifacts into structured inventories of pages, controls, dialogs, and capture targets.

1|Updated May 19, 2026

Search Tags:#evidence planning #ui analysis #page inventory #route discovery #artifact inspection #product intake #capture targets

Ready to run

npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill inspect-edonghyun

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: inspect
Source: https://github.com/edonghyun/donghyuns-agent-tools/tree/main/plugins/feature-intake/skills/inspect
Command: npx skills add https://github.com/edonghyun/donghyuns-agent-tools --skill inspect-edonghyun

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps you quickly understand an unknown product artifact before intake so you can capture the right evidence instead of guessing what matters.

Core Features & Use Cases

Artifact discovery: Identifies pages, routes, views, and other surfaces in local projects, URLs, static exports, or screenshot bundles.
Evidence planning: Classifies controls, dialogs, states, and integration signals so capture work can be scoped accurately.
Blocker awareness: Flags dead paths, hidden functionality, and source-backed limitations before analysis begins.
Use case: A product analyst can point this Skill at a prototype or demo and get a structured inventory that drives browser capture and intake documentation.

Quick Start

Use the inspect skill to inventory this artifact’s pages, controls, dialogs, integration signals, and capture targets before starting product intake.

Frequently Asked Questions about inspect

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

FAQPage Schema

How do I inventory pages and controls in an unknown product artifact?▼

Product intake requires mapping the artifact into a structured inventory of pages, controls, and capture targets. This process classifies integration signals and flags dead paths or hidden functionality before analysis begins.

What is evidence planning for UI analysis and when do I need it?▼

Evidence planning for UI analysis classifies controls, dialogs, and states to scope capture work accurately. You need it when understanding an unknown prototype or demo before starting product intake.

Can I use artifact inspection on static exports and screenshot sets?▼

Yes, artifact inspection supports local projects, URLs, static exports, screenshot sets, and design bundles. It performs route discovery and interaction classification without modifying source files.

How do I identify dead paths and hidden functionality during route discovery?▼

Identify dead paths and hidden functionality by applying artifact inspection to map routes and detect source-backed limitations. This blocker awareness flags inaccessible paths and limitations before analysis begins.

What is the best way to prepare a prototype for product intake documentation?▼

The best way to prepare a prototype for product intake is to generate a structured inventory of its pages, controls, and integration signals. This evidence planning drives browser capture and intake documentation by highlighting capture targets.