agentleFS
Sign inStart free
ZenRowsZenRows/cli/skills/interact-browser/SKILL.md

interact-browser

Skill16 starsChanged 27 days agoMITView on GitHub

Escalate to browser sessions only when fetch/extract cannot do the job.

The file

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Prefer zenrows browser run <script.json> for multi-step flows (auto-closes).

    line 26
  2. Very specific:

    Always close interactive sessions — billed by bandwidth + session time (15-min hard cap).

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Interact / Browser Sessions

Operate protected browser workflows (logins, clicks, forms, multi-step flows, persistent cookies) on JS-heavy or interactive pages that Protected Fetch cannot handle. This is escalation only — use it only when Protected Fetch or Extract is insufficient.

Browser Sessions is a GA Zenrows product (formerly Scraping Browser), on by default (opt out with policy.allow_browser=false). It is escalation-only and costs more than fetch/extract: sessions bill by bandwidth + session time and auto-terminate after 15 minutes. Drive sessions with zenrows browser against the managed REST API (https://mcp.zenrows.com/browser/sessions/*, same backend as @zenrows/mcp browser_*). For raw CDP, zenrows browser connect prints the wss endpoint.

Rules

  • Try [[protected-fetch]] / [[extract]] first; escalate only with evidence — they cost less.
  • On by default; if a workspace opted out, re-enable with zenrows policy set allow_browser true.
  • Prefer zenrows browser run <script.json> for multi-step flows (auto-closes).
  • Always close interactive sessions — billed by bandwidth + session time (15-min hard cap).
  • select --value matches the option's value attribute (bare value or a CSS selector like option[value="2"]). Label text / index are not supported.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free