browser-automation

Automate browser workflows by navigating sites, interacting with elements, and capturing screenshots or DOM snapshots.

45|6|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/ramp-public/ramp-cli --skill browser-automation-ramp-public
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: browser-automation
Source: https://github.com/ramp-public/ramp-cli/tree/main/src/ramp_cli/skills/browser-automation
Command: npx skills add https://github.com/ramp-public/ramp-cli --skill browser-automation-ramp-public

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Browser automation removes the need for you to manually click through complex websites by letting an AI-driven browser navigate pages, fill forms, and capture page state for reliable continuation of web tasks.

Core Features & Use Cases

  • Navigate and operate real websites: open pages, click elements, fill fields, and press keys to complete multi-step workflows.
  • Persistent sessions for logins and cookies: maintains a long-lived Chrome profile so authenticated tasks can resume across sessions.
  • Capture and extract page state: generate screenshots and DOM snapshots (YAML accessibility trees) to locate elements and verify what the browser is showing.
  • Use Case: when you need to submit a payment or checkout form on a logged-in site, the skill uses a persistent headed browser profile and snapshots to keep the workflow accurate and resumable.

Quick Start

Use the browser-automation skill to open https://example.com in a persistent Chrome session and take a snapshot so you can target elements by their refs.

Frequently Asked Questions about browser-automation

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

FAQPage Schema
How do I automate form filling and web scraping with a persistent Chrome session?

You can automate web scraping and form filling by using a persistent Chrome profile to navigate pages, interact with UI elements, and capture DOM snapshots for reliable task continuation. The skill maintains logins and cookies across sessions.

How do I extract structured page content using DOM snapshots during browser automation?

You extract page content by generating YAML accessibility tree DOM snapshots. These snapshots locate interactive elements by their refs, enabling programmatic clicking, typing, and form filling during automated web workflows.

Does playwright-cli work with persistent Chrome profiles for automated logins?

Yes, playwright-cli supports persistent Chrome profiles for automated logins. The skill maintains a long-lived profile at ~/.pw-agent/.playwright-profile, allowing authenticated tasks and session cookies to resume across multiple runs.

Can I automate multi-step checkout workflows with a headed browser?

Yes, you can automate multi-step checkout workflows using headed browser operation by default. The skill navigates pages, fills checkout-adjacent forms, and uses snapshot-driven element refs to keep interactive workflows accurate and resumable.

Why do I need a persistent Chrome profile for web automation tasks?

A persistent Chrome profile is needed to maintain a long-lived session state for web automation tasks. It preserves logins, cookies, and authenticated contexts so that interactive multi-step website journeys can resume reliably across separate runs.

What are the limitations of snapshot-driven element refs in browser automation?

Snapshot-driven element refs require playwright-cli with headed Chrome operation by default and a persistent profile at ~/.pw-agent/.playwright-profile. They rely on DOM snapshots to locate elements, meaning dynamic page changes may require new snapshots for accurate programmatic actions.