Web Browse
initializ/forge
Drive a headless browser to navigate pages, read content, click, and fill forms — for sites that need JavaScript rendering or interaction beyond a plain HTTP fetch.
A skill your agent uses when working with the browser tool — navigating or inspecting a page, clicking through a flow, filling and submitting a form, acting inside a logged-in session, or…
Install Browser Automation
$ npx skills add qualcomm/qai-appbuilder --skill browser-automation -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install qualcomm/qai-appbuilder browser-automation --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/qualcomm/qai-appbuilder.git skills-src && mkdir -p .claude/skills && cp -r skills-src/tools/qaiappbuilder/skills/browser-automation .claude/skills/browser-automation && rm -rf skills-srcUse ~/.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/
Install the "browser-automation" agent skill from https://github.com/qualcomm/qai-appbuilder/tree/main/tools/qaiappbuilder/skills/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 install https://github.com/qualcomm/qai-appbuilder/tree/main/tools/qaiappbuilder/skills/browser-automationType 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.
$ npx skills add qualcomm/qai-appbuilder --skill browser-automation -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install qualcomm/qai-appbuilder browser-automation --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qualcomm/qai-appbuilder.git skills-src && mkdir -p .agents/skills && cp -r skills-src/tools/qaiappbuilder/skills/browser-automation .agents/skills/browser-automation && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "browser-automation" agent skill from https://github.com/qualcomm/qai-appbuilder/tree/main/tools/qaiappbuilder/skills/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.
$ npx skills add qualcomm/qai-appbuilder --skill browser-automation -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install qualcomm/qai-appbuilder browser-automation --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qualcomm/qai-appbuilder.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/tools/qaiappbuilder/skills/browser-automation .cursor/skills/browser-automation && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "browser-automation" agent skill from https://github.com/qualcomm/qai-appbuilder/tree/main/tools/qaiappbuilder/skills/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 https://github.com/qualcomm/qai-appbuilder.git --path tools/qaiappbuilder/skills/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.
$ npx skills add qualcomm/qai-appbuilder --skill browser-automation -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install qualcomm/qai-appbuilder browser-automation --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qualcomm/qai-appbuilder.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/tools/qaiappbuilder/skills/browser-automation .gemini/skills/browser-automation && rm -rf skills-srcUse ~/.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/
Install the "browser-automation" agent skill from https://github.com/qualcomm/qai-appbuilder/tree/main/tools/qaiappbuilder/skills/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.
$ gh skill install qualcomm/qai-appbuilder browser-automationInstalls 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).
$ npx skills add qualcomm/qai-appbuilder --skill browser-automation -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/qualcomm/qai-appbuilder.git skills-src && mkdir -p .github/skills && cp -r skills-src/tools/qaiappbuilder/skills/browser-automation .github/skills/browser-automation && rm -rf skills-srcUse ~/.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/
Install the "browser-automation" agent skill from https://github.com/qualcomm/qai-appbuilder/tree/main/tools/qaiappbuilder/skills/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.
$ npx skills add qualcomm/qai-appbuilder --skill browser-automation -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install qualcomm/qai-appbuilder browser-automation --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/qualcomm/qai-appbuilder.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/tools/qaiappbuilder/skills/browser-automation .opencode/skills/browser-automation && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "browser-automation" agent skill from https://github.com/qualcomm/qai-appbuilder/tree/main/tools/qaiappbuilder/skills/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
- 247
- Token cost
- ~1.6k tokens
- SKILL.md length
- 470 words
- Files
- 1
- Skills in repo
- 13
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
A skill your agent uses when working with the browser tool — navigating or inspecting a page, clicking through a flow, filling and submitting a form, acting inside a logged-in session, or…
- Works in 3 steps: open — acquire a named tab and… → run — act on the tab, either → close — release a tab (all: true for…
- Working with the browser tool — navigating
- SKILL.md covers When to Use, The Three Actions, Selectors and How to Use, plus 3 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Browser Automation is an agent skill from qualcomm/qai-appbuilder. Use when working with the browser tool — navigating or inspecting a page, clicking through a flow, filling and submitting a form, acting inside a logged-in session, or screenshotting a rendered page — and especially when a page will not cooperate — a selector matches nothing, content is missing because it renders with JavaScript, an interaction has no effect, or a browser must be attached to instead of launched.
Its SKILL.md is about 1.6k 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. It works with JavaScript. The repository describes itself as: QAI AppBuilder is designed to help developers easily execute models on WoS and Linux platforms. It encapsulates the Qualcomm® AI Runtime SDK APIs into a set of simplified…
When your agent uses it
- Working with the browser tool — navigating
- Inspecting a page
- Clicking through a flow
- Filling and submitting a form
Example prompts
- “/browser-automation”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- open — acquire a named tab and optionally navigate.
- run — act on the tab, either
- close — release a tab (all: true for every tab). For a headless
What it can do on your machine
Read from SKILL.md and the folder at commit 7db8148. 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 Automation loads about 1.6k tokens when it runs. Until then it costs about 109 tokens; SKILL.md has 470 words of instructions outside code blocks.
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 470 words (~1,577 tokens).
“Companion reference for the browser tool. The tool does the acting (open a tab, run ops or page JavaScript, close); this skill covers the parts the tool signature cannot convey — which browser kind to use, how to pick selectors…”
- name
- browser-automation
- tags
- browser, browser-tool, web, automation, playwright, selectors, cdp
- use_for
- Companion reference for the `browser` tool — navigating and interacting with JavaScript-rendered pages, filling forms, clicking through flows, acting in a…
Files
Just SKILL.md in tools/qaiappbuilder/skills/browser-automation of qualcomm/qai-appbuilder.
Open the folder on GitHubat commit 7db8148
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Browser Automation this skillqualcomm/qai-appbuilder | 247 | — | ~1.6k | Automated safety check: Pass | Custom licence | |
| Web Browseinitializ/forge | 222 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 | |
| Chrome CDP Browser Controlzenstory-ai/oh-story-claudecode | 7.4k | 2 repos | ~1.2k | Automated safety check: Pass | MIT | |
| Control Browserzai-org/ZCode | 7.6k | — | ~4.6k | Automated safety check: Pass | Apache-2.0 | |
| Ego Browserkwakseongjae/oh-my-design | 531 | 1 repos | ~4.9k | Automated safety check: Pass | MIT | |
| Agent Browseroxylabs/agent-skills | 875 | — | ~3k | Automated safety check: Pass | MIT |
Similar skills
Chrome CDP Browser Control
zenstory-ai/oh-story-claudecode
Drives a Chrome window over the DevTools Protocol with the agent-browser CLI, so the agent can reuse your logged-in sessions, read pages and pull tokens.
Control Browser
zai-org/ZCode
A skill your agent uses when opening, navigating, inspecting, testing, clicking, typing, filling, screenshotting, or verifying web pages and local HTTP targets (localhost, 127.0.0.1, ::1) inside…
Ego Browser
kwakseongjae/oh-my-design
When you need a browser, read this Skill by default. An agent skill from kwakseongjae/oh-my-design.
Agent Browser
oxylabs/agent-skills
Connects to Oxylabs remote agent browsers over the Chrome DevTools Protocol (CDP) with Playwright or Puppeteer.
Browser Tools
981377660LMT/algorithm-study
Interactive browser automation via Chrome DevTools Protocol.
More from qualcomm/qai-appbuilder
All 13 skills in this repoModel Hub
qualcomm/qai-appbuilder
Model Hub — download pre-exported models from Qualcomm AI Hub, run inference on-device, and export them to App Builder as ready-to-import Packs.
Aipc Toolkit
qualcomm/qai-appbuilder
AIPC, AI Porting Conversion. An agent skill from qualcomm/qai-appbuilder.
Model Builder
qualcomm/qai-appbuilder
QAI ModelBuilder. An agent skill from qualcomm/qai-appbuilder.
App Builder
qualcomm/qai-appbuilder
App Builder — generate complete, runnable fullstack WebUI applications (FastAPI backend + pure HTML/CSS/JS frontend) around on-device AI Model Packs (OCR, TTS, ASR, Super-Resolution, etc.).
Ppt Gen
qualcomm/qai-appbuilder
Generate fully editable, high-quality PPTX with python-pptx based on the user's topic, materials, or business goals; defaults to a general-purpose "dark gilded elegant" visual system, with adaptive…
Read Arxiv Paper
qualcomm/qai-appbuilder
Fetch and summarize academic papers from arxiv.org. An agent skill from qualcomm/qai-appbuilder.
Related
Works with
Categories
Questions about Browser Automation
What does Browser Automation do?
A skill your agent uses when working with the browser tool — navigating or inspecting a page, clicking through a flow, filling and submitting a form, acting inside a logged-in session, or…. Browser Automation is an agent skill from qualcomm/qai-appbuilder. Use when working with the browser tool — navigating or inspecting a page, clicking through a flow, filling and submitting a form, acting inside a logged-in session, or screenshotting a rendered page — and especially when a page will not cooperate — a selector matches nothing, content is missing because it renders with JavaScript, an interaction has no effect, or a browser must be attached to instead of launched.
When should I use Browser Automation?
Browser Automation fits situations like: working with the browser tool — navigating; inspecting a page; clicking through a flow; filling and submitting a form.
How do I install Browser Automation in Claude Code?
Run `npx skills add qualcomm/qai-appbuilder --skill browser-automation -a claude-code`. Or copy the skill folder (tools/qaiappbuilder/skills/browser-automation in qualcomm/qai-appbuilder) 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 qualcomm/qai-appbuilder --skill browser-automation -a codex`. Or copy the skill folder (tools/qaiappbuilder/skills/browser-automation in qualcomm/qai-appbuilder) 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 qualcomm/qai-appbuilder --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?
Browser Automation 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 Browser Automation use?
About 1.6k tokens (SKILL.md is roughly 6.3k 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: Web Browse (initializ/forge, 222 stars), Chrome CDP Browser Control (zenstory-ai/oh-story-claudecode, 7.4k stars), Control Browser (zai-org/ZCode, 7.6k stars) and Ego Browser (kwakseongjae/oh-my-design, 531 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Browser Automation?
qualcomm (a GitHub organization) maintains it in qualcomm/qai-appbuilder, which has 247 GitHub stars. The repository holds 13 skills in this directory. The repository was last updated on October 9, 2026.
Source: qualcomm/qai-appbuilder on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.