skills.rest
aimasteracc
aimasteraccCOMMUNITY
Explore all skills by this author →
GitHub

browse

Drive a local headless browser to navigate URLs, interact with elements, and verify page state.

46|13|Updated Jul 30, 2025
Search Tags:#automation#screenshots#playwright#browser#headless#qa-testing
One-click install
npx skills add https://github.com/aimasteracc/tree-sitter-analyzer --skill browse-aimasteracc
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browse
Source: https://github.com/aimasteracc/tree-sitter-analyzer/tree/main/.claude/skills/browse
Command: npx skills add https://github.com/aimasteracc/tree-sitter-analyzer --skill browse-aimasteracc

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires bun, perl, sed, and includes scripts (resource) components.

What problem does it solve?

Fast, reliable browser automation for QA testing and site dogfooding. It enables AI agents to navigate URLs, interact with elements, verify page state, and capture evidence without manual testing effort.

Core Features & Use Cases

  • Headless browser automation for QA: navigate pages, interact with UI, and assert outcomes.
  • Evidence generation: diff pages, take annotated screenshots, and verify responsive layouts.
  • Use cases include feature verification, deployment checks, and end-to-end user-flow testing across multiple pages.

Quick Start

Open a URL, interact with elements, and capture a screenshot to verify your result.

Frequently Asked Questions about browse

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

FAQPage Schema
How do I automate headless browser QA testing for dynamic content?▼

Headless browser QA testing for dynamic content is automated by driving a local runtime to navigate URLs, interact with elements, and verify page state. This enables testing workflows across multiple pages and responsive layouts without manual effort.

Can I capture annotated screenshots as evidence during Playwright automation?▼

You can capture annotated screenshots and generate page diffs during browser automation. This evidence generation supports feature verification, deployment checks, and end-to-end user-flow testing across multiple pages.

Do I need Playwright and bun installed to run headless browser automation?▼

Playwright integration and a browser runtime are required to run this headless browser automation. The environment also requires bun, perl, and sed dependencies to execute deterministic commands with structured outputs.

What is the best way to verify responsive layouts across multiple pages?▼

The best way to verify responsive layouts across multiple pages is using headless browser automation to navigate dynamic content and assert outcomes. It drives a local browser to interact with UI elements and capture visual evidence.

How do I generate page diffs to verify deployment changes?▼

You generate page diffs to verify deployment changes by driving a headless browser to navigate URLs and capture evidence. This automation supports feature verification and end-to-end user-flow testing with structured outputs.

Related Skills

Explore More Software Engineering Skills→
kuroRykuroRy

playwright-cli

Automate browser interactions for web testing and data extraction.

Community
Advanced
mulyovedmulyoved

browse

Navigate headless browsers to automate QA testing and site verification.

Community
Advanced
WillNigriWillNigri
33

browse

Drive headless browsers to automate end-to-end QA testing and capture screenshots.

Community
Advanced
tutur3ututur3u
53

agent-browser

Drive the agent-browser CLI to navigate pages, fill forms, and extract data.

Official
Advanced