Skip to content

docs: add explicit install + connect sections to chrome-devtools-remote SKILL.md - #36

Merged
dzianisv merged 2 commits into
mainfrom
docs/skill-install-connect-use
Jun 20, 2026
Merged

dzianisv merged 2 commits into
mainfrom
docs/skill-install-connect-use

Conversation

@dzianisv

Copy link
Copy Markdown
Owner

Summary

  • Add dedicated Install and Connect sections to SKILL.md
  • Prettier formatting cleanup

Test Plan

  • Verify SKILL.md renders correctly in Claude Code

dzianisv and others added 2 commits May 20, 2026 08:52
…ls-remote SKILL.md

The skill previously assumed `chrome-devtools` was already on PATH and
treated connection setup as a "Preflight" detail. Restructure so an
agent reading SKILL.md cold gets, in order:

  1. Install — `npm install -g @vibebrowser/chrome-devtools-mcp` plus
     two real troubleshooting recipes (PATH miss, pkce-challenge bundling
     gap from issue #17).
  2. Connect — set $CHROME_DEVTOOLS_MCP_REMOTE_URL, verify with
     `status`, and a connection-time flag table covering self-signed
     certs, bearer tokens, custom headers, and Tailscale offline.
  3. (existing) Common operations — the tool calls themselves.

No behavior change; documentation only.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@dzianisv
dzianisv merged commit 304801c into main Jun 20, 2026
8 of 34 checks passed
@dzianisv
dzianisv deleted the docs/skill-install-connect-use branch June 20, 2026 10:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant