browser-automation

Automate browser interactions, snapshots, and downloads across logged-in accounts using Playwright-compatible REPL.

Updated Jul 11, 2026
One-click install
npx skills add https://github.com/danielsuguimoto/skills --skill browser-automation-danielsuguimoto
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: browser-automation
Source: https://github.com/danielsuguimoto/skills/tree/main/skills/browser-automation
Command: npx skills add https://github.com/danielsuguimoto/skills --skill browser-automation-danielsuguimoto

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Manual browser work like QA testing, form filling, data downloads, and cross-account verification is repetitive and error-prone. This Skill gives an agent direct control of the user's real browser sessions, including logged-in accounts, cookies, and open tabs. ## Core Features & Use Cases - Two control surfaces: Browser exec for autonomous whole-task delegation, and a persistent Playwright-compatible REPL for deterministic, step-by-step interaction. - Accessibility-tree snapshots: Read pages via compact snapshots with ref IDs for reliable element targeting, plus annotated screenshots for visual verification. - Downloads and evidence capture: Handle direct downloads, blob URLs, and POST-backed exports, saving verified artifacts locally. - Use Case: Ask the agent to log into your SaaS dashboard, navigate to the reports page, export a CSV, and verify the downloaded file contents — all without manual clicking. ## Quick Start Use browser automation to open my current tab, snapshot the page, and click the export button to download the report.

Frequently Asked Questions about browser-automation

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

FAQPage Schema
How do I automate browser tasks with Playwright in a logged-in session?▼

Use the browser REPL, which provides a persistent Playwright-compatible page object connected to the user's real browser with cookies and logged-in accounts. Attach to an open tab with attachActiveBrowserTab() or open a new one with openTab(), then drive interactions through snapshot ref IDs.

What is the difference between browser exec and browser REPL?▼

Browser exec spawns an autonomous agent session for whole-task delegation across accounts and history, while the REPL gives direct low-level Playwright control for deterministic steps, screenshots, and downloads. Choose exec for delegation and REPL for precise verification.

How do I click elements reliably without guessing CSS selectors?▼

Take a snapshot with snapshot(page, { interactive: true }) to get an accessibility tree with unique ref IDs like e12, then pass those refs to page.locator(). Refs are invalidated after each action, so always take a fresh snapshot before the next interaction.

Can browser automation download files from blob URLs or export buttons?▼

Yes, use page.waitForEvent('download') before clicking the export button, then verify the result with download.path() and optionally save a copy with download.saveAs(). The fetch() helper only works for same-origin trusted direct-download URLs.

Why does my browser automation fail after clicking an element?▼

Each action invalidates previous snapshot ref IDs, so stale refs cause failures. Take a new snapshot after every action and treat the action as unconfirmed until a fresh snapshot shows the expected state.