agentsclimarketplace

Browser agent automation

Skill m00kk/agent-skills-playbook/skills/browser-agent-automation

Automates web tasks with LLM-driven browsers using Playwright, Browser-Use, or Playwright MCP. Use for browser automation agents, scraping with agents, form filling, or E2E flows described in natural language.From its SKILL.md

Install
npx -y skills add m00kk/agent-skills-playbook --skill browser-agent-automation

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

1.8 KB, 354 tokens by cl100k_base, as published. Nobody here has run it

Browser Agent Automation

Choose approach

ApproachBest for
Playwright MCPExisting Playwright tests; IDE agents
Browser-Use (Python)Greenfield "do this on the site" tasks
Cursor IDE browser MCPInteractive debugging in Cursor

Default: Playwright MCP in Cursor; Browser-Use for standalone Python agents.

Safety rules

  • Never automate login without explicit user consent in session
  • Respect robots.txt and site ToS for bulk scraping
  • Cap steps (e.g. 30 actions) and timeout per navigation
  • Do not exfiltrate cookies/localStorage to logs

Workflow

- [ ] Define goal and success condition (URL, element, downloaded file)
- [ ] Start from known URL; avoid open-ended googling
- [ ] Use accessibility snapshots before clicks (prefer refs/roles)
- [ ] Verify after each critical action (screenshot or DOM check)
- [ ] On failure: one alternate strategy, then stop and report

Playwright MCP (Cursor)

  1. List tabs → navigate → lock → snapshot
  2. Interact via dedicated browser tools (not raw CDP input)
  3. Unlock when done

Reliability patterns

  • Wait for network idle or specific selector, not fixed sleeps
  • Idempotent clicks: confirm state changed
  • For forms: fill → validate → submit → verify confirmation text

Anti-patterns

  • Brittle CSS selectors when role+name available
  • Infinite retry loops on captcha/login walls
  • Storing credentials in skill files or repo

Report blockers (captcha, 2FA) and ask user to take over.

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.