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, actionable audit skill with excellent progressive disclosure into references/rule.md. Its main weaknesses are redundancy — the Check and Code Review sections duplicate each other and Explain repeats the intro — and the absence of an explicit verification step in the body's workflow.
Suggestions
Merge the "Check" and "Code Review" sections, which cover the same five criteria, into a single checklist to remove duplication.
Trim or cut the "Explain" section, whose content Claude already knows and which largely restates the intro paragraph.
Add a short verification step to the workflow (e.g., "After fixes, re-inspect the rendered HTML and confirm the JSON-LD validates") or explicitly point to the Verification section of references/rule.md.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | "Check" and "Code Review" list essentially the same five criteria (semantic tags, JS-free content, standalone headings, JSON-LD, FAQ patterns), and the "Explain" section restates the intro's point about answer engines extracting text — mostly efficient, but several sections could be merged or trimmed. | 3 / 5 |
Actionability | Concrete, specific guidance throughout: exact tags to check ("<h1>–<h6>, <p>, <ul>, <ol>, <table>"), named schema types ("Article, FAQPage, HowTo"), and directive fixes ("Replace JavaScript-rendered content with server-side rendered HTML"). Minor gap: no concrete verification command or example markup in the body itself. | 4 / 5 |
Workflow Clarity | The Check → Fix sequence is clear and the numbered criteria make the audit unambiguous, and the skill's read-only nature means the destructive-operation cap does not apply. However, no post-fix verification checkpoint appears in the body — it lives only in references/rule.md's Verification section, which the workflow never points to. | 4 / 5 |
Progressive Disclosure | The ~45-line body is a concise overview with well-organized sections, and it ends with a clearly signaled one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and that file exists and holds exactly those details (code examples, FAQ/HowTo JSON-LD, SSR patterns, exceptions, verification). | 5 / 5 |
Total | 16 / 20 Passed |