Individual skill
chrome-performance
Use Chrome DevTools MCP for frontend performance work such as slow page loads, LCP, CLS, INP, Lighthouse regressions, scripting hotspots, or layout thrash. Trigger when the user asks for page speed analysis, Core Web Vitals debugging, trace-based investigation, or before-and-after performance verification.
plugins/win4r/chrome-devtools-codex-plugin/skills/chrome-performance/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
- testing Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Browse files
SKILL.mdcore · 1,633 bytes
Read excerpt
Use this skill when performance findings need evidence from Chrome instead of code inspection alone.
## Default Flow
1. Start from the exact URL and device profile that reproduces the problem.
2. Record a baseline with `lighthouse_audit` or `performance_start_trace` and `performance_stop_trace`.
3. Drill into the highest-signal issue first, then inspect network, DOM, or scripts only as needed.
4. After code changes, rerun the same scenario and compare the results.
## Tool Selection
- `lighthouse_audit` for quick page-level diagnostics and report output.
- `performance_start_trace` and `performance_stop_trace` for deeper timing analysis.
- `performance_analyze_insight` to drill into a specific DevTools insight.