Content
71%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 well-structured overview with excellent progressive disclosure to a real, one-level reference, and the Check/Fix guidance is concrete and testable. Its main weakness is filler: the Explain and Code Review sections add boilerplate rather than skill-specific value.
Suggestions
Cut or merge the 'Explain' section — it re-describes reference content as meta-instruction and adds no unique guidance.
Replace the generic 'Code Review' boilerplate with rule-specific review points (e.g., which headers/anchor patterns to inspect for tracking redirects).
Pull the uBlock Origin DevTools verification steps from references/rule.md into a one-line inline checklist in the Check section to make the validation loop self-contained.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The Quick Reference, Check, and Fix sections are dense and useful, but the 'Explain' section restates content already in references/rule.md as meta-instruction, and the 'Code Review' section is generic boilerplate ('Review server config, headers, forms, and integration points related to Blocked Tracking Links') that could apply to any rule — matching 'Mostly efficient but includes some unnecessary explanation or could be tightened'. Not a 4 because the boilerplate sections are noticeable rather than minor, and not a 2 because the body avoids explaining concepts Claude already knows and stays compact. | 3 / 5 |
Actionability | The Check section is concretely executable ('Identify external script sources, image src URLs, iframe src URLs, and anchor href values... (googletagmanager.com, hotjar.com, facebook.net, doubleclick.net, etc.). Test whether these resources load successfully with uBlock Origin enabled.'), and Fix gives specific remedies (self-host, reverse proxy, direct destination URLs with UTM parameters), with copy-paste code properly deferred to references/rule.md — matching 'Mostly executable guidance; concrete code or commands with minor gaps'. Not a 5 because the body itself contains no executable example, relying on the reference for code. | 4 / 5 |
Workflow Clarity | The Check → Fix sequence is clear and Check embeds an explicit validation step ('Test whether these resources load successfully with uBlock Origin enabled'), expanded by the Verification section in references/rule.md (DevTools Network tab, filter by 'Blocked'), matching 'Clear sequence with most checkpoints present; minor validation gaps'. Not a 5 because the sections are unordered headings rather than an explicit sequence, and the body's own validation guidance is a single sentence deferred to the reference; not a 3 because validation is present and named, not implicit. | 4 / 5 |
Progressive Disclosure | The ~45-line body is a genuine overview (summary bullets, check/fix guidance) with one clearly signaled, one-level-deep reference — 'For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`' — and the file exists in the bundle with exactly that content, matching 'Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'. The anti-drift check against anchor 4 shows only trivial summary overlap between body and reference, not misplaced content. | 5 / 5 |
Total | 16 / 20 Passed |