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 ./.agents/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 body is lean, highly actionable, and clearly sequenced with explicit verdict criteria, but its progressive-disclosure promise is undermined by a referenced STANDARDS.md that is not present in the bundle.

Suggestions

Provide the missing STANDARDS.md bundle file so the referenced easing curves, duration tables, spring configs, and per-element budgets are actually loadable.

If STANDARDS.md is intentionally absent, inline the essential values or remove the "pull the exact one from STANDARDS.md" instructions to avoid a broken reference.

Dimension	Reasoning	Score
Conciseness	The body is dense and domain-specific with no generic concept padding (it never explains what transitions, easing, or springs are), assuming Claude's competence so that nearly every token carries a craft rule.	3 / 3
Actionability	Guidance is concrete and copy-paste ready: exact values (sub-300ms, scale(0.9-0.97)), named anti-patterns (transition: all, scale(0), ease-in, transform-origin: center), a remedial hierarchy, and a Before/After/Why table with specific code examples.	3 / 3
Workflow Clarity	The review process is clearly sequenced (ten standards -> escalation triggers -> remedial hierarchy -> findings table -> verdict) with explicit Block/Approve decision gates; being a single-purpose review skill, it needs no destructive-op feedback loop.	3 / 3
Progressive Disclosure	The intent is good (overview in SKILL.md, one-level-deep [STANDARDS.md](STANDARDS.md) signaled for exact values), but STANDARDS.md does not exist in the bundle, so the promised reference is broken and navigation fails.	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 third-person and carves out a clear, distinct niche, but it is capped by the absence of any explicit "Use when..." trigger guidance and a thin spread of natural keyword variations.

Suggestions

Add an explicit trigger clause, e.g. "Use when reviewing animation, transitions, or motion code (CSS transitions, Framer Motion, WAAPI, gesture-driven motion)."

Broaden trigger terms to include common user phrasings such as "transitions", "easing", "CSS animations", and "Framer Motion".

Dimension	Reasoning	Score
Specificity	Names the domain ("animation and motion code") and one concrete action ("Reviews") but does not enumerate multiple specific actions, matching the anchor that lists a domain and some actions without being comprehensive.	2 / 3
Completeness	It clearly states what the skill does ("Reviews animation and motion code against a high craft bar") but provides no "Use when..." or equivalent explicit trigger guidance, which per the judging guidelines caps completeness at 2.	2 / 3
Trigger Term Quality	Contains the core natural terms "animation" and "motion" a user would say, but misses common variations like "transitions", "easing", "CSS animations", or "Framer Motion", fitting the anchor of some relevant keywords with missing variations.	2 / 3
Distinctiveness Conflict Risk	The animation/motion-code review niche is sharply specific and clearly distinct from general code review, so it is unlikely to trigger for the wrong skill.	3 / 3
	Total	9 / 12 Passed

Validation

93%

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 — 15 / 16 Passed

Validation for skill structure

Criteria	Description	Result
relative_links	Relative link issues: 3 missing	Warning

	Total	15 / 16 Passed

Repository: 1weiho/open-slide
Path: .agents/skills/review-animations/SKILL.md
Commit: 35dc46c

Reviewed: about 11 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.