AI Search Hub
minsight-ai-info/AI-Search-Hub
Run the AI Search Hub browser automation scripts for Yuanbao, LongCat, Doubao, Qwen, Gemini, Grok, and MiniMax.
Opens pages, takes screenshots, reads the console, clicks and types in the browser panes of a Superset workspace, with Browser Use as a fallback for other browsers.
Install Superset Browser Control
$ npx skills add superset-sh/superset --skill browser -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install superset-sh/superset browser --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/superset-sh/superset.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/superset/skills/browser .claude/skills/browser && 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" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/browser into .claude/skills/browser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser", 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/superset-sh/superset/tree/main/plugins/superset/skills/browserType 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 superset-sh/superset --skill browser -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install superset-sh/superset browser --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superset-sh/superset.git skills-src && mkdir -p .agents/skills && cp -r skills-src/plugins/superset/skills/browser .agents/skills/browser && 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" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/browser into .agents/skills/browser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser", 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 superset-sh/superset --skill browser -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install superset-sh/superset browser --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superset-sh/superset.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/plugins/superset/skills/browser .cursor/skills/browser && 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" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/browser into .cursor/skills/browser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser", 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/superset-sh/superset.git --path plugins/superset/skills/browser--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 superset-sh/superset --skill browser -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install superset-sh/superset browser --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superset-sh/superset.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/plugins/superset/skills/browser .gemini/skills/browser && 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" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/browser into .gemini/skills/browser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser", 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 superset-sh/superset browserInstalls 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 superset-sh/superset --skill browser -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/superset-sh/superset.git skills-src && mkdir -p .github/skills && cp -r skills-src/plugins/superset/skills/browser .github/skills/browser && 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" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/browser into .github/skills/browser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser", 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 superset-sh/superset --skill browser -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install superset-sh/superset browser --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/superset-sh/superset.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/plugins/superset/skills/browser .opencode/skills/browser && 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" agent skill from https://github.com/superset-sh/superset/tree/main/plugins/superset/skills/browser into .opencode/skills/browser/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "browser", 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- GitHub stars
- 15k
- Token cost
- ~2.9k tokens
- SKILL.md length
- 1,320 words
- Files
- 3 (incl. references)
- Skills in repo
- 47
- Repo updated
- First seen
- Licence
- Custom licence
At a glance
Opens pages, takes screenshots, reads the console, clicks and types in the browser panes of a Superset workspace, with Browser Use as a fallback for other browsers.
- Works in 3 steps: Run superset browser --help and require… → Resolve the workspace. Inside a… → Panes live in the desktop app. A host…
- Previewing a running local web app and checking how it looks
- SKILL.md covers Choose a surface, Establish the control surface, Find or open a pane and Drive with the high-level verbs, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Pages are driven through `superset browser` commands in the pane you can see, using that pane's real logged-in session, with a raw Chrome DevTools Protocol endpoint for anything the high-level commands do not cover. The agent first decides on a surface: plain `curl` or fetch for public pages and JSON, and the in-app pane for previewing a dev server or checking a flow you are watching.
Browser Use is kept for targets the panes cannot reach, such as a Chrome window outside Superset, a host without the desktop app or an isolated or cloud browser, and for open-ended or long multi-step flows after you agree to it. Setup checks that `superset browser --help` lists the needed commands, updates the CLI if not, and resolves the workspace from the environment or `superset workspaces list`. `references/browser-use.md` covers install consent, attaching and cleanup.
When your agent uses it
- Previewing a running local web app and checking how it looks
- Reading the browser console of a page under test
- Filling in a form or clicking through a web flow in your signed-in session
- Driving a browser the Superset panes cannot reach
Example prompts
- “Open localhost:3000 in a browser pane and take a screenshot.”
- “Show me the console output on the checkout page after I click the submit button.”
- “Click through the signup flow and tell me where it breaks.”
Requirements
- The Superset desktop app and its `superset` CLI with the browser commands
- `curl`
- Pre-approved tools (allowed-tools): Bash(superset:*), Bash(curl:*)
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Run superset browser --help and require list, open, navigate,
- Resolve the workspace. Inside a workspace, use $SUPERSET_WORKSPACE_ID;
- Panes live in the desktop app. A host with no desktop attached (a standalone
What it can do on your machine
Read from SKILL.md and the folder at commit 4ec5b6e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves these tools, so the agent can use them without asking each time:
Bash(superset:*)Bash(curl:*)
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 bash and javascript).
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
Superset Browser Control loads about 2.9k tokens when it runs, and up to ~4.2k if it reads all its reference files. Until then it costs about 122 tokens; SKILL.md has 1,320 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 1,320 words (~2,853 tokens).
“Drive web pages through the browser panes inside a Superset workspace with the superset browser commands. Every operation runs in the pane the user can see, against the pane's real, logged-in session. A raw Chrome DevTools Protocol (CDP) endpoint covers…”
- name
- browser
- allowed-tools
- Bash(superset:*), Bash(curl:*)
- argument-hint
- URL or what to do in the browser
Files
SKILL.md and 2 other files (references) in plugins/superset/skills/browser of superset-sh/superset.
- SKILL.md
- agents/openai.yaml
- references/browser-use.md
Open the folder on GitHubat commit 4ec5b6e
Compare with similar skills
Superset 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Superset Browser Control this skillsuperset-sh/superset | 15k | — | ~2.9k | Automated safety check: Pass | Custom licence | |
| AI Search Hubminsight-ai-info/AI-Search-Hub | 1.3k | — | ~1.3k | Automated safety check: Pass | None | |
| Browser Tools981377660LMT/algorithm-study | 277 | 1 repos | ~1.3k | Automated safety check: Pass | None | |
| Agent Browser Automationwithkynam/vibecode-pro-max-kit | 1.1k | — | ~2.6k | Automated safety check: Pass | Apache-2.0 | |
| Electron Devtools Testingankitvgupta/exo | 495 | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Discover UI SurfaceZhixiangLuo/10xProductivity | 479 | — | ~296 | Automated safety check: Pass | MIT |
Similar skills
Browser Tools
981377660LMT/algorithm-study
Interactive browser automation via Chrome DevTools Protocol.
Agent Browser Automation
withkynam/vibecode-pro-max-kit
Drives a browser through the agent-browser CLI, using compact snapshots with element refs to keep context small in long sessions, plus video recording and cloud browsers.
Electron Devtools Testing
ankitvgupta/exo
Test the Electron app interactively using Chrome DevTools Protocol.
Discover UI Surface
ZhixiangLuo/10xProductivity
Walk through a UI flow once manually and capture a durable interaction map — which DOM elements to click, which network requests they trigger, and what field shapes they expose.
Cdp Connect
adobe/skills
Connect Claude Code to an existing Chrome browser via CDP (Chrome DevTools Protocol).
More from superset-sh/superset
All 47 skills in this repoMobile Demo Film Editor
superset-sh/superset
Edits real mobile screen recordings into a configurable demo video with phone framing, title cards, cutaways and an end card, using a bundled renderer.
Superset Agent Standup
superset-sh/superset
Sweeps every Superset workspace, task and agent terminal to report what finished, what needs review and what is blocked, read-only, and can publish the digest as a page.
Superset Automate
superset-sh/superset
Turns a recurring chore into a scheduled or event-triggered Superset agent, drafting its prompt, picking a target and trigger, and reviewing the first run.
Drizzle Migration Safety on Neon
superset-sh/superset
Generates a Drizzle migration on a fresh Neon branch and runs a production-safety checklist for table sizes, lock order and load rehearsal before the PR opens.
Superset Feedback Reporter
superset-sh/superset
Turns a bug report or feature request about Superset into a short, scannable write-up and submits it privately or as a public GitHub issue.
Superset Incident Triage
superset-sh/superset
Does a read-only first pass on a possible production incident: gathers deploy, Sentry and health-check signals, proposes a severity and status message, then stops for human approval.
Related
Works with
Categories
Questions about Superset Browser Control
What does Superset Browser Control do?
Opens pages, takes screenshots, reads the console, clicks and types in the browser panes of a Superset workspace, with Browser Use as a fallback for other browsers. Pages are driven through `superset browser` commands in the pane you can see, using that pane's real logged-in session, with a raw Chrome DevTools Protocol endpoint for anything the high-level commands do not cover. The agent first decides on a surface: plain `curl` or fetch for public pages and JSON, and the in-app pane for previewing a dev server or checking a flow you are watching.
When should I use Superset Browser Control?
Superset Browser Control fits situations like: previewing a running local web app and checking how it looks; reading the browser console of a page under test; filling in a form or clicking through a web flow in your signed-in session; driving a browser the Superset panes cannot reach.
How do I install Superset Browser Control in Claude Code?
Run `npx skills add superset-sh/superset --skill browser -a claude-code`. Or copy the skill folder (plugins/superset/skills/browser in superset-sh/superset) into .claude/skills/browser in your project. Claude Code loads it when a task matches its description.
How do I install Superset Browser Control in Codex?
Run `npx skills add superset-sh/superset --skill browser -a codex`. Or copy the skill folder (plugins/superset/skills/browser in superset-sh/superset) into .agents/skills/browser in your project. Codex loads it when a task matches its description.
Can I use Superset 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 superset-sh/superset --skill browser -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, .gemini/skills/browser, .github/skills/browser and .opencode/skills/browser in your project.
What does Superset Browser Control need to run?
SKILL.md names no scripts, command-line tools or credentials: Superset Browser Control is instructions for the agent only. Our summary lists: The Superset desktop app and its `superset` CLI with the browser commands; `curl`. Its frontmatter pre-approves these tools: Bash(superset:*), Bash(curl:*).
Does Superset 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 Superset Browser Control 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 Superset Browser Control use?
Superset Browser Control 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 Superset Browser Control use?
About 2.9k tokens (SKILL.md is roughly 11k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 1.3k tokens, read only when the agent opens those files.
What are the alternatives to Superset Browser Control?
Skills that share tags, products or a category with Superset Browser Control: AI Search Hub (minsight-ai-info/AI-Search-Hub, 1.3k stars), Browser Tools (981377660LMT/algorithm-study, 277 stars), Agent Browser Automation (withkynam/vibecode-pro-max-kit, 1.1k stars) and Electron Devtools Testing (ankitvgupta/exo, 495 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Superset Browser Control?
superset-sh (a GitHub organization) maintains it in superset-sh/superset, which has 15,042 GitHub stars. The repository holds 47 skills in this directory. The repository was last updated on October 10, 2026.
Source: superset-sh/superset on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.