CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

12-principles-of-animation

Apply Disney's 12 animation principles to web interfaces. Use when implementing motion, reviewing animation quality, designing micro-interactions, or making UI feel alive. Triggers on tasks involving CSS animations, transitions, motion libraries, easing curves, springs, or UX feedback.

Quality

79%

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 ./.agents/skills/04-develop/01-ui-skills-dot-com/12-principles-of-animation/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

60%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.

The body is a well-organized, readable reference for applying animation principles to UI, with a few genuinely concrete rules. Its main weaknesses are duplication between the overview table and the per-principle sections, and a lack of executable examples (no CSS/snippet demonstrations) for a domain that is inherently code-centric.

Suggestions

Remove the duplication between the Principles Overview table and the Quick Reference sections — keep one as the summary and let the other carry the applied guidance.

Add small executable snippets for the most actionable principles, e.g., a cubic-bezier example for ease-out entrances or a spring config for overshoot-and-settle.

Turn the timing guidance into a concrete reusable timing scale (e.g., 150ms/200ms/300ms tokens) so 'define timing scales early, reuse everywhere' becomes directly actionable.

DimensionReasoningScore

Conciseness

Writing is mostly tight, but the Principles Overview table duplicates the Quick Reference sections (e.g., 'Use springs for organic overshoot-and-settle' vs 'Springs add organic overshoot-and-settle that easing curves can't replicate') and 'When to Apply' repeats the description — unnecessary duplication that fits anchor 3's 'could be tightened'.

3 / 5

Actionability

Some concrete rules exist (the 300ms timing budget, the ease-out/ease-in/ease-in-out mapping, CSS 'perspective'), but there are no executable code examples and several principles remain abstract ('The sum of all techniques applied with care and taste'), matching anchor 3's 'concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The usage flow is clear (When to Apply → overview table → per-principle guidance → Key Guidelines) and this is a reference skill with no destructive or batch operations requiring validation, but there is no sequenced process for, say, reviewing animation quality — anchor 4 rather than 5.

4 / 5

Progressive Disclosure

A single cohesive, well-sectioned file with clearly labeled one-level-deep external links and easy header navigation; the table-vs-sections duplication is a minor organization gap that keeps it at anchor 4 rather than 5.

4 / 5

Total

14

/

20

Passed

Description

87%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 strong description that clearly states what the skill does and when to use it, with a rich set of domain-specific trigger terms. It is highly distinctive and unlikely to fire for the wrong skill; only minor gains are available from tighter capability phrasing and a few more natural synonyms.

DimensionReasoningScore

Specificity

Lists several specific applications — 'implementing motion, reviewing animation quality, designing micro-interactions' — but 'making UI feel alive' is soft and the coverage of what the skill does has minor gaps, matching anchor 4 rather than the comprehensive anchor 5.

4 / 5

Completeness

Explicitly answers both 'what' ('Apply Disney's 12 animation principles to web interfaces') and 'when' ('Use when implementing motion... Triggers on tasks involving CSS animations...') with concrete trigger phrases, cleanly matching anchor 5.

5 / 5

Trigger Term Quality

Good natural keyword coverage ('CSS animations, transitions, motion libraries, easing curves, springs, UX feedback, micro-interactions'), but common variations users might say — 'hover effects', 'loading states', or named libraries like Framer Motion — are missing, so it fits anchor 4 rather than the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

A clear niche — Disney's 12 animation principles applied to web UI — with distinct motion-specific triggers (easing curves, springs, micro-interactions) and minimal realistic conflict with other skills, matching anchor 5; it is more distinct than anchor 4's 'minor overlap risk with closely related skills'.

5 / 5

Total

18

/

20

Passed

Validation

100%

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

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

marchatton/agent-skills

Path

.agents/skills/04-develop/01-ui-skills-dot-com/12-principles-of-animation/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.