Browser Automation

Use when a task requires navigating websites, filling forms, extracting structured page data, capturing screenshots or PDFs, or validating an end-to-end browser flow; use explicit selectors, bounded waits, and user-approved destinations.

9 stars 3 forksProductivity & Notes

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add sandbaseai/workbuddy-skill --skill browser-automation
Manual install
git clone --depth 1 https://github.com/sandbaseai/workbuddy-skill.git /tmp/workbuddy-skill
mkdir -p ~/.claude/skills
cp -r /tmp/workbuddy-skill/skills/browser-automation ~/.claude/skills/browser-automation

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Browser Automation

Use a real browser client to complete a concrete, authorized task. Before acting, identify the target origin, intended outcome, authentication state, data sensitivity, and whether the action is read-only or changes external state. Never infer permission to access private sites, bypass controls, or submit irreversible changes.

## Plan the flow

1. Confirm the exact URL or application origin and the user-visible goal.
2. Check the available browser client and its version; prefer the repository's existing tool and conventions.
3. Open the page and capture a fresh DOM snapshot or accessibility tree.
4. Use stable semantic selectors, labels, roles, or test IDs. Avoid coordinates and brittle generated classes.
5. After navigation, modal changes, tab switches, or significant DOM updates, capture a new snapshot before using element references.
6. Bound navigation, selector, download, and retry waits; stop and report the failing stage when a bound expires.

## Interact safely

Prefer `goto`, snapshot, inspect, interact, and snapshot again. For forms, verify field labels, destination, and visible validation before submitting. Treat file uploads, purchases, account changes, deletion, publication, messages, and permission changes as external side effects: preview the exact payload and obtain explicit user authorization immediately before the irreversible action.
Read the full skill on GitHub

Details

Skill name
browser-automation
Path
skills/browser-automation/SKILL.md
License
MIT
Repo updated
8 September 2026

FAQ

What does the Browser Automation skill do?

Use when a task requires navigating websites, filling forms, extracting structured page data, capturing screenshots or PDFs, or validating an end-to-end browser flow; use explicit selectors, bounded waits, and user-approved destinations.

How do I install the Browser Automation skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add sandbaseai/workbuddy-skill --skill browser-automation. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Browser Automation popular?

It lives in sandbaseai/workbuddy-skill, which has 9 GitHub stars and 3 forks.

Related skills

Browse the most popular Claude skills, all productivity & notes skills, or write your own with the skills generator.