browser

Automates web browser navigation, interaction, and data extraction using AI-optimized accessibility snapshots.

Updated May 8, 2026
One-click install
npx skills add https://github.com/FrekiManagarm/d-chambaud --skill browser-frekimanagarm
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser
Source: https://github.com/FrekiManagarm/d-chambaud/tree/main/.agents/skills/browser
Command: npx skills add https://github.com/FrekiManagarm/d-chambaud --skill browser-frekimanagarm

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual web browsing for testing, scraping, and form automation is slow and error-prone, and raw DOM dumps overwhelm AI agents with irrelevant markup. This Skill provides browser automation with compact accessibility-tree snapshots that reduce context usage by 93% through element references. ## Core Features & Use Cases - AI-Optimized Snapshots: Capture interactive elements only with stable refs (@e1, @e2) instead of full DOM trees, making page state cheap to reason about. - Full Interaction Set: Click, fill, type, hover, select, scroll, and wait for elements, text, URLs, or network idle states. - Isolated Sessions: Run parallel browser sessions with saved authentication state for multi-agent or swarm workflows. - Use Case: Automate a login flow by opening the page, snapshotting interactive elements, filling credentials via refs, clicking submit, and waiting for the dashboard URL. ## Quick Start Ask the agent to open a website with the browser skill, take an interactive snapshot, and click or fill elements using the returned refs.

Frequently Asked Questions about browser

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

FAQPage Schema
How do I automate browser interactions with an AI agent?▼

Open a URL with agent-browser, run snapshot -i to get interactive elements with refs like @e2, then use click, fill, or type commands against those refs. Re-snapshot after any navigation since page state changes.

How to fill and submit a web form programmatically?▼

Navigate to the form page, take an interactive snapshot to identify input refs, use fill for each field, click the submit button ref, then wait for confirmation text or a URL change to verify submission.

What is the difference between element refs and CSS selectors in browser automation?▼

Element refs come from accessibility snapshots and remain stable across minor DOM changes, making them more deterministic. CSS selectors like #submit work but break more easily when page structure changes.

Can I run multiple browser sessions in parallel?▼

Yes, use the --session flag to create isolated sessions, each with its own browser state. You can save authentication state from one session and load it into another for shared login contexts.

Why does my browser automation fail after clicking a link?▼

Element refs become stale after navigation or DOM updates. Always take a fresh snapshot after page changes before interacting again, and use wait commands for URLs, text, or network idle states.