Content
72%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 a lean, well-structured overview for an instruction-only review skill: it gives concrete tool names, budgets, and a clear Check-then-Fix flow, and defers all framework code to a single verified reference file at one level of depth. The main gap is workflow validation — no post-fix verification step is surfaced in the body, even though the reference file contains one.
Suggestions
Add an explicit post-fix validation step to the body, e.g. 'Verify: re-run Lighthouse and confirm no render-blocking stylesheets remain in <head> and layout is intact across breakpoints' — the reference file's Verification section already exists and just needs surfacing.
Trim the duplicated rationale: the intro sentence and the 'Explain' section both restate the render-blocking/LCP/FCP explanation Claude already knows.
Include one copy-paste-ready command in the Quick Reference (e.g. an npx critical or critters invocation) so the most common case is executable directly from the body.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient overall: the Quick Reference bullets are dense and specific, and Check/Fix sections are single-sentence directives. Minor over-explanation remains — the intro sentence and the 'Explain' section both restate the render-blocking/LCP/FCP rationale Claude already knows. Not 5 because that duplicated rationale could be trimmed. | 4 / 5 |
Actionability | Concrete, specific guidance: names exact tools ('critical, critters, or Lighthouse'), a concrete budget ('~14KB of critical above-the-fold CSS in <head>'), and explicit handling for the remainder ('Load remaining CSS asynchronously after page load'). As an instruction-only skill the absence of code in the body is acceptable, and full executable examples are properly deferred to references/rule.md. Not 5 because the body itself contains no copy-paste command (e.g. an npx critical invocation). | 4 / 5 |
Workflow Clarity | A sequence is present (Check analyzes the CSS loading strategy, Fix extracts and inlines), but validation checkpoints are missing or implicit — the body has no post-fix verification step (the reference file's Verification section is never surfaced in the body). Fits anchor 3: steps listed but sequence checkpoints absent. This is not a destructive or batch operation, so no hard cap applies, but it clearly does not meet anchor 4's 'most checkpoints present'. | 3 / 5 |
Progressive Disclosure | Clear overview body (~33 lines) with well-organized sections, and a single well-signaled one-level-deep reference: 'For full implementation details, code examples, and framework-specific guidance, see references/rule.md' — verified to exist (574 lines of framework implementations, build-tool integration, and verification guidance) with no nested references. Content is appropriately split between overview and detail, matching the anchor 5 pattern for a single-reference bundle. | 5 / 5 |
Total | 16 / 20 Passed |