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:
Quick answer
Faster Chrome DevTools — direct-CDP browser control CLI, local Chrome or Cloudflare Browser Run (short listing) is a free Muse skill that controls Chrome through the Chrome DevTools Protocol with a CLI, listing tabs, snapshots, navigating, clicking, filling, typing, evaluating JavaScript, and reading console and network output. Own accounts and systems only, never third parties, license not verifiable, short listing.
Install
Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 11, 2026📌 Pinned version: commit a04384eStep 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. 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://raw.githubusercontent.com/zeke/faster-chrome-devtools-skill/a04384e63e80b730589c35579e166081d911c462/skills/faster-chrome-devtools-skill/SKILL.md Pinned version: install the code at commit a04384e63e80b730589c35579e166081d911c462 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder 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.
Saved to your recent installs. Find it anytime on /connect.
🔒 Security, provenance and what this touches
- It works with an API key or a token that you provide.
What the scan found — excerpts from the install prompt
- uses API keys or tokens — Prerequisites: Node.js 22+; for local use a Chrome/Chromium with remote debugging enabled (or a throwaway anon
The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?
Verification certificate
Dated facts about what was checked for this listing, and how. This is not a safety certification.
- Pinned version
- a04384e · 2026-10-13
- Sandbox install test
- Install ran in our test sandbox · Nov 11, 2026
- Creator identity
- Not verified
- Fingerprint watch
- Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
- Install prompt analysis
- 2026-10-13 : uses API keys or tokens
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Questions
How do I install a skill?
Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill 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 skill before installing it.