Justfinethanku Cc Chrome Devtools Mcp Skill
justfinethanku-cc_chrome_devtools_mcp_skill is a Claude Code plugin for the Ship phase that connects Claude to chrome-devtools-mcp for CDP-driven browser testing, performance, and accessibility automation.
by justfinethanku · github.com/justfinethanku/cc_chrome_devtools_mcp_skill
Add this plugin so Claude Code can drive Chrome via CDP through chrome-devtools-mcp for automated browser tests, Core Web Vitals, network visibility, and accessibility checks.
Add it to Claude Code
Install the plugin in Claude Code. One command, paste-ready.
/plugin install justfinethanku-cc_chrome_devtools_mcp_skill@justfinethanku/cc_chrome_devtools_mcp_skillBuilt to be called by your agent
Skillselion is itself an MCP server. Your agent can pull this entry and a paste-ready install config straight from the API - no copy-paste.
Retrieve this entry with skillselion.get_details("plugin:justfinethanku/cc_chrome_devtools_mcp_skill") and the paste-ready config with skillselion.get_install_config("plugin:justfinethanku/cc_chrome_devtools_mcp_skill").
What it does
justfinethanku-cc_chrome_devtools_mcp_skill is a Claude Code plugin that exposes automated Chrome browser testing and performance analysis through the Chrome DevTools Protocol using the chrome-devtools-mcp server. Indie builders shipping web apps install it when they want the agent to run real-browser checks—navigation, DOM interaction, network traces, debugging, accessibility validation, and Core Web Vitals—without maintaining a separate Playwright-only harness for every task. The description calls out 27 tools, which covers a full professional testing surface rather than a thin screenshot wrapper. Use it during ship prep to catch regressions, during launch when vitals and a11y affect SEO and conversion, and during grow when monitoring production-like behavior. You need MCP wiring and a Chrome/CDP environment the server can reach. It complements unit tests and static review; it does not replace security audits or backend contract tests.
Highlights
- Chrome DevTools Protocol automation via the chrome-devtools-mcp server from Claude Code
- 27 professional-grade tools for browser testing, performance, network, and debugging
- Core Web Vitals and performance measurement workflows for real Chrome sessions
- Accessibility validation and automated web application test flows
- MCP-backed skill pattern: agent invokes CDP tools instead of manual DevTools clicking
Why builders use it
Manual Chrome DevTools work does not scale for solo builders who need repeatable browser tests, vitals, and a11y validation inside their agent coding loop.
After install, Claude Code can call 27 CDP-backed MCP tools to automate Chrome sessions for testing, measurement, and validation instead of ad hoc manual checks.
At a glance
- Type - Plugin in Testing.
- Adoption - 0 installs, 28 stars, 0 votes.
FAQ
Who is justfinethanku-cc_chrome_devtools_mcp_skill for?
Claude Code users building web apps who want automated Chrome testing, performance analysis, and accessibility checks via the chrome-devtools-mcp server.
When should I use justfinethanku-cc_chrome_devtools_mcp_skill?
Use it before release and during perf or a11y investigations when you need real-browser automation, network visibility, debugging, or Core Web Vitals through CDP.
How do I add justfinethanku-cc_chrome_devtools_mcp_skill to my agent?
Install the Claude Code plugin, configure the chrome-devtools-mcp server per the repo skill docs, ensure Chrome/CDP is reachable, then enable the skill so Claude can invoke its 27 tools.
Comments
Share how you use justfinethanku-cc_chrome_devtools_mcp_skill, gotchas, or tips for other indie builders.
No comments yet - be the first to share how you use it.