Content
82%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The body is highly actionable with concrete MCP tool calls, thresholds, and a clear phased workflow, and it opens with a useful retrieval-bias reminder. It loses points mainly for some inlined reference material (framework detection tables) that Claude largely already knows and for lacking an explicit post-trace validation feedback loop.
Suggestions
Add an explicit validate-fix-retry loop after Phase 1/2 (e.g., 'If LCPBreakdown insight returns empty, verify insightSetId and retry with a discovered insight name') to strengthen workflow_clarity.
Move the framework/bundler config-file detection table and Phase 5 codebase checks into a references/ file to improve progressive_disclosure and trim tokens Claude already knows.
Tighten the 'Be assertive' / 'Verify before recommending' guideline bullets, which partly restate each other and pad the Key Guidelines section.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly lean with tables and concrete tool calls rather than explanations of concepts, but sections like the framework/config-file table and Phase 5 codebase analysis add reference material Claude largely already knows and could be trimmed. | 4 / 5 |
Actionability | Provides copy-paste-ready tool calls (navigate_page, performance_start_trace, performance_analyze_insight) with parameters and a Quick Reference table, plus specific thresholds and concrete fix examples like 'compress hero.png (450KB) to WebP'. | 5 / 5 |
Workflow Clarity | Clear five-phase sequence with a progress checklist and troubleshooting notes, plus an upfront MCP-availability validation gate; however there is no explicit validate-fix-retry feedback loop after the trace or insight steps. | 4 / 5 |
Progressive Disclosure | Well-organized sections (Quick Reference, Workflow, Output Format) keep the body navigable, and retrieval sources are cleanly tabulated rather than inlined; minor gaps are the inlined framework/config tables that could live in a reference file. | 4 / 5 |
Total | 17 / 20 Passed |