browse

Report visible elements, layout, and accessibility structure of a web page.

6|2|Updated Apr 5, 2026
One-click install
npx skills add https://github.com/i-standard1/yamasaki --skill browse-i-standard1
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/i-standard1/yamasaki/tree/main/.claude/skills/browse
Command: npx skills add https://github.com/i-standard1/yamasaki --skill browse-i-standard1

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill provides an AI-assisted way to quickly observe and understand the current UI state of a web page by driving a browser automation tool to capture screenshots, extract accessibility trees, and perform lightweight interactions, reducing manual inspection time.

Core Features & Use Cases

  • UI state observation: Open pages, render the current layout, and report visible elements and accessibility structure.
  • Visual verification: Capture screenshots and generate a concise UI state report for bug triage and design reviews.
  • Exploratory checks: Interact with forms and navigate flows to quickly assess behavior without writing tests.

Quick Start

Open the target URL and report the current UI state using agent-browser.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I capture a web page screenshot for bug investigation?

To capture a web page screenshot for bug investigation, this skill drives browser automation to render the current layout and extract visible elements. It observes the UI state and generates a concise report for triaging visual defects.

What is an accessibility tree and how does it help with visual inspection?

An accessibility tree maps the semantic structure of a UI. This skill extracts it during visual inspection to report visible elements and layout, helping verify design compliance and understand how assistive technologies interpret the page.

Can I use browser automation to verify UI layout without writing tests?

Yes, you can use browser automation to verify UI layout without writing tests. This skill performs exploratory checks by navigating flows and interacting with forms to assess behavior and report the current design state.

Does this approach work for design verification across web apps and dashboards?

Yes, this approach works for design verification across web apps and dashboards. It identifies the current UI state, captures screenshots, and reports the layout and accessibility structure to streamline design reviews.

What are the limitations of using AI for UI state observation?

A key limitation of using AI for UI state observation is that it does not execute tests. It is built strictly for exploratory reviews, capturing screenshots and extracting accessibility trees to report visible elements rather than validating functional logic.