New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Browser Control

by Porabuild in Porabuild/Poracode

Open, inspect, interact with, and verify websites or local web apps in Poracode's isolated browser.

Apache-2.0Auto-check: warningsProductivity & Automation

Install Browser Control

The automated check flagged lines worth reading first. See the safety section below.

skills CLI
$ npx skills add Porabuild/Poracode --skill browser-control -a claude-code

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

GitHub CLI
$ gh skill install Porabuild/Poracode browser-control --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/Porabuild/Poracode.git skills-src && mkdir -p .claude/skills && cp -r skills-src/resources/plugins/browser-tools/skills/browser-control .claude/skills/browser-control && 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/

Facts

Skill name
browser-control
GitHub stars
115
Token cost
~708 tokens
SKILL.md length
360 words
Files
1
Skills in repo
21
Repo updated
First seen
Licence
Apache-2.0

At a glance

Open, inspect, interact with, and verify websites or local web apps in Poracode's isolated browser.

  • Works in 7 steps: Call browser.api when you need the… → Reuse a relevant tab from… → Establish the baseline with the current… → …
  • Visible page state
  • SKILL.md covers Workflow, Boundaries and Output
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Browser Control is an agent skill from Porabuild/Poracode. Open, inspect, interact with, and verify websites or local web apps in Poracode's isolated browser. Use for visible page state, navigation, screenshots, console or network evidence, and end-to-end UI testing; do not use it for semantic service operations when a purpose-built connector is available.

Its SKILL.md is about 710 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. The repository describes itself as: One window for all your AI coding agents. Run Claude, Codex, OpenCode, Gemini, Antigravity, Cursor, and Copilot side-by-side. Terminal and chat, any layout. The licence is Apache-2.0.

When your agent uses it

  • Visible page state
  • Network evidence
  • End-to-end UI testing
  • Do not use it for semantic service operations when a purpose-built connector is available

Example prompts

  • “/browser-control”

Workflow steps

7 steps, taken from the first numbered list in SKILL.md.

  1. Call browser.api when you need the current API map, then call browser.enable once before the first browser action.
  2. Reuse a relevant tab from browser.list_tabs; otherwise open the exact URL the user supplied or the known local target. Do not guess a…
  3. Establish the baseline with the current URL plus browser.snapshot or browser.find. Prefer accessible roles, names, and returned element…
  4. Use perform for a bounded sequence of known actions: {steps:[{action:"fill",ref:"@e1",text:"Ada"},{action:"click",ref:"@e2"},{action:"wait"…
  5. Include a condition wait at the end of a batch for asynchronous changes, then inspect its returned observation. After navigation, wait for…
  6. Capture a screenshot when visual layout or appearance is part of the requirement.
  7. Call browser.disable before asking the user for input, waiting on an external event, or finishing.

What it can do on your machine

Read from SKILL.md and the folder at commit e56fcc8. 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.

    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 Control loads about 708 tokens when it runs. Until then it costs about 79 tokens; SKILL.md has 360 words of instructions outside code blocks.

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

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: warnings

The automated check found patterns that need a careful read before installing.

  • WarningMentions a credentials file (SSH keys, cloud or package-manager tokens)SKILL.md:22
    er is isolated from the user's personal Chrome profile. Do not assume it contains existing logins, cookies, or extension

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

The full file from Porabuild/Poracode at commit e56fcc8, republished under its Apache-2.0 licence (© Porabuild). 360 words, ~708 tokens.

Download SKILL.mdSave it as .claude/skills/browser-control/SKILL.md (or your agent's skills folder).
name
browser-control
description
Open, inspect, interact with, and verify websites or local web apps in Poracode's isolated browser. Use for visible page state, navigation, screenshots, console or network evidence, and end-to-end UI testing; do not use it for semantic service operations when a purpose-built connector is available.

Browser Control

Use Poracode's browser MCP when the task depends on a rendered page, visible interaction, or local web app. If the request is really about structured data or a service operation and a purpose-built connector is available, use that connector instead. An explicit request for Poracode's browser wins.

Workflow

  1. Call browser.api when you need the current API map, then call browser.enable once before the first browser action.
  2. Reuse a relevant tab from browser.list_tabs; otherwise open the exact URL the user supplied or the known local target. Do not guess a remote site or substitute web search when authentication blocks the requested page.
  3. Establish the baseline with the current URL plus browser.snapshot or browser.find. Prefer accessible roles, names, and returned element refs over brittle selectors or coordinates.
  4. Use perform for a bounded sequence of known actions: {steps:[{action:"fill",ref:"@e1",text:"Ada"},{action:"click",ref:"@e2"},{action:"wait",text:"Saved"}]}. It stops on failure and returns one final compact snapshot (observe:"none" omits it). Use fill for replacement and type for appending. Split batches at decisions, new targets, and navigation; do not replay completed steps after failure.
  5. Include a condition wait at the end of a batch for asynchronous changes, then inspect its returned observation. After navigation, wait for the expected URL, text, or element and inspect the resulting state. For web-app verification, also check relevant console errors and failed network requests.
  6. Capture a screenshot when visual layout or appearance is part of the requirement.
  7. Call browser.disable before asking the user for input, waiting on an external event, or finishing.
Show full SKILL.md (107 more words)Show less

Boundaries

  • The in-app browser is isolated from the user's personal Chrome profile. Do not assume it contains existing logins, cookies, or extensions.
  • Never inspect cookies or storage unless the task requires it and the user authorized that data access.
  • A successful click is not proof of success. Verify the user-visible or application state it was meant to produce.
  • Pause before purchases, submissions, messages, deletions, or other irreversible external actions unless the user explicitly authorized that exact action.

Output

Report the tested URL and flow, the final observed state, and the evidence used. Separate visual, console, and network findings, and state any step that could not be verified.

© Porabuild, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in resources/plugins/browser-tools/skills/browser-control of Porabuild/Poracode.

Open the folder on GitHubat commit e56fcc8

Compare with similar skills

Browser Control 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 Control compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Browser Control this skillPorabuild/Poracode115—~708Automated safety check: WarnApache-2.0
Agent Browserquran/quran.com-frontend-next1.9k40 repos~3.3kAutomated safety check: PassNone
Dev-Browser CLI AutomationSawyerHood/dev-browser6.7k1 repos~455Automated safety check: PassMIT
Browser Automationopenclaw/openclaw392k—~2.9kAutomated safety check: PassMIT
Camoufox CLIBin-Huang/camoufox-cli3501 repos~4.5kAutomated safety check: PassMIT
BrowserVibiumDev/vibium2.9k—~4.8kAutomated safety check: PassApache-2.0

Similar skills

  • Agent Browser

    quran/quran.com-frontend-next

    Automates browser interactions for web testing, form filling, screenshots, and data extraction.

    1.9k GitHub starsUsed in 40 repos~3.3k tokens
    Productivity & AutomationAuto-check passed

  • Dev-Browser CLI Automation

    SawyerHood/dev-browser

    Browser automation with persistent named pages via the dev-browser CLI. Use when users ask to navigate websites, fill forms, take screenshots, extract web…

    6.7k GitHub starsUsed in 1 repo~455 tokens
    Productivity & AutomationAuto-check passed

  • Browser Automation

    openclaw/openclaw

    A skill your agent uses when controlling web pages with the OpenClaw browser tool, especially multi-step flows, login checks, tab management, or recovery from stale refs/timeouts.

    392k GitHub stars~2.9k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Camoufox CLI

    Bin-Huang/camoufox-cli

    Anti-detect browser automation CLI & Skills for AI agents. An agent skill from Bin-Huang/camoufox-cli.

    350 GitHub starsUsed in 1 repo~4.5k tokens
    Productivity & AutomationAuto-check passed

  • Browser

    VibiumDev/vibium

    Automate browsers with the Vibium CLI. An agent skill from VibiumDev/vibium.

    2.9k GitHub stars~4.8k tokensUpdated today
    Productivity & AutomationAuto-check passed

  • Use Agent Browser For Airi

    moeru-ai/airi

    Test AIRI display-model imports with agent-browser across stage-tamagotchi Electron, stage-web, and stage-pocket mobile web layouts.

    50k GitHub stars~1.1k tokensUpdated today
    Productivity & AutomationAuto-check passed

More from Porabuild/Poracode

All 21 skills in this repo

  • Interactive Testing

    Porabuild/Poracode

    Run repeatable integration and smoke testing against the real Poracode Electron app through Chrome DevTools Protocol.

    115 GitHub stars~4.5k tokensUpdated today
    Auto-check: notes

  • Release Notes

    Porabuild/Poracode

    Write consistent, hand-written-looking changelog entries for a Poracode release.

    115 GitHub stars~4.2k tokensUpdated today
    Auto-check passed

  • Skill Creator Poracode

    Porabuild/Poracode

    Create a new reusable agent skill managed by Poracode. An agent skill from Porabuild/Poracode.

    115 GitHub stars~1.2k tokensUpdated today
    Auto-check passed

  • App Controls

    Porabuild/Poracode

    Inspect and drive Poracode itself — the Terminal panel, other threads, projects, workspaces, git, pull requests, and schedules — through the poracode MCP.

    115 GitHub stars~745 tokensUpdated today
    Auto-check passed

  • Chrome Control

    Porabuild/Poracode

    Use the user's real Chrome tabs and signed-in sessions for visible browser workflows.

    115 GitHub stars~691 tokensUpdated today
    Auto-check passed

  • Computer Use

    Porabuild/Poracode

    Inspect and operate native Windows, macOS, or Linux applications through Poracode's desktop-control tools.

    115 GitHub stars~718 tokensUpdated today
    Auto-check passed

Categories

Questions about Browser Control

What does Browser Control do?

Open, inspect, interact with, and verify websites or local web apps in Poracode's isolated browser. Browser Control is an agent skill from Porabuild/Poracode. Open, inspect, interact with, and verify websites or local web apps in Poracode's isolated browser.

When should I use Browser Control?

Browser Control fits situations like: visible page state; network evidence; end-to-end UI testing; do not use it for semantic service operations when a purpose-built connector is available.

How do I install Browser Control in Claude Code?

Run `npx skills add Porabuild/Poracode --skill browser-control -a claude-code`. Or copy the skill folder (resources/plugins/browser-tools/skills/browser-control in Porabuild/Poracode) into .claude/skills/browser-control in your project. Claude Code loads it when a task matches its description.

How do I install Browser Control in Codex?

Run `npx skills add Porabuild/Poracode --skill browser-control -a codex`. Or copy the skill folder (resources/plugins/browser-tools/skills/browser-control in Porabuild/Poracode) into .agents/skills/browser-control in your project. Codex loads it when a task matches its description.

Can I use Browser Control 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 Porabuild/Poracode --skill browser-control -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-control, .gemini/skills/browser-control, .github/skills/browser-control and .opencode/skills/browser-control in your project.

What does Browser Control need to run?

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

Does Browser Control 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 Control safe to install?

Our automated static check of SKILL.md flagged 1 warning(s): mentions a credentials file (ssh keys, cloud or package-manager tokens). Read the flagged lines before installing; the check is not a guarantee either way.

What licence does Browser Control use?

Browser Control is published under the Apache-2.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Browser Control use?

About 708 tokens (SKILL.md is roughly 2.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 Control?

Skills that share tags, products or a category with Browser Control: Agent Browser (quran/quran.com-frontend-next, 1.9k stars), Dev-Browser CLI Automation (SawyerHood/dev-browser, 6.7k stars), Browser Automation (openclaw/openclaw, 392k stars) and Camoufox CLI (Bin-Huang/camoufox-cli, 350 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Browser Control?

Porabuild (a GitHub organization) maintains it in Porabuild/Poracode, which has 115 GitHub stars. The repository holds 21 skills in this directory. The repository was last updated on October 9, 2026.

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