Content
57%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
A well-structured overview with good progressive disclosure and a real reference file, but it carries some redundant explanation across sections and only a light verification step for a batch-replace workflow.
Suggestions
Collapse the overlapping scan guidance in Check and Code Review into one place, and trim the 'Explain' section's restatement of well-known HTTPS ranking facts to improve conciseness.
Add an explicit validate→fix→re-scan feedback loop after the CMS search-and-replace step rather than a single terminal 'verify with grep'.
Move or inline one concrete avoid/correct HTML code pair into the body so the core action is copy-paste ready without opening the reference.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is mostly tight, but the 'Explain' section restates concepts Claude already knows (HTTPS as a ranking factor) and the Check/Fix/Code Review sections overlap on the same href-scanning guidance, so it could be trimmed. | 2 / 3 |
Actionability | Provides specific guidance — concrete URL rewrites (http://yourdomain.com/path → /path), a copy-paste `grep -r 'href="http://'` command, and exact attribute lists — but the fuller executable HTML examples are delegated to the reference rather than present in-body. | 2 / 3 |
Workflow Clarity | The Fix section is a clear 7-step numbered sequence ending with a verify step (step 7), but there is no explicit validate→fix→retry feedback loop for the batch search-and-replace operation, so it stops at the listed-steps-with-gaps anchor. | 2 / 3 |
Progressive Disclosure | The body is a concise overview organized into clear sections (Quick Reference, Check, Fix, Explain, Code Review) with a single well-signaled one-level-deep pointer to references/rule.md, which exists and holds the detailed examples. | 3 / 3 |
Total | 9 / 12 Passed |