animation-vocabulary

Reverse-lookup glossary that turns a vague description of a web animation or motion effect into its exact term ("the bouncy thing when a popover opens" → Pop in; "the iOS rubber-band scroll" → Rubber-banding). Use when the user asks "what's it called when…", or describes a motion effect without knowing its name and wants the right word to prompt an AI or designer with. For naming an effect, not designing or building one.

Quality

78%

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/animation-vocabulary/SKILL.md

Quality

Content

56%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 well-organized, actionable, and follows a clear single-purpose workflow with good worked examples, but it is let down by an oversized inlined glossary that re-explains many basic concepts and ignores progressive disclosure by not splitting the reference content into a separate file. Conciseness and progressive disclosure are the weakest dimensions.

Suggestions

Move the ~110-entry Glossary into a separate references file (e.g. references/glossary.md) and have SKILL.md point to it one level deep, keeping only the Quick Start, Instructions, and Examples inline.

Trim or remove glossary entries that restate concepts Claude already knows (e.g. Easing, Keyframes, Duration, Translate, Scale) and keep only terms whose specific definition here is authoritative.

Add a brief verification cue for the 'when nothing matches' case, e.g. re-confirming against the glossary before declaring an approximation, to give the workflow a light feedback loop.

Dimension	Reasoning	Score
Conciseness	The glossary section is large (~110 definitions across 11 categories) and a portion restates well-known animation concepts Claude already knows (e.g. 'Easing — The rate at which an animation speeds up or slows down', 'Keyframes', 'Duration'); while each entry is terse, the aggregate re-teaches fundamentals rather than only adding what Claude lacks.	3 / 5
Actionability	The Quick Start gives an explicit output format and the three worked examples are concrete and copy-ready, plus the numbered Instructions tell Claude exactly how to read intent, quote verbatim, and disambiguate — only minor gaps remain (e.g. no guidance on handling truly novel effects beyond 'say so').	4 / 5
Workflow Clarity	The six-step Instructions sequence the task clearly (read for intent → quote verbatim → disambiguate → approximate → stay in glossary → keep tight), and this is a simple single-purpose skill so the simple-skill exception applies; it stops short of a 5 only because there are no explicit verification/check feedback loops, though the task is non-destructive so none are required.	4 / 5
Progressive Disclosure	There are no bundle files (references/scripts/assets absent) yet the entire ~110-entry glossary is inlined directly in SKILL.md rather than split into a referenced vocabulary file; the body itself notes it 'mirroring the project's /vocabulary page; keep the two in sync', indicating the bulk reference content clearly belongs in a separate file but is monolithically inlined.	2 / 5
	Total	13 / 20 Passed

Description

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

The description is exemplary: it states the skill's purpose concretely, gives vivid worked examples, supplies explicit natural-language triggers, and draws a clear boundary against adjacent skills. All four dimensions land at the top of the scale.

Dimension	Reasoning	Score
Specificity	The description states multiple concrete actions — 'turns a vague description ... into its exact term', 'Reverse-lookup glossary' — and the two worked examples concretely demonstrate the input→output behavior, giving comprehensive coverage of what the skill does.	5 / 5
Completeness	It explicitly answers both 'what' (reverse-lookup glossary mapping vague descriptions to exact terms) and 'when' (Use when the user asks 'what's it called when…' or describes a motion effect without knowing its name), plus a clear boundary clause ('For naming an effect, not designing or building one').	5 / 5
Trigger Term Quality	It captures the exact natural phrases users say ('what's it called when…', 'the bouncy thing when a popover opens', 'the iOS rubber-band scroll') plus synonyms like 'motion effect', 'animation', and the output framing ('prompt an AI or designer'), giving comprehensive coverage of natural terms.	5 / 5
Distinctiveness Conflict Risk	The niche is sharply defined — naming motion effects rather than building them — and the distinctive trigger phrasing ('what's it called when…') makes overlap with animation-building or design skills minimal.	5 / 5
	Total	20 / 20 Passed

Validation

100%

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

Validation for skill structure

No warnings or errors.

Repository: emilkowalski/skills
Path: skills/animation-vocabulary/SKILL.md
Commit: 78761e1

Reviewed: 4 days 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.