agentleFS
Sign inStart free
vrevre/flow-state/chrome-control/SKILL.md

chrome-control

Skill11 starsChanged 10 months agoMITView on GitHub

Use when debugging web applications, diagnosing page errors, inspecting console output, or capturing screenshots via Chrome DevTools Protocol (CDP).

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. alexjmiller5/agent-config-public★ 0same 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.

  • In this repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

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

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

    If connection fails → tell user to check remote debugging is enabled, or offer legacy mode (launch).

    line 19
  2. Very specific:

    Use --json for machine-parseable JSON output (default is human-readable).

    line 33
  3. Very specific:

    All target commands: chromectl.py TARGET COMMAND [ARGS]

    line 37
  4. Very specific:

    Wait commands: --timeout N (default 10s)

    line 69

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “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 Control

Control Chrome via CDP. Connects to user's running Chrome — all tabs, cookies, logins accessible.

Prerequisites

User must enable chrome://inspect/#remote-debugging in Chrome.

The daemon starts automatically on first command. No explicit start needed. User clicks Allow once on the Chrome permission dialog.

Chrome pops a permission dialog on every new WebSocket connection. The daemon holds that single connection open so the user clicks Allow once and all subsequent CLI calls go through without prompts. Each command is a one-shot call; the caller does not hold any connection. The daemon idles out after 5 min of no commands. Unix socket: /tmp/chromectl-{uid}.sock.

If connection fails → tell user to check remote debugging is enabled, or offer legacy mode (launch).

Tool responses are sanitized: prompt-injection markers in page content are stripped before reaching the LLM.

Commands

chromectl.py list
chromectl.py open https://example.com
chromectl.py status
chromectl.py targets
chromectl.py stop

Use --json for machine-parseable JSON output (default is human-readable).

Target commands

All target commands: chromectl.py TARGET COMMAND [ARGS]

Target ID from list/open output. Prefix match OK (e.g. 88FA instead of full 32-char ID).

chromectl.py ABC123 eval "document.title"
chromectl.py ABC123 screenshot -o page.png [--full-page]
chromectl.py ABC123 console-tail [--for 30]
chromectl.py ABC123 navigate https://example.com

DOM helpers

Shorthands for common eval patterns. Selectors are CSS.

  click/check/uncheck/highlight SELECTOR
  submit/clear FORM
  type/fill SELECTOR TEXT
  select SELECTOR VALUE
  get-text/get-html/get-value/exists/count/get-texts SELECTOR
  get-attr SELECTOR ATTR
  scroll-to/wait-for/wait-hidden SELECTOR
  wait-text SELECTOR TEXT
  navigate URL
  wait-url PATTERN
  scroll-up/scroll-down [PIXELS]
  scroll-by X Y
  inject-css CSS
  reload/back/forward/get-title/get-url/scroll-top/scroll-bottom

Wait commands: --timeout N (default 10s)

For anything not covered: chromectl.py ABC123 eval "JS expression"

Top-level await: chromectl.py ABC123 eval "await fetch('/api').then(r => r.json())"

Raw CDP

chromectl.py cdp Browser.getVersion
chromectl.py cdp Target.getTargets

Legacy mode

For clean browser without existing sessions: chromectl.py launch [--headless]

Resources

  • chromectl-reference.md — all options, socket protocol, troubleshooting

Download now (ZIP)

Does it work?

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

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

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