Content
78%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 lean, concrete, well-sectioned rule set: nearly every bullet carries an exact CSS value, timing, or API name, and the guidance is easy to act on. Its main gaps are the absence of a complete executable example (a component or GSAP snippet) and any verification step for the reduced-motion accessibility requirement.
Suggestions
Add one minimal, copy-paste example combining the core ideas — e.g., a floating glassmorphism card with a staggered GSAP ScrollTrigger entrance — so the common case is fully executable.
Include a quick verification step such as 'Confirm all animations are gated behind a prefers-reduced-motion check before delivering' to close the workflow's accessibility checkpoint.
Trim the role-play framing in the Role Overview (e.g., 'You are a world-class UI/UX Engineer') since it repeats the frontmatter description without adding actionable content.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense and value-laden (exact shadows like 'box-shadow: 0 20px 40px rgba(0,0,0,0.05)', exact transforms, timings, and CSS properties), explaining little that Claude already knows. Minor trimmable padding remains ('You are a world-class UI/UX Engineer...', 'buttery-smooth scroll animations'), so it sits at anchor 4 rather than the fully lean anchor 5. | 4 / 5 |
Actionability | Concrete, executable guidance dominates: 'backdrop-filter: blur(12px)', 'transform: rotateX(60deg) rotateZ(-45deg)', 'minimum 0.3s ease-out', 'stagger ... by 0.1s', 'will-change: transform', and 'prefers-reduced-motion: reduce'. It is not a 5 because there is no complete copy-paste example (e.g., a floating-card component or a GSAP ScrollTrigger snippet) covering the common case. | 4 / 5 |
Workflow Clarity | The skill is a clear, well-categorized rule set rather than a multi-step pipeline, and it involves no destructive or batch operations, so no validation cap applies. It misses anchor 5 because there is no explicit build sequence or verification step (e.g., confirming the reduced-motion fallback actually disables the animations) for the single task it governs. | 4 / 5 |
Progressive Disclosure | The skill is under 50 lines with no bundle files and no need for external references, and the body is cleanly organized into labeled sections (Role Overview, Tech Stack, Design Principles, Motion & Animation Rules, Execution Constraints). Per the rubric's guideline for short self-contained skills, well-organized sections alone earn a 5. | 5 / 5 |
Total | 17 / 20 Passed |