review-animations

Reviews animation and motion code against a high craft bar derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.

Quality

75%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/review-animations/SKILL.md

The canonical home for this skill is review-animations in emilkowalski/skills

Quality

Content

92%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is lean, highly actionable, and gives a well-sequenced review workflow with concrete fixes and explicit approval criteria. Its one real defect is progressive disclosure: STANDARDS.md is referenced throughout but is missing from the bundle, leaving dead links where detailed values should live.

Suggestions

Add the missing STANDARDS.md (or a references/STANDARDS.md) so the repeated [STANDARDS.md](STANDARDS.md) links resolve; update the link paths to match the actual bundle location.

If STANDARDS.md is intentionally absent, inline the few exact values the body already promises ('per-element budgets live in STANDARDS.md') so the skill is self-sufficient.

Consider a one-line 'Bundle:' note listing the reference file so the structure is visible without scanning the prose.

Dimension	Reasoning	Score
Conciseness	The body is dense and assumes Claude's competence — it never explains known concepts (what CSS transitions, easing, or transform are); every section (ten standards, escalation triggers, remedial hierarchy, output format) earns its tokens, matching the 'lean and efficient; every token earns its place' anchor rather than the padded level-2 example.	3 / 3
Actionability	It provides copy-paste-ready fixes in the Before/After/Why table ('transition: all 300ms' → 'transition: transform 200ms ease-out', 'scale(0)' → 'scale(0.95); opacity: 0') plus concrete thresholds ('sub-300ms', 'scale(0.9–0.97)') and exact pattern triggers, meeting the 'fully executable; specific examples; copy-paste ready' anchor.	3 / 3
Workflow Clarity	A clear sequence runs measure-against-ten-standards → escalation triggers → remedial hierarchy → findings table → tiered verdict → explicit Block/Approve decision, with the ten standards acting as a checklist and the Block/Approve criteria as explicit validation gates, matching the 'clear sequence with explicit validation steps; checklists' anchor.	3 / 3
Progressive Disclosure	The body is well-signaled and one level deep — it repeatedly points to [STANDARDS.md](STANDARDS.md) for the full rule catalog — but STANDARDS.md does not exist in the bundle (no references/ dir and no STANDARDS.md at the skill root), so the signaled navigation is a dead link; this falls short of the level-3 'easy navigation' anchor and lands at 'some structure but could be better organized.'	2 / 3
	Total	11 / 12 Passed

Description

57%

Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.

The description is specific and distinctive but omits an explicit 'Use when...' trigger clause and packs its best natural keywords into the triggers field rather than the description itself. Adding a usage clause and surfacing a couple of natural trigger phrases would lift completeness and trigger quality.

Suggestions

Append an explicit 'Use when reviewing animation or motion code, or when the user mentions easing, transitions, or motion craft.' clause to satisfy the 'when' half of completeness.

Fold one or two natural trigger phrases (e.g. 'animation review', 'motion review') into the description text so trigger-term quality is not solely carried by the triggers field.

Optionally name a second concrete action (e.g. 'flags regressions and proposes GPU-friendly fixes') to move specificity from domain-plus-one-action to multiple concrete actions.

Dimension	Reasoning	Score
Specificity	Quotes 'Reviews animation and motion code against a high craft bar' — names the domain and a single action (reviewing), but lists no multiple concrete operations, matching the 'names domain and some actions, but not comprehensive' anchor rather than the multi-action level 3.	2 / 3
Completeness	It states what the skill does ('Reviews animation and motion code...') but gives no 'Use when...' clause in the description; per the guidelines a missing explicit trigger clause caps completeness at 2, and it is not the level-1 case because the 'what' is clearly stated.	2 / 3
Trigger Term Quality	The description offers 'animation and motion code' as natural terms, but the richer natural triggers ('review animations', 'motion review', 'audit animations') live only in the separate triggers field, not the description text, so coverage is partial rather than the full level-3 set.	2 / 3
Distinctiveness Conflict Risk	The niche is sharply scoped to 'animation and motion code' review with an explicit 'decline general code' posture, making it clearly distinguishable and unlikely to trigger for the wrong skill, matching the 'clear niche with distinct triggers' anchor.	3 / 3
	Total	9 / 12 Passed

Validation

87%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 14 / 16 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning
relative_links	Relative link issues: 3 missing	Warning

	Total	14 / 16 Passed

Repository: nexu-io/open-design
Path: skills/review-animations/SKILL.md
Commit: a2ba3ee

Reviewed: about 13 hours ago

Table of Contents

Discovery Implementation Validation

Is this your skill?

If you maintain this skill, you can claim it as your own. Once claimed, you can manage eval scenarios, bundle related skills, attach documentation or rules, and ensure cross-agent compatibility.