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.
A compact, well-sectioned audit rule with concrete numeric criteria, an explicit check/fix workflow, and exemplary progressive disclosure to a single verified reference file. Its weakness is redundancy: the same flag criteria appear in three sections and the Explain section covers platform behavior Claude already knows.
Suggestions
Merge the "Check" and "Code Review" sections into one checklist to eliminate the duplicated flag criteria (dimensions, aspect ratio, file size, URL, width/height tags) currently repeated in Quick Reference as well.
Trim or cut the "Explain" section, since how social platforms use og:image and crop wrongly sized images is knowledge Claude already has; keep only the rule-specific thresholds.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The "Explain" section restates platform behavior Claude already knows ("Social platforms use og:image to construct the visual card shown when a URL is shared"), and the flag criteria are repeated across "Quick Reference", "Check", and "Code Review". It is mostly efficient given the short length, so above 2, but the duplication and known-concept explanation could be trimmed, so below 4. | 3 / 5 |
Actionability | Concrete thresholds throughout: "1200×630 pixels (1.91:1 aspect ratio)", "under 5 MB", "Export as JPEG at 80–85% quality", "og:image:width and og:image:height tags". As an instruction-only skill the guidance is actionable and specific, but no copy-paste commands or examples appear in the body itself, keeping it below 5. | 4 / 5 |
Workflow Clarity | The Check → Fix sequence carries explicit flag conditions ("Flag if width < 1200px, height < 630px, aspect ratio differs significantly from 1.91:1, or file size exceeds 5 MB"). Not 5 because "Check" and "Code Review" are two overlapping checklists rather than one unambiguous sequence, and there is no post-fix verification step. | 4 / 5 |
Progressive Disclosure | The body is under 50 lines with well-organized sections and a clearly signaled one-level-deep pointer: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md". The referenced file exists and contains only external links, with no nested file references. | 5 / 5 |
Total | 16 / 20 Passed |