Agent skill

Efficient Embedded Browser Loop

by holaboss-ai in holaboss-ai/holaOS

Guidelines for driving a workspace's embedded browser with the fewest tool calls, smallest state reads and no needless screenshots or waits.

Custom licenceAuto-check passedProductivity & Automation

Install Efficient Embedded Browser Loop

skills CLI
$ npx skills add holaboss-ai/holaOS --skill browser-core-efficient -a claude-code

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

GitHub CLI
$ gh skill install holaboss-ai/holaOS browser-core-efficient --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/holaboss-ai/holaOS.git skills-src && mkdir -p .claude/skills && cp -r skills-src/runtime/harnesses/src/embedded-skills/browser-core-efficient .claude/skills/browser-core-efficient && 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-core-efficient
GitHub stars
11k
Token cost
~736 tokens
SKILL.md length
377 words
Files
1
Skills in repo
30
Repo updated
First seen
Licence
Custom licence

At a glance

Guidelines for driving a workspace's embedded browser with the fewest tool calls, smallest state reads and no needless screenshots or waits.

  • Works in 5 steps: If the target is already known, use… → If the target is semantically known but… → Use browser_get_state only for… → …
  • Automating a task in the workspace's embedded browser with few tool calls
  • SKILL.md covers Goals, Default Loop, Tool Selection and State Discipline, plus 2 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

The default loop is to act directly when the target is known, using `browser_act` with locator signals such as text, label, role, selector or ref; to use `browser_find` when you know what you want on a large page but not where it is; and to call `browser_get_state` only for orientation. Index-based `browser_click` and `browser_type` are reserved for a stable index from a fresh state snapshot, and tab tools replace extra re-orienting calls.

State is kept small: compact detail by default, no page text unless reading content is the task, and no screenshots unless DOM signals fall short. When a fact may sit in custom-element attributes, `data-*` attributes, hrefs or hydration data, the agent inspects those before concluding it is unavailable, and treats refs as stale after a page change. For waiting, it prefers `wait_for` on the action itself, with `interactive` or `domcontentloaded` for light transitions, full load only when needed, and `download_started` and `download_completed` for downloads. Standard detail and page text are escalations, not defaults.

When your agent uses it

  • Automating a task in the workspace's embedded browser with few tool calls
  • Locating an element on a large page without dumping the whole state
  • Waiting for navigation or a download without polling

Example prompts

  • “Open the pricing page in the embedded browser and click the Enterprise plan button using as few calls as possible.”
  • “Find the search box on this long page and type the query without reading the full page text.”
  • “Start the report download and wait until it finishes.”

Requirements

  • The workspace's embedded browser tools, such as browser_act and browser_find

Workflow steps

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

  1. If the target is already known, use browser_act directly with locator signals.
  2. If the target is semantically known but the page is large, use browser_find.
  3. Use browser_get_state only for orientation or when the target is still unclear.
  4. After page-changing actions, use wait_for on the action itself when possible.
  5. Re-read state only if the action result is ambiguous.

What it can do on your machine

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

Efficient Embedded Browser Loop loads about 736 tokens when it runs. Until then it costs about 29 tokens; SKILL.md has 377 words of instructions outside code blocks.

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

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

Its licence (Custom licence) doesn't allow us to republish the file, so here is its outline and opening line. It has 377 words (~736 tokens).

“Use this skill when operating the workspace-embedded browser and efficiency matters.”

— opening of SKILL.md by holaboss-ai, Custom licence
name
browser-core-efficient

Read the full SKILL.md on GitHub

Files

Just SKILL.md in runtime/harnesses/src/embedded-skills/browser-core-efficient of holaboss-ai/holaOS.

Open the folder on GitHubat commit 4684714

Compare with similar skills

Efficient Embedded Browser Loop 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.

Efficient Embedded Browser Loop compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Efficient Embedded Browser Loop this skillholaboss-ai/holaOS11k—~736Automated safety check: PassCustom licence
Agent Browser CLIvercel-labs/agent-browser44k24 repos~864Automated safety check: PassApache-2.0
Agent Browserquran/quran.com-frontend-next1.9k41 repos~3.3kAutomated safety check: PassNone
Web Access via Browser CDPeze-is/web-access9.1k4 repos~2.2kAutomated safety check: PassMIT
Dev Browser AutomationMemTensor/MemOS12k3 repos~1.7kAutomated safety check: PassApache-2.0
Electron App Automationvercel-labs/agent-browser44k5 repos~1.7kAutomated safety check: PassApache-2.0

Similar skills

  • Agent Browser CLI

    vercel-labs/agent-browser

    Official

    Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking…

    44k GitHub starsUsed in 24 repos~864 tokens
    Productivity & AutomationAuto-check passed
  • Agent Browser

    quran/quran.com-frontend-next

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

    1.9k GitHub starsUsed in 41 repos~3.3k tokens
    Productivity & AutomationAuto-check passed
  • Routes every web task, from searching to logged-in browsing, through a tiered choice of search, fetch, curl or a real Chrome or Edge session driven over CDP.

    9.1k GitHub starsUsed in 4 repos~2.2k tokens
    Productivity & AutomationAuto-check passed
  • Dev Browser Automation

    MemTensor/MemOS

    Automates a real browser through short TypeScript scripts that keep page state between runs, for navigating, filling forms, taking screenshots and extracting data.

    12k GitHub starsUsed in 3 repos~1.7k tokens
    Productivity & AutomationAuto-check passed
  • Electron App Automation

    vercel-labs/agent-browser

    Official

    Automates Electron desktop apps such as VS Code, Slack or Discord by connecting agent-browser to their Chrome DevTools Protocol port.

    44k GitHub starsUsed in 5 repos~1.7k tokens
    Productivity & AutomationAuto-check passed
  • Slack Browser Automation

    vercel-labs/agent-browser

    Official

    Drives the Slack web app with the agent-browser CLI to check unread channels, search, read channel details and extract information, with screenshots as evidence.

    44k GitHub starsUsed in 1 repo~2.1k tokens
    Productivity & AutomationAuto-check passed

More from holaboss-ai/holaOS

All 30 skills in this repo
  • Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.

    11k GitHub starsUsed in 3 repos~6k tokens
    Auto-check passed
  • Edits an already-installed workspace capability's manifest to add an MCP server, a skill, an integration or agent guidance, then reinstalls it so the change takes effect on the next run.

    11k GitHub stars~815 tokensUpdated 1 mo ago
    Auto-check passed
  • Builds the visual layer of a holaOS dashboard app with TanStack Start and @holaboss/ui, starting from a bundled reference instead of a blank page.

    11k GitHub stars~6.3k tokensUpdated 1 mo ago
    Auto-check passed
  • Capability Creator

    holaboss-ai/holaOS

    Bundles one or more existing skills and the integrations they need into a single named, installable capability.

    11k GitHub stars~385 tokensUpdated 1 mo ago
    Auto-check passed
  • Browser QA Repro Loop

    holaboss-ai/holaOS

    Validates or debugs a workflow in the embedded browser with a reproducible, evidence-first loop that separates product failures from wait or locator problems.

    11k GitHub stars~712 tokensUpdated 1 mo ago
    Auto-check passed
  • holaOS MCP Configurator

    holaboss-ai/holaOS

    Adds, removes or updates MCP servers in a holaOS workspace by editing workspace.yaml in the mcp_registry format, with rules for headers, local servers and tool allowlists.

    11k GitHub stars~874 tokensUpdated 1 mo ago
    Auto-check passed

Questions about Efficient Embedded Browser Loop

What does Efficient Embedded Browser Loop do?

Guidelines for driving a workspace's embedded browser with the fewest tool calls, smallest state reads and no needless screenshots or waits. The default loop is to act directly when the target is known, using `browser_act` with locator signals such as text, label, role, selector or ref; to use `browser_find` when you know what you want on a large page but not where it is; and to call `browser_get_state` only for orientation. Index-based `browser_click` and `browser_type` are reserved for a stable index from a fresh state snapshot, and tab tools replace extra re-orienting calls.

When should I use Efficient Embedded Browser Loop?

Efficient Embedded Browser Loop fits situations like: automating a task in the workspace's embedded browser with few tool calls; locating an element on a large page without dumping the whole state; waiting for navigation or a download without polling.

How do I install Efficient Embedded Browser Loop in Claude Code?

Run `npx skills add holaboss-ai/holaOS --skill browser-core-efficient -a claude-code`. Or copy the skill folder (runtime/harnesses/src/embedded-skills/browser-core-efficient in holaboss-ai/holaOS) into .claude/skills/browser-core-efficient in your project. Claude Code loads it when a task matches its description.

How do I install Efficient Embedded Browser Loop in Codex?

Run `npx skills add holaboss-ai/holaOS --skill browser-core-efficient -a codex`. Or copy the skill folder (runtime/harnesses/src/embedded-skills/browser-core-efficient in holaboss-ai/holaOS) into .agents/skills/browser-core-efficient in your project. Codex loads it when a task matches its description.

Can I use Efficient Embedded Browser Loop 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 holaboss-ai/holaOS --skill browser-core-efficient -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-core-efficient, .gemini/skills/browser-core-efficient, .github/skills/browser-core-efficient and .opencode/skills/browser-core-efficient in your project.

What does Efficient Embedded Browser Loop need to run?

SKILL.md names no scripts, command-line tools or credentials: Efficient Embedded Browser Loop is instructions for the agent only. Our summary lists: The workspace's embedded browser tools, such as browser_act and browser_find.

Does Efficient Embedded Browser Loop 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 Efficient Embedded Browser Loop 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 Efficient Embedded Browser Loop use?

Efficient Embedded Browser Loop has a licence file (the repository's licence) that doesn't match a standard licence. Read it on GitHub before reusing the skill.

How many tokens does Efficient Embedded Browser Loop use?

About 736 tokens (SKILL.md is roughly 2.9k 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 Efficient Embedded Browser Loop?

Skills that share tags, products or a category with Efficient Embedded Browser Loop: Agent Browser CLI (vercel-labs/agent-browser, 44k stars), Agent Browser (quran/quran.com-frontend-next, 1.9k stars), Web Access via Browser CDP (eze-is/web-access, 9.1k stars) and Dev Browser Automation (MemTensor/MemOS, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Efficient Embedded Browser Loop?

holaboss-ai (a GitHub organization) maintains it in holaboss-ai/holaOS, which has 11,449 GitHub stars. The repository holds 30 skills in this directory. The repository was last updated on August 21, 2026.

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