chromium-debug-use
Attach to a user's already-open Chromium-family browser for live inspection and light interaction after explicit local approval
Best use case
chromium-debug-use is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Attach to a user's already-open Chromium-family browser for live inspection and light interaction after explicit local approval
Teams using chromium-debug-use should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/chromium-debug-use/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How chromium-debug-use Compares
| Feature / Agent | chromium-debug-use | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
Attach to a user's already-open Chromium-family browser for live inspection and light interaction after explicit local approval
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
Related Guides
AI Agents for Coding
Browse AI agent skills for coding, debugging, testing, refactoring, code review, and developer workflows across Claude, Cursor, and Codex.
Cursor vs Codex for AI Workflows
Compare Cursor and Codex for AI coding workflows, repository assistance, debugging, refactoring, and reusable developer skills.
SKILL.md Source
<!-- SPDX-License-Identifier: MIT --> <!-- SPDX-FileCopyrightText: 2025-2026 Marcus Quinn --> # Chromium Debug Use Read `tools/browser/chromium-debug-use.md` first. ## Use This Skill When The user wants to inspect or lightly interact with something already open in a Chromium-family browser (Chrome, Brave, Edge, Vivaldi, Chromium) before committing to a heavier automation tool. ## Workflow 1. Confirm explicit, user-approved live-session investigation. 2. If the debug port is not yet open, have the user launch with the flag from `tools/browser/chromium-debug-use.md`. 3. Use `.agents/scripts/chromium-debug-use-helper.sh version` and `list` to confirm access. 4. Prefer `snapshot`, `html`, and `eval` to understand the page before using `click`, `type`, `navigate`, or `screenshot`. 5. Once the flow is understood, hand off to the best-fit longer-term tool: - `tools/browser/playwright.md` — repeatable isolated automation - `tools/browser/dev-browser.md` — aidevops-managed persistent profile - `tools/browser/playwriter.md` — per-tab extension consent in the user's normal browser - `tools/browser/chrome-devtools.md` — performance, network, and console inspection ## Safety - Local-only and temporary; the user must have enabled the debug path for this investigation. - Prefer loopback endpoints and temporary profiles. - Do not use this path for unrelated tabs or long-lived background control. ## Commands ```bash .agents/scripts/chromium-debug-use-helper.sh version .agents/scripts/chromium-debug-use-helper.sh list .agents/scripts/chromium-debug-use-helper.sh snapshot <target> .agents/scripts/chromium-debug-use-helper.sh html <target> [selector] .agents/scripts/chromium-debug-use-helper.sh eval <target> "document.title" .agents/scripts/chromium-debug-use-helper.sh click <target> "button.submit" .agents/scripts/chromium-debug-use-helper.sh type <target> "hello world" .agents/scripts/chromium-debug-use-helper.sh screenshot <target> /tmp/page.png ``` Use `--browser-url http://127.0.0.1:9222` when the session is not on the default endpoint.
Related Skills
debugging-streamlit
Debug Streamlit frontend and backend changes using make debug with hot-reload. Use when testing code changes, investigating bugs, checking UI behavior, or needing screenshots of the running app.
ios-debugger-agent
Debug the current iOS project on a booted simulator with XcodeBuildMCP.
error-diagnostics-smart-debug
Use when working with error diagnostics smart debug
error-debugging-multi-agent-review
Use when working with error debugging multi agent review
error-debugging-error-trace
You are an error tracking and observability expert specializing in implementing comprehensive error monitoring solutions. Set up error tracking systems, configure alerts, implement structured logging, and ensure teams can quickly identify and resolve production issues.
error-debugging-error-analysis
You are an expert error analysis specialist with deep expertise in debugging distributed systems, analyzing production incidents, and implementing comprehensive observability solutions.
distributed-debugging-debug-trace
You are a debugging expert specializing in setting up comprehensive debugging environments, distributed tracing, and diagnostic tools. Configure debugging workflows, implement tracing solutions, and establish troubleshooting practices for development and production environments.
debugging-toolkit-smart-debug
Use when working with debugging toolkit smart debug
debugging-strategies
Transform debugging from frustrating guesswork into systematic problem-solving with proven strategies, powerful tools, and methodical approaches.
debugger
Debugging specialist for errors, test failures, and unexpected behavior. Use proactively when encountering any issues.
debug-buttercup
All pods run in namespace crs. Use when pods in the crs namespace are in CrashLoopBackOff, OOMKilled, or restarting, multiple services restart simultaneously (cascade failure), or redis is unresponsive or showing AOF warnings.
debug-nw
Debug a Nativewind v5 setup issue. Walks through common configuration problems with metro, babel, postcss, and dependencies.