Agent skill · Security

core

Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.

Friday Platform98★ · 1 repos on radarProfile →
claude-coderead-onlyNOASSERTION
Install
npx skills add friday-platform/friday-studio --skill skill --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 9
SKILL.md size: 16 KB
Bundled scripts: none
Allowed tools: Bash(agent-browser:*)Bash(npxagent-browser:*)
Path: packages/bundled-agents/src/web/skill/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 98
Language: TypeScript
Read our review of the source →

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# agent-browser core Fast browser automation CLI for AI agents. Chrome/Chromium via CDP, no Playwright or Puppeteer dependency. Accessibility-tree snapshots with compact `@eN` refs let agents interact with pages in ~200-400 tokens instead of parsing raw HTML. Most normal web tasks (navigate, read, click, fill, extract, screenshot) are covered here. Load a specialized skill when the task falls outside browser web pages — see [When to load another skill](#when-to-load-another-skill). ## The core loop ```bash agent-browser open <url> # 1. Open a page agent-browser snapshot -i # 2. See what's on it (interactive elements only) agent-browser click @e3 # 3. Act on refs from the snapshot agent-browser snapshot -i # 4. Re-snapshot after any page change ``` Refs (`@e1`, `@e2`, ...) are assigned fresh on every snapshot. They become **stale the moment the page changes** — after clicks that navigate, form submits, dynamic re-renders, dialog opens. Always re-snapshot before your next ref interaction. ## Quickstart ```bash # Install once npm i -g agent-browser && agent-browser install # Take a screenshot of a page agent-browser open https://example.com agent-browser screenshot home.png agent-brow

What's inside
Steps it walks through
  1. The core loop
  2. Quickstart
  3. Reading a page
  4. Interacting
  5. When refs don't work or you don't want to snapshot
  6. Waiting (read this)
  7. Common workflows
  8. Log in
  9. Persist session across runs
  10. Extract data
  11. Screenshot
  12. Handle multiple pages via tabs
  13. Run multiple browsers in parallel
  14. Mock network requests
Ships with 8 files
  • references/authentication.md
  • references/commands.md
  • references/profiling.md
  • references/proxy-support.md
  • references/session-management.md
  • references/snapshot-refs.md
  • references/trust-boundaries.md
  • references/video-recording.md
Commands it runs
agent-browser open <url>        # 1. Open a page
agent-browser snapshot -i       # 2. See what's on it (interactive elements only)
agent-browser click @e3         # 3. Act on refs from the snapshot
agent-browser snapshot -i       # 4. Re-snapshot after any page change
Install once
npm i -g agent-browser && agent-browser install
Take a screenshot of a page
agent-browser open https://example.com
agent-browser screenshot home.png
agent-browser close
More from friday-studio
All skills →
workspace-apiCreate, list, update, delete, and clean up workspaces via the daemon HTTP API at $FRIDAYD_URL. Use…Testing & QAauthoring-skillsAuthors new agent skills that follow the Anthropic + agentskills.io specification. Use when the…Code Review & Qualitycomposing-contextInternal pattern guide for composing turn-local retrieval-gated context into a synthetic…AI & Agentsdebugging-broken-jobsTriage entry-point for any "the job ran but something's wrong" situation in a Friday workspace.…Code Review & Qualitydebugging-empty-outputLoads when a workspace job tool returns `success: true, status: completed` AND (`summary: ""` OR…Workflow & Productivitycomposing-emailsGeneral styling and tone guidelines for composing HTML emails. Use when writing email copy that…Data & Analytics
About this skill
What does the core skill do?

Core agent-browser usage guide. Read this before running any agent-browser commands. Covers the snapshot-and-ref workflow, navigating pages, interacting with elements (click, fill, type, select), extracting text and data, taking screenshots, managing tabs, handling forms and auth, waiting for content, running multiple browser sessions in parallel, and troubleshooting common failures. Use when the user asks to interact with a website, fill a form, click something, extract data, take a screenshot, log into a site, test a web app, or automate any browser task.

How do I install it?

Run `npx skills add friday-platform/friday-studio --skill skill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From friday-platform/friday-studio, a repository with 98 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going
All skills →
The full catalog, by category and by tool.
Open Source Radar →
The repositories these skills come from, watched daily.
The people behind them →
Makers and builders across the ecosystem.