Content
65%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.
A well-structured, token-efficient overview that delegates executable detail appropriately to one clearly signaled reference file. The gaps are in the body's own actionability and workflow: no concrete command or snippet inline, and no explicit post-fix re-measurement loop.
Suggestions
Inline one small executable anchor in the body (e.g. the async GTM snippet or the exact Lighthouse/DevTools steps to spot third-party blocking), so the Fix section is not purely high-level.
Make the measure → fix → re-measure loop explicit: add a verify step after Fix (e.g. 'Re-run Lighthouse and confirm the third-party blocking / LCP improvement') rather than leaving verification only in the reference file.
Drop the generic opening sentence about what an unoptimized GTM setup causes; Claude already knows this, and the Quick Reference bullets carry the same information.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is lean and section-driven with almost no padding, but the opening sentence ('An unoptimized GTM setup can lead to significant main-thread blocking and increased page weight, slowing down the overall user experience') explains background Claude already knows and could be trimmed. | 4 / 5 |
Actionability | The body gives high-level direction with named tools ('Place the GTM script in the <head> but audit its impact', 'evaluate its impact on page performance using Lighthouse', 'Use Server-Side GTM'), but all executable code and commands are delegated to references/rule.md — no snippet, command, or specific DevTools/Lighthouse step appears in the body itself. | 3 / 5 |
Workflow Clarity | The Check → Fix → Explain → Code Review sections establish a rough sequence with a measure-first checkpoint ('Verify that GTM is implemented correctly... using Lighthouse'), but the measure → fix → re-measure feedback loop is only implicit in the body; the verification steps live in the reference file. | 3 / 5 |
Progressive Disclosure | The body is under 50 lines, cleanly sectioned, and points to a single one-level-deep reference that exists in the bundle ('For full implementation details, code examples, and framework-specific guidance, see references/rule.md'), with the reference's contents clearly signaled. | 5 / 5 |
Total | 15 / 20 Passed |