Agent skill

Browser Automation

Non-testing browser automation - web scraping, form filling, screenshot capture, PDF generation, workflow automation.

No licenceAuto-check passedProductivity & Automation

Install Browser Automation

skills CLI

$ npx skills add ynulihao/AgentSkillOS --skill browser-automation -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI

$ gh skill install ynulihao/AgentSkillOS browser-automation --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy

$ git clone --depth 1 https://github.com/ynulihao/AgentSkillOS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/data/skill_seeds/browser-automation .claude/skills/browser-automation && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Paste into Claude Code

Install the "browser-automation" agent skill from https://github.com/ynulihao/AgentSkillOS/tree/main/data/skill_seeds/browser-automation into .claude/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/ynulihao/AgentSkillOS/tree/main/data/skill_seeds/browser-automation

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add ynulihao/AgentSkillOS --skill browser-automation -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install ynulihao/AgentSkillOS browser-automation --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ynulihao/AgentSkillOS.git skills-src && mkdir -p .agents/skills && cp -r skills-src/data/skill_seeds/browser-automation .agents/skills/browser-automation && rm -rf skills-src

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "browser-automation" agent skill from https://github.com/ynulihao/AgentSkillOS/tree/main/data/skill_seeds/browser-automation into .agents/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add ynulihao/AgentSkillOS --skill browser-automation -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install ynulihao/AgentSkillOS browser-automation --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ynulihao/AgentSkillOS.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/data/skill_seeds/browser-automation .cursor/skills/browser-automation && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "browser-automation" agent skill from https://github.com/ynulihao/AgentSkillOS/tree/main/data/skill_seeds/browser-automation into .cursor/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/ynulihao/AgentSkillOS.git --path data/skill_seeds/browser-automation

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add ynulihao/AgentSkillOS --skill browser-automation -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install ynulihao/AgentSkillOS browser-automation --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ynulihao/AgentSkillOS.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/data/skill_seeds/browser-automation .gemini/skills/browser-automation && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "browser-automation" agent skill from https://github.com/ynulihao/AgentSkillOS/tree/main/data/skill_seeds/browser-automation into .gemini/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install ynulihao/AgentSkillOS browser-automation

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add ynulihao/AgentSkillOS --skill browser-automation -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

$ git clone --depth 1 https://github.com/ynulihao/AgentSkillOS.git skills-src && mkdir -p .github/skills && cp -r skills-src/data/skill_seeds/browser-automation .github/skills/browser-automation && rm -rf skills-src

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "browser-automation" agent skill from https://github.com/ynulihao/AgentSkillOS/tree/main/data/skill_seeds/browser-automation into .github/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add ynulihao/AgentSkillOS --skill browser-automation -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install ynulihao/AgentSkillOS browser-automation --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/ynulihao/AgentSkillOS.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/data/skill_seeds/browser-automation .opencode/skills/browser-automation && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "browser-automation" agent skill from https://github.com/ynulihao/AgentSkillOS/tree/main/data/skill_seeds/browser-automation into .opencode/skills/browser-automation/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser-automation", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: browser-automation
GitHub stars: 617
Token cost: ~2.2k tokens
SKILL.md length: 371 words
Files: 1
Skills in repo: 26
Repo updated: Mar 7, 2026
First seen: Oct 7, 2026
Licence: None found

At a glance

Non-testing browser automation - web scraping, form filling, screenshot capture, PDF generation, workflow automation.

Works in 12 steps: Playwright Automation → Testing Frameworks → Web Scraping → …
Tasks that involve Browser automation
SKILL.md covers Expertise Areas, Code Examples, Selector Strategies and Best Practices, plus 2 more sections
Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Browser Automation is an agent skill from ynulihao/AgentSkillOS. Non-testing browser automation - web scraping, form filling, screenshot capture, PDF generation, workflow automation. For TESTING with Playwright, use e2e-playwright skill instead. Activates for web scraping, form automation, screenshot, PDF, headless browser, Puppeteer, Selenium, automation scripts, data extraction.

Its SKILL.md is about 2.2k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Productivity & Automation, covering Browser automation, Browser testing and Web scraping. It works with Playwright, Puppeteer and Selenium. The repository describes itself as: Build your agent from 200,000+ skills via skill RETRIEVAL & ORCHESTRATION.

When your agent uses it

Tasks that involve Browser automation
Tasks that involve Browser testing
Tasks that involve Web scraping

Example prompts

“/browser-automation”

Workflow steps

12 steps, taken from the step headings in SKILL.md.

Playwright Automation
Testing Frameworks
Web Scraping
Form Automation
CSS Selectors (Preferred)
XPath (When CSS isn't enough)
Playwright-Specific
Use Stable Selectors
Add Explicit Waits
Handle Errors Gracefully
Clean Up Resources
Use Page Object Model (POM)

What it can do on your machine

Read from SKILL.md and the folder at commit c3cfae1. It shows what the files ask for, not the result of running them.

Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are typescript).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Browser Automation loads about 2.2k tokens when it runs. Until then it costs about 84 tokens; SKILL.md has 371 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~84
When it runs · the whole SKILL.md, loaded when a task matches: ~2.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

Without a licence we can't republish the file, so here is its outline and opening line. It has 371 words (~2,197 tokens).

“Expert in browser automation using Playwright, Puppeteer, and Selenium. Specializes in UI testing, web scraping, form automation, and automated workflows.”

— opening of SKILL.md by ynulihao

name: browser-automation

Outline of SKILL.md

Browser Automation Skill
Expertise Areas
1. Playwright Automation
2. Testing Frameworks
3. Web Scraping
4. Form Automation
Code Examples
Basic Page Navigation
Form Automation with Validation
Data Extraction from Multiple Pages
Network Interception
Visual Regression Testing
Selector Strategies
1. CSS Selectors (Preferred)
2. XPath (When CSS isn't enough)
3. Playwright-Specific
Best Practices
1. Use Stable Selectors
2. Add Explicit Waits
3. Handle Errors Gracefully
4. Clean Up Resources
5. Use Page Object Model (POM)
Common Pitfalls
1. Race Conditions
2. Stale Element References
3. Timing Issues with Dynamic Content
Debugging Tools
1. Headful Mode
2. Screenshot on Failure
3. Trace Recording

Read the full SKILL.md on GitHub

Files

Just SKILL.md in data/skill_seeds/browser-automation of ynulihao/AgentSkillOS.

Open the folder on GitHubat commit c3cfae1

Compare with similar skills

Browser Automation next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Browser Automation compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Browser Automation this skillynulihao/AgentSkillOS	617	—	~2.2k	Automated safety check: Pass	None	7 mo ago
Cloudflare Browser Renderingeinverne/dotfiles	121	—	~4.9k	Automated safety check: Pass	GPL-3.0	29 days ago
Open BrowserJasonHonKL/Openbrowser	114	—	~1.6k	Automated safety check: Pass	MIT	5 mo ago
Agent Browseroxylabs/agent-skills	875	—	~3k	Automated safety check: Pass	MIT	8 days ago
Agenttinyfish-io/tinyfish-cookbook	2.2k	—	~1.1k	Automated safety check: Pass	MIT	7 days ago
Browser Automationdavila7/claude-code-templates	32k	3 repos	~569	Automated safety check: Pass	MIT	today

Similar skills

Cloudflare Browser Rendering
einverne/dotfiles
Guide for implementing Cloudflare Browser Rendering - a headless browser automation API for screenshots, PDFs, web scraping, and testing.
121 GitHub stars~4.9k tokensUpdated 29 days ago
Productivity & AutomationAuto-check passed
Open Browser
JasonHonKL/Openbrowser
A skill your agent uses whenever the task involves browsing web pages, extracting page content, clicking forms, or completing web workflows.
114 GitHub stars~1.6k tokensUpdated 5 mo ago
Testing & QAAuto-check passed
Agent Browser
oxylabs/agent-skills
Connects to Oxylabs remote agent browsers over the Chrome DevTools Protocol (CDP) with Playwright or Puppeteer.
875 GitHub stars~3k tokensUpdated 8 days ago
Productivity & AutomationAuto-check passed
Agent
tinyfish-io/tinyfish-cookbook
Default browser automation agent — click, fill forms, navigate, log in, and extract structured data from any website using a natural-language goal, or run the same task across multiple sites in…
2.2k GitHub stars~1.1k tokensUpdated 7 days ago
Testing & QAAuto-check passed
Browser Automation
davila7/claude-code-templates
Browser automation powers web testing, scraping, and AI agent interactions.
32k GitHub starsUsed in 3 repos~569 tokens
Productivity & AutomationAuto-check passed
Brightdata Proxy
brightdata/skills
Generate working code that routes HTTP requests through Bright Data proxy networks (Datacenter, ISP, Residential, Mobile) and help users decide which network and IP pool type to use (shared pool…
264 GitHub stars~5.1k tokensUpdated yesterday
Testing & QAAuto-check passed

Questions about Browser Automation

What does Browser Automation do?

Non-testing browser automation - web scraping, form filling, screenshot capture, PDF generation, workflow automation. Browser Automation is an agent skill from ynulihao/AgentSkillOS. Non-testing browser automation - web scraping, form filling, screenshot capture, PDF generation, workflow automation.

When should I use Browser Automation?

Browser Automation fits situations like: tasks that involve Browser automation; tasks that involve Browser testing; tasks that involve Web scraping.

How do I install Browser Automation in Claude Code?

Run `npx skills add ynulihao/AgentSkillOS --skill browser-automation -a claude-code`. Or copy the skill folder (data/skill_seeds/browser-automation in ynulihao/AgentSkillOS) into .claude/skills/browser-automation in your project. Claude Code loads it when a task matches its description.

How do I install Browser Automation in Codex?

Run `npx skills add ynulihao/AgentSkillOS --skill browser-automation -a codex`. Or copy the skill folder (data/skill_seeds/browser-automation in ynulihao/AgentSkillOS) into .agents/skills/browser-automation in your project. Codex loads it when a task matches its description.

Can I use Browser Automation in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add ynulihao/AgentSkillOS --skill browser-automation -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/browser-automation, .gemini/skills/browser-automation, .github/skills/browser-automation and .opencode/skills/browser-automation in your project.

What does Browser Automation need to run?

SKILL.md names no scripts, command-line tools or credentials: Browser Automation is instructions for the agent only.

Does Browser Automation access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Browser Automation safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Browser Automation use?

No licence was found for Browser Automation or its repository. Without one, default copyright applies: ask the author before reusing or redistributing it.

How many tokens does Browser Automation use?

About 2.2k tokens (SKILL.md is roughly 8.8k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Browser Automation?

Skills that share tags, products or a category with Browser Automation: Cloudflare Browser Rendering (einverne/dotfiles, 121 stars), Open Browser (JasonHonKL/Openbrowser, 114 stars), Agent Browser (oxylabs/agent-skills, 875 stars) and Agent (tinyfish-io/tinyfish-cookbook, 2.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Browser Automation?

ynulihao (a GitHub user) maintains it in ynulihao/AgentSkillOS, which has 617 GitHub stars. The repository holds 26 skills in this directory. The repository was last updated on March 7, 2026.

Source: ynulihao/AgentSkillOS on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.

Browser Automation

Install Browser Automation

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Files

Compare with similar skills

Similar skills

Cloudflare Browser Rendering

Open Browser

Agent Browser

Agent