AI Agent Hub
Back to skills
Chrome CDP Runtime icon

Chrome CDP Runtime

Development Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

To install this skill into your AI assistant, follow https://skillhub.cn/install/skillhub.md and install @user_2a19425c/chrome-cdp-runtime.

About this skill

Problem

Browser automation often stalls on environment checks: whether 9222 is listening, whether an existing Chrome instance can be reused, or whether a confirmed Chrome executable path is available. Guessing other browsers can introduce inconsistent behavior. This skill keeps the setup path explicit and predictable.

How It Works

  • Checks whether 9222 is accessible first.
  • Attaches to an existing Chrome CDP instance when the port is already listening.
  • Launches a Chrome debugging instance only when a confirmed chromeExecutablePath is provided, then enables 9222.
  • Operates tabs by listing available tabs, selecting the target page, and running basic page reads, navigation, and scripts.
  • Reports blockers when the path is unknown, Chrome is missing, or 9222 is unavailable, instead of assuming a local Chrome installation.

Boundaries

The skill is Chrome CDP-specific and does not fall back to Edge or other browsers. It provides a stable runtime entry point for page and tab operations; higher-level automation can add wait logic, retries, and orchestration on top of it.

Use Cases

  • Check whether port 9222 is listening, attach to the existing Chrome CDP instance, and run page scripts.
  • Launch a Chrome debugging instance on 9222 using a confirmed executable path, then list and select a tab.
  • Prepare a Chrome runtime for higher-level skills, connect to a target tab, and perform basic reads, navigation, and scripts.
  • Report environment failure when 9222 is absent and no Chrome path is provided, without guessing paths or switching browsers.

Best For

  • Automation engineers who need to check whether a Chrome CDP instance can be attached in CI or local scripts.
  • Browser tool developers who need to run page inspection scripts against an existing Chrome instance.
  • Platform developers who need to prepare a Chrome runtime environment for higher-level agent skills.
  • Test engineers who need to launch Chrome debugging by confirmed path and operate a target tab.