agent-browser

Automate browser navigation, form filling, and data extraction via commands.

Updated Jan 5, 2026
One-click install
npx skills add https://github.com/LLLLimbo/Skills --skill agent-browser-llllimbo
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: agent-browser
Source: https://github.com/LLLLimbo/Skills/tree/main/front-development/agent-browser
Command: npx skills add https://github.com/LLLLimbo/Skills --skill agent-browser-llllimbo

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill automates browser interactions for web testing, form filling, screenshots, and data extraction, reducing repetitive manual tasks and increasing reliability.

Core Features & Use Cases

  • Navigate to webpages and manage browser sessions programmatically.
  • Snapshot elements by refs or semantic locators, then automate clicks, fills, and data extraction.
  • Take screenshots, wait for page states, and verify results for testing and QA workflows.
  • Example use cases include automated login flows, multi-page form submissions, and cross-site data capture.

Quick Start

Use the agent-browser command to open a URL, snapshot interactive elements, interact with elements via refs or semantic locators, wait for results, and capture outputs. agent-browser open https://example.com agent-browser snapshot -i agent-browser click @e1 agent-browser fill @e2 "text" agent-browser screenshot

Frequently Asked Questions about agent-browser

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

FAQPage Schema
How do I automate web testing and form filling across multiple pages?

To automate web testing and form filling, you programmatically navigate to URLs, snapshot interactive elements by refs, and execute clicks and fills. This manages multi-page form submissions and cross-site data capture through a command-based workflow.

Can I extract data from web pages using semantic locators instead of CSS selectors?

Yes, data extraction supports semantic locators alongside refs to identify elements. You snapshot the page to capture these locators, which allows automated scripts to interact with elements and extract data without relying on specific CSS selectors.

What is the best way to capture screenshots during automated browser navigation?

The best way to capture screenshots during browser navigation is to use a dedicated screenshot command within an automated workflow. This captures visual outputs of the current page state, which is essential for visual verification in QA testing.

Does automated browser interaction require external dependencies for session management?

No, automated browser interaction and session management do not require external dependencies. The Skill provides built-in commands to open URLs, manage browser sessions, wait for page states, and execute interactions natively.

How do I verify page states and wait for results in an automated login flow?

To verify page states in an automated login flow, you use wait commands to pause execution until specific conditions are met. After filling forms and submitting, you take screenshots to verify the resulting page state visually.

When should I not use command-based browser automation for data extraction?

You should not use command-based browser automation when static HTML parsing is sufficient. If a website does not require JavaScript execution for rendering or element interaction, simpler data extraction methods are more efficient than managing full browser sessions.