Loading skill
Install any skill in seconds. Free to start, no credit card required.
Get Started Free →tmchow/chrome-devtools-axi
This skill should be used when the user names chrome-devtools-axi, asks to "execute npx -y chrome-devtools-axi", wants Chrome DevTools Protocol browser automation through the AXI CLI, or needs token-efficient accessibility snapshots, stale-ref-safe clicks/fills, console/network inspection, screenshots, Lighthouse, or performance traces from a Chrome session.
Passed 16 of 19 test cases with the skill, and 10 of 19 without it.
and 5 more in the full report
7 fixed12 passed either way3 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
One of 7 test cases the skill fixed. Same model, same prompt, with and without the skill.
I opened a link in chrome-devtools-axi, but the snapshot shows elements from a different browser tab. What sequence of commands switches active focus to the target tab?
| Checked | Without skill | With skill |
|---|---|---|
| Uses pages subcommand to list active browser tabs. | Missed | Passed |
| Uses selectpage subcommand with the target tab identifier. | Missed | Passed |
The instructions your model reads when the skill loads.
Use this skill when the task specifically needs chrome-devtools-axi or a
Chrome DevTools Protocol browser controlled from the terminal:
chrome-devtools-axi, chrome-devtools-mcp, AXI browser automation, or asks to run npx -y chrome-devtools-axiDo not use it for ordinary web search, curl-able pages, static extraction,
or stealth/anti-detection work. Use Camofox/Camoufox only when cloaking is
load-bearing. Use built-in browser tools when the task is already solved there
and the user did not name chrome-devtools-axi.
chrome-devtools-axi is an npm CLI wrapper around chrome-devtools-mcp. The
first command starts a persistent local bridge, then later invocations reuse the
same Chrome/DevTools session. Output is AXI/TOON-style: page metadata,
accessibility snapshots, element refs, and next-step suggestions.
State lives under ~/.chrome-devtools-axi/, including the bridge PID and
snapshot-generation counter.
The skill only teaches the agent how to use the tool. The actual CLI is the npm
package chrome-devtools-axi; source repo:
https://github.com/kunchenguid/chrome-devtools-axi
Prefer npx for one-off use so the CLI is installed on demand:
npx -y chrome-devtools-axi --help
npx -y chrome-devtools-axi
test cases passed, vs 10 / 19 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.