Chrome Performance
Testing & Qualitychrome-performanceChrome Performance is an Agent Skill for testing & quality published in the hashgraph-online/awesome-codex-plugins repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.
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.
How to use this skill
Bring this guide into your coding agent with a prompt tailored to the tool you use.
- Open your project in Codex.
- Copy and paste the prompt below.
- Review files and risks before approving any action.
Inspect the Agent Skill at https://github.com/hashgraph-online/awesome-codex-plugins/blob/HEAD/plugins/win4r/chrome-devtools-codex-plugin/skills/chrome-performance/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/chrome-performance, but wait for my approval before writing files or running scripts.
Copying this prompt does not install or run the skill. Review third-party files before use.
Use this skill when performance findings need evidence from Chrome instead of code inspection alone.
Default Flow
- Start from the exact URL and device profile that reproduces the problem.
- Record a baseline with
lighthouse_auditorperformance_start_traceandperformance_stop_trace. - Drill into the highest-signal issue first, then inspect network, DOM, or scripts only as needed.
- After code changes, rerun the same scenario and compare the results.
Tool Selection
lighthouse_auditfor quick page-level diagnostics and report output.performance_start_traceandperformance_stop_tracefor deeper timing analysis.performance_analyze_insightto drill into a specific DevTools insight.emulateto keep device, network, CPU, and viewport conditions consistent.
Working Rules
- Keep the scenario deterministic: one URL, one interaction path, one device profile.
- Save traces and reports to files when they are large.
- Treat LCP, CLS, and INP as user-path problems; connect each finding to the specific element, request, or script that caused it.
- Avoid mixing unrelated experiments in one trace.
Expected Output
Return the problem, the evidence, the likely cause, and the concrete code area to change before proposing fixes.