chrome
Comprehensive Chrome DevTools development system with native Chrome capabilities for debugging, E2E testing, performance analysis, and browser automation
Best use case
chrome is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
Comprehensive Chrome DevTools development system with native Chrome capabilities for debugging, E2E testing, performance analysis, and browser automation
Teams using chrome 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/chrome/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How chrome Compares
| Feature / Agent | chrome | 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?
Comprehensive Chrome DevTools development system with native Chrome capabilities for debugging, E2E testing, performance analysis, and browser automation
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
SKILL.md Source
# Chrome: Complete Chrome DevTools Integration System Advanced browser development support system utilizing Chrome DevTools MCP's native capabilities for debugging, E2E testing, performance analysis, and comprehensive browser automation. ## Context - Browser status: `ps aux | grep chrome | wc -l` - Page count: Available pages via Chrome DevTools MCP - Performance state: Active traces and monitoring status - Network activity: Request monitoring and analysis - Console state: Message count and error levels ## Tool Priorities **ALWAYS prioritize Chrome DevTools MCP for all browser operations:** ### Chrome DevTools MCP (Primary Browser Control) - **Visual DOM Analysis**: Use `mcp__chrome-devtools__take_snapshot` for complete DOM structure analysis - **UI Problem Diagnosis**: Translate visual issues into technical causes - **Performance Analysis**: Use `mcp__chrome-devtools__performance_start_trace`, `performance_stop_trace` - **Browser Automation**: Use `mcp__chrome-devtools__click`, `fill`, `navigate_page`, `take_screenshot` - **Debugging**: Use `mcp__chrome-devtools__list_console_messages`, `evaluate_script` - **Network Monitoring**: Use `mcp__chrome-devtools__list_network_requests` ## Usage ```bash /chrome [action] [target] [options] ``` ### Available Actions | Action | Description | Example | |--------|-------------|---------| | `analyze` | Comprehensive page analysis | `/chrome analyze --full` | | `summarize` | Content summarization | `/chrome summarize --structure` | | `extract` | Data extraction | `/chrome extract --metadata` | | `logs` | View console messages | `/chrome logs --filter "ERROR"` | | `debug` | Debug specific issues | `/chrome debug "login fails"` | | `test` | E2E testing scenarios | `/chrome test --scenario login` | | `perf` | Performance analysis | `/chrome perf start --trace` | | `network` | Network monitoring | `/chrome network list` | | `screenshot` | Capture screenshots | `/chrome screenshot --full-page` | ### Options | Option | Description | |--------|-------------| | `--headless` | Headless mode | | `--verbose` | Detailed output | | `--analyze` | Auto-analysis | | `--filter` | Content filtering | ## Key Features ### AI-Driven Page Analysis - DOM + Console + Network + Performance + AI synthesis - Security & Accessibility analysis - Content summarization and structure analysis ### Debugging & Console Analysis - View recent console messages with filtering - Analyze specific error patterns - Execute debugging JavaScript ### E2E Testing & Automation - Complete form interaction - Multi-field form automation - E2E test scenario execution ### Performance Analysis - Performance tracing - Core Web Vitals analysis - Network performance analysis ## Requirements - Chrome DevTools MCP server configured and running - Chrome browser (stable/beta/dev/canary) - Node.js 22.12.0+ for MCP server
Related Skills
test
Advanced test implementation command with unit/E2E support, auto-execution, and smart fixing capabilities
serena
Token-efficient Serena MCP command for structured app development and problem-solving
project-guidelines-example
Example project-specific skill template based on a real production application.
notion-bug-pr
Skill that pulls bug tickets (titles containing 「不具合」) from a Notion database, investigates root cause in a GitHub repo, applies fixes, and opens draft PRs. Supports three modes — daily recurring schedule, one-shot at a specific time, or immediate on-demand run. Takes three or four args: Notion database URL, repo path or name, and either HH:MM (daily), "once HH:MM" (one-shot), or "now" (immediate).
graphify
any input (code, docs, papers, images, videos) to knowledge graph. Use when user asks any question about a codebase, documents, or project content - especially if graphify-out/ exists, treat the question as a /graphify query.
webapp-testing
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
web-design-guidelines
Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
typescript-advanced-types
Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.
tanstack-start
Full-stack React framework powered by TanStack Router with SSR, streaming, server functions, and deployment to any hosting provider.
tanstack-start-server-fn-testing
Unit-test TanStack Start createServerFn handlers via a global vi.mock that combines two patterns from Discussion #2701
tailwind-css-patterns
Provides comprehensive Tailwind CSS utility-first styling patterns including responsive design, layout utilities, flexbox, grid, spacing, typography, colors, and modern CSS best practices. Use when styling React/Vue/Svelte components, building responsive layouts, implementing design systems, or optimizing CSS workflow.
skill-creator
Create new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy.