agent-browser

Automate browser navigation, element interactions, and form submissions across web applications.

1|Updated Jan 18, 2026
One-click install
npx skills add https://github.com/anntnzrb/agents --skill agent-browser-anntnzrb
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-browser
Source: https://github.com/anntnzrb/agents/tree/main/assets/skills/agent-browser
Command: npx skills add https://github.com/anntnzrb/agents --skill agent-browser-anntnzrb

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Automates browser interactions for web testing, form filling, screenshots, and data extraction, reducing manual navigation and repetitive tasks across web applications.

Core Features & Use Cases

  • Page Navigation & Snapshotting: Open pages, capture accessibility trees, and identify interactive elements for reliable automation.
  • Interaction & Form Handling: Click, fill, type, select, and drag interactions using element references or semantic finders.
  • Data Extraction & Validation: Retrieve text, attributes, and titles, capture screenshots, and verify page state for QA or data pipelines.

Quick Start

Open a page and interact with elements using references from snapshot outputs.

Frequently Asked Questions about agent-browser

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

FAQPage Schema
How do I automate browser tasks like form filling and data extraction across multiple pages?

Browser automation streamlines testing, data collection, and form submission by applying commands for navigation, element discovery, and state verification across web pages. You open pages, capture accessibility trees, and interact with elements using references from snapshot outputs.

What's the best way to capture screenshots and verify page state for QA workflows?

Capturing screenshots and verifying page state for QA workflows involves using browser automation to retrieve text, attributes, and titles from web applications. You navigate to target pages, snapshot the accessibility tree, and validate the retrieved information against expected results.

Does browser automation support interactions with elements inside multiple frames?

Browser automation supports reliable navigation, element discovery, and state verification across multiple pages or frames. You can click, fill, type, select, and drag interactions using element references or semantic finders within these nested structures.

Can I use element references to click and fill forms without manual element discovery?

Form filling relies on element references extracted from snapshot outputs to click, fill, type, and select form fields. You open a page, capture the accessibility tree, and pass the discovered element references directly to interaction commands.

What do I need to run browser automation for automated testing setups?

Running browser automation for testing setups requires a browser automation engine to execute navigation, snapshotting, and interaction commands. No additional dependencies are listed, but the engine must support capturing accessibility trees and managing page state.

Why does browser automation require snapshotting before interacting with elements?

Browser automation requires snapshotting because it captures the accessibility tree, which identifies interactive elements and generates the element references needed for reliable interactions. Without snapshots, commands cannot accurately target elements for clicking, filling, or data extraction.