CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

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

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

SKILL.md
Quality
Evals
Security

Quality

Content

92%Weight 40%Scale 1-5

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

An exceptionally tight, high-signal review skill: lean prose, concrete values and code, a clearly sequenced review workflow, and an explicit output contract. Its one real defect is that all detail is delegated to a STANDARDS.md that is not present in the bundle, leaving the promised rule catalog unreachable.

Suggestions

Bundle STANDARDS.md with the skill (or correct its path) so the three in-body references resolve — the body explicitly directs the reviewer to pull exact curves, durations, and spring configs from it.

Until the file exists, inline a few of the most-needed exact values (the canonical ease-out cubic-bezier, per-element duration budgets, default spring config) so findings don't stall when STANDARDS.md is absent.

Verify the link path: the bundle has no references/ directory, so a relative STANDARDS.md link only works if the file is placed alongside SKILL.md.

DimensionReasoningScore

Conciseness

The body is dense and assumes Claude's competence throughout — "Animate `transform` and `opacity` only", "scale(0.9–0.97) + opacity", "@media (hover: hover) and (pointer: fine)" — with zero padding and no explanation of basics like what CSS transitions or Framer Motion are. The overlap between the Ten Standards and the Escalation Triggers is deliberate cross-referencing for flag-on-sight emphasis, not verbosity. Re-read anchor 4 ("minor instances of over-explanation that could be trimmed"): nothing here reads as over-explanation to trim, so 5 is the better fit.

5 / 5

Actionability

Guidance is fully concrete and executable for a review skill: exact thresholds ("stay under 300ms", "scale(0.9–0.97)"), exact CSS ("transition: transform 200ms ease-out", "transform-origin: center" flags), a copy-paste-ready before/after findings table with exact replacement code, a numbered remedial hierarchy with concrete fixes, and an explicit two-part output template with Block/Approve criteria. Anchor 5 ("specific examples cover the common cases") matches; anchor 4's "minor gaps" doesn't apply.

5 / 5

Workflow Clarity

The review process is unambiguously sequenced: measure every animation against the Ten Standards → flag the Escalation Triggers "on sight" → propose fixes via the ordered 9-step "Remedial Preference Hierarchy" → emit the Required Output Format (findings table, then verdict) → close with an explicit Block/Approve decision with named conditions. This is a single-purpose, read-only skill (no destructive/batch ops, so no validation cap applies), and per the rubric's simple-skill guidance the unambiguous single action scores 5. Anchor 4's "minor validation gaps" doesn't fit — the Block/Approve criteria are explicit.

5 / 5

Progressive Disclosure

The split design is right — SKILL.md is an overview and precise values ("easing curves, duration tables, spring config") are deferred to STANDARDS.md with clear load signals ("Load it whenever a finding needs a precise value or citation"), which alone would fit anchor 4–5. However, scoring against the actual bundle structure per the judging guidelines: there are no references/, scripts/, or assets/ directories and no STANDARDS.md anywhere in the bundle — every one of the three links is a broken path, and the load-bearing instruction "pull the exact one from STANDARDS.md rather than approximating" cannot be executed. A wholly missing referenced file is more than anchor 4's "minor organization gaps", so the score lands at 3.

3 / 5

Total

18

/

20

Passed

Description

61%Weight 40%Scale 1-5

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

A specific, correctly third-person description with good domain keyword coverage and a clear niche, whose main gap is the missing 'when': there is no explicit trigger guidance telling Claude (or a user) when this skill should be invoked. A single "Use when..." clause naming animation, motion, or transition review would lift it substantially.

Suggestions

Add an explicit trigger clause, e.g. "Use when reviewing animation, motion, or transition code in a diff or PR" — its absence caps completeness at 3.

Fold in a couple more natural trigger terms users actually say ("transitions", "easing", "springs", "Framer Motion") to move trigger coverage from good to comprehensive.

Optionally name one or two more concrete actions (e.g. "flags regressions in easing, duration, origin, and interruptibility") to sharpen specificity beyond a single verb.

DimensionReasoningScore

Specificity

"Reviews animation and motion code against a high craft bar" names the domain and one concrete action (reviews), with the remainder ("derived from Emil Kowalski's design engineering philosophy. Default to flagging; approval is earned.") describing posture, not further capabilities. This matches anchor 3 ("Names domain and 1-2 concrete actions, but not comprehensive"): it is more concrete than anchor 2's "Processes PDF files" but does not list the several distinct actions anchor 4 requires.

3 / 5

Completeness

The "what" is clear and concrete — "Reviews animation and motion code against a high craft bar" — but there is no "Use when..." clause or equivalent trigger guidance anywhere in the description ("Default to flagging; approval is earned" describes verdict posture, not when to invoke). Per the rubric's cap rule, a missing 'when' caps completeness at 3, exactly matching anchor 3 ("Has a clear 'what' but 'when' is missing or only weakly implied").

3 / 5

Trigger Term Quality

"animation and motion code" supplies the two terms users would most naturally say in this domain, plus "design engineering" as a secondary hook — better coverage than anchor 3's single-term example ("Works with PDF files"). It falls just short of anchor 5's comprehensive synonym coverage because common variations like "transitions", "easing", or "springs" are absent, fitting anchor 4 ("Good keyword coverage; a few natural terms missing").

4 / 5

Distinctiveness Conflict Risk

"animation and motion code" carves out a clear niche distinct from general document or data skills, fitting anchor 4 ("Mostly distinct; minor overlap risk with closely related skills") — the residual overlap is with general code-review skills, since a request to "review this component's animation changes" could plausibly match either. It is not anchor 5 because "reviews ... code" still competes with any generic review skill on code-review requests.

4 / 5

Total

14

/

20

Passed

Validation

93%

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

CriteriaDescriptionResult

relative_links

Relative link issues: 3 missing

Warning

Total

15

/

16

Passed

Repository

jscraik/websites

Path

.codex/skills/review-animations/SKILL.md

Reviewed

Table of Contents

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.