Electron Devtools Testing
ankitvgupta/exo
Test the Electron app interactively using Chrome DevTools Protocol.
Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP.
Install Chrome Devtools
$ npx skills add github/awesome-copilot --skill chrome-devtools -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install github/awesome-copilot chrome-devtools --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/chrome-devtools .claude/skills/chrome-devtools && rm -rf skills-srcUse ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.
Claude Code skills documentation · loads skills from .claude/skills/
Install the "chrome-devtools" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/chrome-devtools into .claude/skills/chrome-devtools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-devtools", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/github/awesome-copilot/tree/main/skills/chrome-devtoolsType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add github/awesome-copilot --skill chrome-devtools -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install github/awesome-copilot chrome-devtools --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/chrome-devtools .agents/skills/chrome-devtools && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "chrome-devtools" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/chrome-devtools into .agents/skills/chrome-devtools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-devtools", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill chrome-devtools -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install github/awesome-copilot chrome-devtools --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/chrome-devtools .cursor/skills/chrome-devtools && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "chrome-devtools" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/chrome-devtools into .cursor/skills/chrome-devtools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-devtools", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/github/awesome-copilot.git --path skills/chrome-devtools--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add github/awesome-copilot --skill chrome-devtools -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install github/awesome-copilot chrome-devtools --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/chrome-devtools .gemini/skills/chrome-devtools && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "chrome-devtools" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/chrome-devtools into .gemini/skills/chrome-devtools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-devtools", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install github/awesome-copilot chrome-devtoolsInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add github/awesome-copilot --skill chrome-devtools -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/chrome-devtools .github/skills/chrome-devtools && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "chrome-devtools" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/chrome-devtools into .github/skills/chrome-devtools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-devtools", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add github/awesome-copilot --skill chrome-devtools -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install github/awesome-copilot chrome-devtools --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/github/awesome-copilot.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/chrome-devtools .opencode/skills/chrome-devtools && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "chrome-devtools" agent skill from https://github.com/github/awesome-copilot/tree/main/skills/chrome-devtools into .opencode/skills/chrome-devtools/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "chrome-devtools", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
Facts
- Skill name
chrome-devtools- GitHub stars
- 40k
- Used in
- 2 other repos
- Token cost
- ~1k tokens
- SKILL.md length
- 407 words
- Files
- 1
- Skills in repo
- 417
- Repo updated
- First seen
- Licence
- MIT
At a glance
Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP.
- Works in 4 steps: Navigation & Page Management → Input & Interaction → Debugging & Inspection → …
- Interacting with web pages
- SKILL.md covers Overview, When to Use, Tool Categories and Workflow Patterns, plus 1 more section
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Chrome Devtools is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.
Its SKILL.md is about 1k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.
It sits in Testing & QA, covering Browser testing and Browser automation. It works with Chrome DevTools and Model Context Protocol. The repository describes itself as: Community-contributed instructions, agents, skills, and configurations to help you make the most of GitHub Copilot. The licence is MIT.
When your agent uses it
- Interacting with web pages
- Capturing screenshots
- Analyzing network traffic
- Profiling performance
Example prompts
- “/chrome-devtools”
Workflow steps
4 steps, taken from the step headings in SKILL.md.
What it can do on your machine
Read from SKILL.md and the folder at commit 727ff2e. It shows what the files ask for, not the result of running them.
Tool permissions
Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.
From allowed-tools in the SKILL.md frontmatter.
Runs code
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
From the folder's file list and the shell code blocks in SKILL.md.
Network
No URLs in SKILL.md.
From URLs in SKILL.md, links to its own repository left out.
Credentials
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
Context cost
Chrome Devtools loads about 1k tokens when it runs. Until then it costs about 56 tokens; SKILL.md has 407 words of instructions outside code blocks.
Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.
Safety
Auto-check passed
The automated check found no risky patterns in SKILL.md.
Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.
SKILL.md
The full file from github/awesome-copilot at commit 727ff2e, republished under its MIT licence (© github). 407 words, ~1,037 tokens.
Download SKILL.mdSave it as
.claude/skills/chrome-devtools/SKILL.md (or your agent's skills folder).- name
- chrome-devtools
- description
- Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.
- license
- MIT
Chrome DevTools Agent
Overview
A specialized skill for controlling and inspecting a live Chrome browser. This skill leverages the chrome-devtools MCP server to perform a wide range of browser-related tasks, from simple navigation to complex performance profiling.
When to Use
Use this skill when:
- Browser Automation: Navigating pages, clicking elements, filling forms, and handling dialogs.
- Visual Inspection: Taking screenshots or text snapshots of web pages.
- Debugging: Inspecting console messages, evaluating JavaScript in the page context, and analyzing network requests.
- Performance Analysis: Recording and analyzing performance traces to identify bottlenecks and Core Web Vital issues.
- Emulation: Resizing the viewport or emulating network/CPU conditions.
Tool Categories
1. Navigation & Page Management
new_page: Open a new tab/page.navigate_page: Go to a specific URL, reload, or navigate history.select_page: Switch context between open pages.list_pages: See all open pages and their IDs.close_page: Close a specific page.wait_for: Wait for specific text to appear on the page.
2. Input & Interaction
click: Click on an element (useuidfrom snapshot).fill/fill_form: Type text into inputs or fill multiple fields at once.hover: Move the mouse over an element.press_key: Send keyboard shortcuts or special keys (e.g., "Enter", "Control+C").drag: Drag and drop elements.handle_dialog: Accept or dismiss browser alerts/prompts.upload_file: Upload a file through a file input.
3. Debugging & Inspection
take_snapshot: Get a text-based accessibility tree (best for identifying elements).take_screenshot: Capture a visual representation of the page or a specific element.list_console_messages/get_console_message: Inspect the page's console output.evaluate_script: Run custom JavaScript in the page context.list_network_requests/get_network_request: Analyze network traffic and request details.
Show full SKILL.md (147 more words)Show less
4. Emulation & Performance
resize_page: Change the viewport dimensions.emulate: Throttling CPU/Network or emulating geolocation.performance_start_trace: Start recording a performance profile.performance_stop_trace: Stop recording and save the trace.performance_analyze_insight: Get detailed analysis from recorded performance data.
Workflow Patterns
Pattern A: Identifying Elements (Snapshot-First)
Always prefer take_snapshot over take_screenshot for finding elements. The snapshot provides uid values which are required by interaction tools.
1. `take_snapshot` to get the current page structure.
2. Find the `uid` of the target element.
3. Use `click(uid=...)` or `fill(uid=..., value=...)`.Pattern B: Troubleshooting Errors
When a page is failing, check both console logs and network requests.
1. `list_console_messages` to check for JavaScript errors.
2. `list_network_requests` to identify failed (4xx/5xx) resources.
3. `evaluate_script` to check the value of specific DOM elements or global variables.Pattern C: Performance Profiling
Identify why a page is slow.
1. `performance_start_trace(reload=true, autoStop=true)`
2. Wait for the page to load/trace to finish.
3. `performance_analyze_insight` to find LCP issues or layout shifts.Best Practices
- Context Awareness: Always run
list_pagesandselect_pageif you are unsure which tab is currently active. - Snapshots: Take a new snapshot after any major navigation or DOM change, as
uidvalues may change. - Timeouts: Use reasonable timeouts for
wait_forto avoid hanging on slow-loading elements. - Screenshots: Use
take_screenshotsparingly for visual verification, but rely ontake_snapshotfor logic.
© github, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Files
Just SKILL.md in skills/chrome-devtools of github/awesome-copilot.
Open the folder on GitHubat commit 727ff2e
Used in 2 other repositories
We found 2 copies of this SKILL.md (exact, near-identical or edited) in other folders, from 2 other GitHub owners. This page covers the copy in github/awesome-copilot, which our catalogue first saw on October 7, 2026.
Compare with similar skills
Chrome Devtools next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Chrome Devtools this skillgithub/awesome-copilot | 40k | 2 repos | ~1k | Automated safety check: Pass | MIT | |
| Electron Devtools Testingankitvgupta/exo | 496 | — | ~2.4k | Automated safety check: Pass | Custom licence | |
| Sap Sac Test Automationsecondsky/sap-skills | 460 | — | ~4.2k | Automated safety check: Pass | GPL-3.0 | |
| Cdp Connectadobe/skills | 195 | — | ~847 | Automated safety check: Pass | Apache-2.0 | |
| Browseragutinbaigo28/financial-agent-api | 128 | 1 repos | ~480 | Automated safety check: Pass | None | |
| Chrome Devtoolsaeroxy/chrome-devtools-cli | 253 | — | ~9k | Automated safety check: Warn | None |
Similar skills
Sap Sac Test Automation
secondsky/sap-skills
SAP Analytics Cloud (SAC) automated testing skill for designing capability-gated browser discovery and deterministic Playwright test suites for SAC stories, dashboards, reports, planning workflows…
Cdp Connect
adobe/skills
Connect Claude Code to an existing Chrome browser via CDP (Chrome DevTools Protocol).
Browser
agutinbaigo28/financial-agent-api
This skill should be used for browser automation tasks using Chrome DevTools Protocol (CDP).
Chrome Devtools
aeroxy/chrome-devtools-cli
A skill your agent uses when the user asks to "take a screenshot of a website", "navigate to a URL", "fill a form in the browser", "interact with Chrome", or when a chrome automation task is needed.
Browser Navigation
Factory-AI/factory-plugins
Automate browser interactions for web testing, form filling, screenshots, and data extraction.
More from github/awesome-copilot
All 417 skills in this repo- Official
Acquire Codebase Knowledge
github/awesome-copilot
Maps an unfamiliar codebase into seven evidence-backed documents in docs/codebase/, using a scan script and templates, for onboarding or architecture write-ups.
- Official
Azure Architecture Autopilot
github/awesome-copilot
Designs Azure infrastructure from a natural-language description, or diagrams an existing resource group, then refines the design through conversation and deploys it with Bicep.
- Official
Draw.io Diagram Generator
github/awesome-copilot
Generates, edits and validates draw.io files with correct mxGraph XML, covering flowcharts, architecture, sequence, ER and UML class diagrams.
- Official
Credit Risk Data Cleaning
github/awesome-copilot
Cleans raw credit data and screens variables before loan modeling, dropping unstable, noisy or redundant features and writing an Excel report of every step.
- Official
Daily Focus Board
github/awesome-copilot
Builds a warm, browser-based daily focus board the user updates by talking to their agent, with Eisenhower priorities, a brain-dump box and kind not-today carryover.
- Official
Python Pypi Package Builder
github/awesome-copilot
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI.
Related
Works with
Questions about Chrome Devtools
What does Chrome Devtools do?
Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Chrome Devtools is an agent skill from github/awesome-copilot, published by the product's own GitHub organization. Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP.
When should I use Chrome Devtools?
Chrome Devtools fits situations like: interacting with web pages; capturing screenshots; analyzing network traffic; profiling performance.
How do I install Chrome Devtools in Claude Code?
Run `npx skills add github/awesome-copilot --skill chrome-devtools -a claude-code`. Or copy the skill folder (skills/chrome-devtools in github/awesome-copilot) into .claude/skills/chrome-devtools in your project. Claude Code loads it when a task matches its description.
How do I install Chrome Devtools in Codex?
Run `npx skills add github/awesome-copilot --skill chrome-devtools -a codex`. Or copy the skill folder (skills/chrome-devtools in github/awesome-copilot) into .agents/skills/chrome-devtools in your project. Codex loads it when a task matches its description.
Can I use Chrome Devtools in Cursor, Gemini CLI or GitHub Copilot?
Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add github/awesome-copilot --skill chrome-devtools -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/chrome-devtools, .gemini/skills/chrome-devtools, .github/skills/chrome-devtools and .opencode/skills/chrome-devtools in your project.
What does Chrome Devtools need to run?
SKILL.md names no scripts, command-line tools or credentials: Chrome Devtools is instructions for the agent only.
Does Chrome Devtools access the network?
SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.
Is Chrome Devtools safe to install?
Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.
What licence does Chrome Devtools use?
Chrome Devtools is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.
How many tokens does Chrome Devtools use?
About 1k tokens (SKILL.md is roughly 4.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Chrome Devtools?
Skills that share tags, products or a category with Chrome Devtools: Electron Devtools Testing (ankitvgupta/exo, 496 stars), Sap Sac Test Automation (secondsky/sap-skills, 460 stars), Cdp Connect (adobe/skills, 195 stars) and Browser (agutinbaigo28/financial-agent-api, 128 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Chrome Devtools?
github (a GitHub organization, an official publisher) maintains it in github/awesome-copilot, which has 39,748 GitHub stars. The repository holds 417 skills in this directory. The repository was last updated on October 7, 2026.
Source: github/awesome-copilot on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.