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 tight, actionable skill body with concrete numeric thresholds and a clean one-level reference split. The main costs are a redundant intro/Explain pair that re-explains platform behavior Claude already knows, overlap between the Check and Code Review sections, and the absence of any executable command for the check/resize steps in the body itself.
Suggestions
Merge the intro and Explain sections into one brief statement, cutting the duplicated explanation of how platforms crop or skip images.
Consolidate the overlapping Check and Code Review sections into a single checklist, and add a post-fix re-verification step (e.g. re-fetch the image and confirm dimensions).
Include one executable snippet or command for checking an image's dimensions and file size (e.g. curl plus ImageMagick `identify`), since the body currently tells Claude what to verify but not how.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The intro paragraph ("An incorrectly sized og:image is displayed poorly or not at all... resulting in blank or distorted link previews") and the Explain section ("Social platforms use og:image to construct the visual card...") are mutually redundant and explain platform behavior Claude already knows. Not 2 because Quick Reference, Check, Fix, and Code Review are dense and unpadded; not 4 because the duplication spans two sections, beyond a minor instance. | 3 / 5 |
Actionability | Concrete thresholds throughout — "Flag if width < 1200px, height < 630px", "Export as JPEG at 80–85% quality", "Add og:image:width and og:image:height tags" — plus a 5-point Code Review checklist. Not 5 because the body gives no executable command or snippet for fetching the image or checking/resizing dimensions. | 4 / 5 |
Workflow Clarity | Check → Fix form a clear sequence with explicit flag criteria and a concrete verification checklist in Code Review. Not 5 because the Check and Code Review sections overlap substantially and there is no re-verification loop after fixing; not 3 because sequence and checkpoints are explicit, not implicit. | 4 / 5 |
Progressive Disclosure | A lean ~45-line body 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`" — and I verified references/rule.md exists and contains exactly those details (code examples, platform table, framework guidance). The split is appropriate and navigation is unambiguous. | 5 / 5 |
Total | 16 / 20 Passed |