browser

Automate browser tasks to inspect UI, capture screenshots, fill forms, and extract page data.

14|2|Updated Jan 11, 2026
One-click install
npx skills add https://github.com/brsbl/ottonomous --skill browser-brsbl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser
Source: https://github.com/brsbl/ottonomous/tree/main/skills/browser
Command: npx skills add https://github.com/brsbl/ottonomous --skill browser-brsbl

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Browser automation with persistent page state for navigation, screenshots, forms, data extraction, and testing. Use when inspecting UI, taking screenshots, filling forms, extracting page data, verifying frontend behavior, or automating browser workflows.

Core Features & Use Cases

  • Persistent page sessions enable navigation, interaction, and validation across reloads.
  • Capture screenshots and ARIA snapshots for visual QA and accessibility checks.
  • Automate form filling, data extraction, and frontend testing in repeatable, auditable runs.

Quick Start

Start the browser server and connect a client to begin automating a session.

Frequently Asked Questions about browser

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

FAQPage Schema
How do I automate browser tasks while keeping the page state persistent across reloads?

Browser automation with persistent page sessions allows you to maintain navigation and interaction state across reloads. You connect a client to a hosted server interface to execute scripts that drive the session continuously.

Can I capture screenshots and ARIA snapshots for visual QA and accessibility checks?

Yes, you can capture screenshots and ARIA snapshots for visual QA and accessibility checks. The automation interface executes client scripts to grab page data and validate frontend behavior during repeatable runs.

How do I automate form filling and data extraction from web pages?

You automate form filling and data extraction by running client scripts through the automation server. These scripts navigate the persistent browser session to interact with elements and capture the extracted page data.

What do I need to set up before starting browser automation for UI testing?

Browser automation requires a persistent browser session model, a server to host the automation interface, and client scripts to execute navigation. Start the server and connect a client to begin automating your session.

Is browser automation suitable for exploratory testing and QA workflows on remote sites?

Yes, browser automation applies to QA workflows, exploratory testing, and front-end behavior automation across local or remote sites. It provides repeatable, auditable runs for verifying UI interactions and extracting data.

Why does my browser automation session lose state when navigating between pages?

Sessions lose state without a persistent page session model. This Skill maintains page state across reloads by hosting a continuous automation server interface, ensuring navigation and interactions persist throughout the run.