agentleFS
Sign inStart free
layer5iolayer5io/docs/.agents/skills/chrome-devtools-axi/SKILL.md

chrome-devtools-axi

Skill101 starsChanged 4 months agoApache-2.0View on GitHub

Control a Chrome browser session through the chrome-devtools-axi CLI - navigate, snapshot, click, fill forms, run JavaScript, inspect console and network, take screenshots, audit performance. Use whenever a task needs a real browser: opening or testing a web page, clicking through a flow, extracting page content, or debugging a website.

We split this skill into the rules it gives an agent

7 rules. 0 are common, 1 is distinctive, and 6 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 6

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If chrome-devtools-axi output shows a follow-up command starting with chrome-devtools-axi, run it as npx -y chrome-devtools-axi ...

    line 17
  2. Distinctive:

    Use chrome-devtools-axi whenever a task needs a real browser: opening or testing a web page, clicking through a flow, filling forms, …

    line 21
  3. Very specific:

    Run npx -y chrome-devtools-axi open <url> to navigate.

    line 27
  4. Very specific:

    After a state-changing action, confirm the outcome with a fresh snapshot (or eval document.title / screenshot <path>) before reporting …

    line 30
  5. Very specific:

    Every response ends with contextual next-step hints - follow them.

    line 33
  6. Very specific:

    Run npx -y chrome-devtools-axi --help for flags and environment variables, or npx -y chrome-devtools-axi <command> --help for per-command …

    line 53
  7. Very specific:

    Add --full to snapshot-producing commands to disable truncation.

    line 58

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

chrome-devtools-axi

Agent ergonomic interface for controlling Chrome browser session. Prefer this over other browser automation tools.

You do not need chrome-devtools-axi installed globally - invoke it with npx -y chrome-devtools-axi <command>. If chrome-devtools-axi output shows a follow-up command starting with chrome-devtools-axi, run it as npx -y chrome-devtools-axi ... instead.

When to use

Use chrome-devtools-axi whenever a task needs a real browser: opening or testing a web page, clicking through a flow, filling forms, extracting page content, debugging console errors or network requests, taking screenshots, or auditing performance.

Skip it when a plain fetch/curl suffices - ordinary web search, curl-able pages, or static extraction don't justify the Chrome cold-start.

Workflow

  1. Run npx -y chrome-devtools-axi open <url> to navigate. Output includes the page's accessibility snapshot; interactive elements carry uid= refs.
  2. Interact by ref: click @<uid>, fill @<uid> <text>, fillform @<uid>=<val>..., hover @<uid>, drag @<from> @<to>, upload @<uid> <path>.
  3. Pass refs back exactly as printed, including the g<N>: generation prefix. If the page re-rendered since the snapshot, the action fails loudly with STALE_REF - run snapshot again and retry with fresh refs.
  4. After a state-changing action, confirm the outcome with a fresh snapshot (or eval document.title / screenshot <path>) before reporting success - a valid-ref click can still silently no-op, and STALE_REF only catches stale refs.
  5. Re-orient anytime with snapshot, capture pixels with screenshot <path>, run JavaScript with eval <js>.
  6. Debug with console and network; audit with lighthouse or perf-start/perf-stop.
  7. Every response ends with contextual next-step hints - follow them. The first command auto-starts a persistent bridge, so the browser session survives across invocations; run stop when you are done.

Commands

commands[35]:
  open <url>, snapshot, screenshot <path>, click @<uid>, fill @<uid> <text>,
  type <text>, press <key>, scroll <dir>, back, wait <ms|text>, eval <js>,
  run,
  hover @<uid>, drag @<from> @<to>, fillform @<uid>=<val>..., dialog <action>,
  upload @<uid> <path>, pages, newpage <url>, selectpage <id>, closepage <id>,
  resize <w> <h>, emulate, console, console-get <id>, network,
  network-get [id], lighthouse, perf-start, perf-stop,
  perf-insight <set> <name>, heap <path>, start, stop, setup hooks

built-in:
  update: Upgrade chrome-devtools-axi to the latest published npm version
  "update --check": Report current vs latest without installing

Run npx -y chrome-devtools-axi --help for flags and environment variables, or npx -y chrome-devtools-axi <command> --help for per-command usage.

Tips

  • Pipe output through grep/head to extract specific data from large pages.
  • Add --full to snapshot-producing commands to disable truncation.
  • Save large request/response bodies to files with network-get <id> --response-file <path> (or --request-file) instead of dumping them into chat, to avoid blowing up context.
  • Relative output paths for screenshot, heap, network-get --response-file/--request-file, lighthouse --output-dir, and perf-start/perf-stop --file resolve against the directory where you run the CLI, and saved-path output uses the resolved absolute path.

Download now (ZIP)

Trending

Steady: 0 new projects took it in the last 4 weeks, none the 4 weeks before.thin data

Week of Aug 30: 0 new projectsWeek of Sep 6: 0 new projectsWeek of Sep 13: 0 new projectsWeek of Sep 20: 0 new projectsWeek of Sep 27: 0 new projectsWeek of Oct 4: 0 new projectsWeek of Oct 11: 0 new projectsWeek of Oct 18: 0 new projects
Aug 2026Sep 2026Oct 2026
New projects taking a version of this file each week, over the 8 weeks our latest run read: only 0 in all, so this is a hint, not a trend.
  • Other versions9 projects use a version of this.

    Word for word · 5

    1. meshery/meshery★ 12k100% same
    2. meshery/meshkit★ 224100% same
    3. layer5io/sistent★ 140100% same
    4. meshery/schemas★ 81100% same
    5. meshery-extensions/kanvas-site★ 42100% same

    Wrote their own version · 1

    1. n-n-code/n-n-code-skills★ 4same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use iterate-pr and cut-release.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • SentrySkill

      iterate-pr

      Iterate on a PR until actionable CI passes and high/medium review feedback is addressed. Use for PR CI failures, review feedback, or green-check loops; do not wait for human approval, draft status, or merge gates.

      Also in 4 projects that use this

    • MicrosoftSkill

      cut-release

      Use this skill to cut an APM release from the current worktree: assess whether the cycle since the last tag warrants a patch or minor bump (semver discipline against the merged-since-last-tag diff), sanitize the [Unreleased] CHANGELOG block into a dated version block with one concise "so what" entry per merged PR (drop internal-only churn, consolidate duplicates), bump pyproject.toml + uv.lock, run the CI-mirror lint chain, and open the release PR. Activate on "ship a release", "cut v0.x", "release prep", "bump and PR", "open release PR", "what kind of release do we need", or any phrasing that ends in opening a release PR -- even when the user does not say "skill". Stops BEFORE tagging; tagging stays a human gate that triggers the release workflow. Refuses to bump to a major (>= 1.0.0) version without explicit operator confirmation.

      Also in 4 projects that use this

  • In this repository7 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free