Content
82%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.
High-quality single-file skill body: executable, well-structured, and disciplined about token efficiency. The main improvement opportunities are reducing restatement between the Rules and Anti-Patterns sections and providing an explicit ordered setup sequence.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense, rule-first, and free of explanations Claude already knows, but the 8 rules are restated nearly verbatim in the Anti-Patterns table and 'When to Activate' partially duplicates the frontmatter description, so a few sections could be trimmed. | 4 / 5 |
Actionability | All code is fully executable and copy-paste ready — motionTokens, springs, motionConfig with typeof window guards, the useSafeMotion hook, and a complete FadeInCard with imports, file paths, and 'use client' — plus decision tables and a wrong/correct SSR pair covering the common cases. | 5 / 5 |
Workflow Clarity | Sequencing and constraints are unambiguous for a foundation skill ('Load this skill before any animation work begins', ordered accessibility priority tiers, When to Activate list), but there is no explicit ordered setup workflow or validation checkpoint; this is a reference layer, not a destructive or batch operation, so the workflow cap does not apply. | 4 / 5 |
Progressive Disclosure | No bundle files exist and the body references none, so there are no dead links; the single file is well organized with clear sections and decision tables. The anti-pattern table and token reference could arguably live in separate files, which keeps it below the top anchor. | 4 / 5 |
Total | 17 / 20 Passed |