Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →superset-sh/browser
Drive a workspace's in-app browser panes from the Superset CLI: list panes, open and navigate URLs, screenshot, read the console, evaluate JavaScript, and speak raw Chrome DevTools Protocol for click/type/scroll automation (browser-use / Playwright-class).
Passed 16 of 19 test cases with the skill, and 8 of 19 without it.
and 7 more in the full report
10 fixed9 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
I need to point an existing browser pane with identifier `pane-99` to `https://docs.example.org`. Which CLI subcommand and flags should I use?
| Checked | Without skill | With skill |
|---|---|---|
| Uses superset browser navigate with --pane pane-99 and --url https://docs.example.org | Missed | Passed |
The instructions your model reads when the skill loads.
Drive the browser panes inside a Superset workspace with the superset browser
commands. High-level verbs cover the common 90%; a raw Chrome DevTools Protocol
(CDP) endpoint covers full interaction (mouse, keyboard, scroll, DOM). Every
operation runs in the pane the user can see, against the browser's real,
logged-in session — treat it accordingly (see Safety).
superset browser --help and require list, open, navigate,
screenshot, eval, console, and cdp. If absent, run superset update
and recheck. Do not substitute unsupported commands. The app-bundled CLI
(~/.superset/bin/superset) updates only with the desktop app — if it lacks
browser, updating the app (not the CLI) is the fix; check type -a superset
for another install before giving up.$SUPERSET_WORKSPACE_ID;
otherwise superset workspaces list --local --json and pick the target.
Pass --host <id> for a remote host.superset start) has no panes and every command errors
clearly — surface that rather than retrying.When developing against a dev build of the desktop app in the Superset monorepo,
drive it with bun scripts/dev-cli.ts browser … (from the worktree) instead of
superset browser … — a plain dev CLI authenticates as your API org, not the
local-first dev host, so it finds no panes. See docs/agent-tooling.md.
Every pane has a stable paneId. Discover the panes already open in a
workspace:
superset browser list --workspace <id> --json
Open a URL and get the resulting paneId back. --target new-tab opens a
fresh tab and focuses it; the default current-tab reuses the active browser
pane. Opening requires the workspace to be visible in the desktop app (the
test cases passed, vs 8 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.