Faster Chrome DevTools — direct-CDP browser control CLI, local Chrome or Cloudflare Browser Run (short listing)
⚠️ AUTHORIZED USE ONLY — short listing — license not verifiable; inspect, debug, and automate Chrome directly through the Chrome DevTools Protocol with a dependency-free Node.js CLI — local tabs, remote Cloudflare endpoints, human-in-the-loop handoffs
- What
- ⚠️ AUTHORIZED USE ONLY — short listing — license not verifiable; inspect, debug, and automate Chrome directly through the Chrome DevTools Protocol with a dependency-free Node.js CLI — local tabs, remote Cloudflare endpoints, human-in-the-loop handoffs
- Cost
- Free
- Needs
- Node.js 22+; for local use a Chrome/Chromium with remote debugging enabled (or a throwaway anonymous profile); for remote use a Cloudflare account with Browser Rendering access (billed service) — account ID and API token via environment variables, never hardcoded — ⚠️ AUTHORIZED USE ONLY: full control of a LIVE browser with your logged-in sessions; use only on your own accounts and systems
- Install
- Copy the installer prompt below into your Muse — your agent does the rest.
Selected by Skill Harbor — ⚠️ AUTHORIZED USE ONLY: this CLI gives your agent full control of a LIVE browser — open tabs and logged-in sessions are visible and actionable, so use it only for your own accounts and systems, never against third parties or accounts you do not own. Short listing (the discovery manifest records no license for this skill — the manifest makes faith, so no content is reproduced beyond this summary; the repo frontmatter carries no license field, only a Node 22+ compatibility note): @zeke's faster-chrome-devtools-skill — a dependency-free Node.js CLI (scripts/cdp.mjs) that controls Chrome directly through the Chrome DevTools Protocol, no MCP server, Puppeteer, or Playwright required. It lists tabs, takes accessibility snapshots (preferred over screenshots for speed and context), screenshots, navigates, clicks/fills/types with stable refs or CSS selectors, evaluates JS, reads console output and failed network requests, and works against the user's local Chrome or a remote Cloudflare Browser Rendering endpoint — with anonymous-profile guidance for clean sessions, a 20-minute connection daemon, human-in-the-loop handoffs (live-view URL + Done/Failed flow) for MFA/SSO/CAPTCHA/sensitive input, WebMCP beta feature support, and optional MCP compatibility. Honest caveats: license terms not verifiable — short listing with a link only; connects the agent to your LIVE browser with its logged-in state — grant access deliberately; remote Cloudflare use needs account ID + API token (a billed service) kept in environment variables, never in shell history; Node 22+ required. Skill Harbor never reviews the code, review it yourself before use. Discovered via skills.sh.
Version:
Install
Prerequisites: Node.js 22+; for local use a Chrome/Chromium with remote debugging enabled (or a throwaway anonymous profile); for remote use a Cloudflare account with Browser Rendering access (billed service) — account ID and API token via environment variables, never hardcoded — ⚠️ AUTHORIZED USE ONLY: full control of a LIVE browser with your logged-in sessions; use only on your own accounts and systems Install "Faster Chrome DevTools — direct-CDP browser control CLI, local Chrome or Cloudflare Browser Run (short listing)" for me. It gives my agent @zeke's direct-CDP browser control CLI: list tabs, snapshot the accessibility tree (preferred over screenshots), screenshot, navigate with realistic timeouts, click/fill/type with stable refs or CSS selectors, evaluate JavaScript, read console output and failed network requests, use anonymous Chrome profiles for clean sessions, hand off to a human (live-view + Done/Failed) for MFA/SSO/CAPTCHA/sensitive input on Browser Run, and keep tokens in environment variables. IMPORTANT: the license terms were not verifiable (the discovery manifest records no license; the repo frontmatter carries no license field) — fetch from the link only, reproduce nothing beyond the link, and read the license terms yourself before reuse. Repository: https://github.com/zeke/faster-chrome-devtools-skill/blob/main/skills/faster-chrome-devtools-skill/SKILL.md 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "faster-chrome-devtools-skill". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. read the license terms before reuse, enable Chrome remote debugging or spin up the anonymous profile, set Cloudflare env vars if using Browser Run, decide whether to grant access to my live browser session). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.
Questions
How do I install a build?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the build up for you — no manual configuration.
Where does my money go?
Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.
What does the ✓ next to a creator’s name mean?
It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a build before installing it.