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 dense, well-structured audit checklist that is unusually concrete for an instruction-only skill — specific fonts, values, CSS properties, and a fix-priority sequence make it directly actionable. Its main weaknesses are the absence of any bundle files for a body this long (everything is inlined) and no explicit validation/feedback loop beyond 'test after every change'.
Suggestions
Split the Design Audit categories into references/ files (e.g. typography.md, color.md, layout.md) and keep a condensed audit index in SKILL.md so only the relevant checklist loads per project.
Add an explicit feedback loop to the workflow, e.g. after applying fixes: verify functionality, revert on regression, and re-run the audit to confirm the pattern was resolved.
Include one short before/after code snippet (e.g. a card or button) to anchor the abstract 'premium' style guidance in executable markup.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Nearly every line is a compact, imperative directive with concrete values (fonts, hexes, CSS properties) and no explanations of concepts Claude already knows. A few long prose items (collapsed-navigation rules, the mid-page dark-section entry) could be tightened, keeping it below a 5. | 4 / 5 |
Actionability | Concrete throughout: named fonts ('Geist', 'Satoshi'), specific values ('#0a0a0a', 200-300ms, 65 characters), exact CSS properties ('font-variant-numeric: tabular-nums', 'min-height: 100dvh', 'text-wrap: balance') and a usable placeholder URL. As an instruction-only skill this is highly actionable; the minor gap is that no complete snippet demonstrates any fix end-to-end. | 4 / 5 |
Workflow Clarity | An explicit Scan -> Diagnose -> Fix sequence, a numbered Fix Priority order, and Rules including 'Test after every change' as a validation checkpoint. It lacks an explicit error-recovery/feedback loop for when a change breaks something, so it does not reach 5. | 4 / 5 |
Progressive Disclosure | Sections are well-organized with clear headers, but the ~175-line body inlines the entire audit checklist with no reference files at all. For a skill this size, the audit categories are stable reference material that could live in references/ files, so content that should be separate is inline. | 3 / 5 |
Total | 15 / 20 Passed |