Individual skill
chrome-devtools
Use Chrome DevTools MCP to inspect live pages, reproduce browser issues, automate user flows, inspect console and network activity, and verify frontend fixes in a real Chrome session. Trigger when the user mentions browser bugs, client-side errors, broken forms, flaky UI behavior, or asks to interact with a site directly.
plugins/win4r/chrome-devtools-codex-plugin/skills/chrome-devtools/SKILL.md
Source commit d780783eba4ecc7c8b9429f95c9362df95f07c61
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- Yes
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Network or broad shell
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 1,532
- Repository last updated
- Nov 6, 2026
- License
- Apache-2.0
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- ai-coding Repository topic
- awesome Repository topic
- awesome-list Repository topic
- codex Repository topic
- codex-plugins Repository topic
- openai Repository topic
- codex-skill Repository topic
- codex-skills Repository topic
- marketplace Repository topic
- codex-marketplace Repository topic
- design Derived category
- design-interface Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
Use this skill when source inspection alone is not enough and Codex should operate a live browser.
## Default Flow
1. Open or reuse a page with `new_page` or `navigate_page`.
2. Wait for the relevant UI if needed with `wait_for`.
3. Capture structure with `take_snapshot`.
4. Interact using `uid` values from the snapshot.
5. Inspect the relevant evidence surface:
- `list_console_messages` or `get_console_message` for runtime errors
- `list_network_requests` or `get_network_request` for API and asset failures
- `take_screenshot` when visible state matters
- `evaluate_script` for targeted DOM or app-state checks
6. Re-run the smallest verification path after each code change.