CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

animations

Authors performant CSS-first web animations and picks the right feedback for an interaction — transitions, View Transitions, scroll-driven motion, Motion for React, reduced motion, and perceived performance. Triggers on "animate this", "hover effect", "feel faster", "skeleton loader", "/animations".

Quality

78%

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 ./skills/design/animations/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

66%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-architected index: crisp principles, a decision table, gated phases with validation and a bounded feedback loop, and a Definition of Done. Its fatal flaw in this bundle is that the progressive-disclosure chain is broken — almost every referenced rule/template file is absent, so the thin-index design points at nothing. Secondary issues are duplicated file-link tables and verbose 7.5/7.6 cells.

Suggestions

Ship the referenced files: the entire `rules/` directory (17+ files), `templates/`, and `lens.md` are missing from the bundle, so nearly all links in the decision flow, workflow table, and required-reading table dead-end.

Merge the "Required Reading by Phase" table into the Workflow table — both repeat the same phase → rule-file mapping, doubling the link maintenance surface.

Compress the Phase 7.5 and 7.6 cells to one-line pointers to `rules/record-and-iterate.md`, since the cells currently restate that file's full procedure.

DimensionReasoningScore

Conciseness

The body is high-signal and opinionated ("Animate `transform`, `opacity`, and `filter` only", "150–500 ms band for UI") with no concept explanations Claude already knows, but it could be tightened: the "Required Reading by Phase" table repeats the same rule-file links already given in the Workflow table, and the Phase 7.5/7.6 cells spell out full procedures ("invoke `Skill(\"screencast\")` twice — once with `\"reducedMotion\": false\`, once with `true`...") that duplicate [`rules/record-and-iterate.md`] they also link. Mostly efficient with some duplication — anchor 3, not 4's "minor instances".

3 / 5

Actionability

Concrete, executable direction throughout: a first-match-wins decision table mapping signals to exact tools ("`animation-timeline: scroll()` / `view()`", "`interpolate-size: allow-keywords`"), numeric duration bands, a runnable command ("`node ${CLAUDE_SKILL_DIR}/scripts/is-motion-diff.mjs`" — the script exists), and a Definition of Done checklist. Not 5 because copy-paste code lives in [`references/recipes.md`] and [`templates/`] and most deep guidance sits behind rule files that are not present in the bundle, leaving minor gaps for the common cases.

4 / 5

Workflow Clarity

The phased workflow (A, B, 0–7.6) is clearly sequenced with an explicit gate per phase ("Animated property is `transform`, `opacity`, or `filter`. If not, justify with a layout-thrash measurement"), measurement validation (Phase 7: "no purple Layout / green Paint bars"), and a real feedback loop with a bounded retry and escalation path ("apply the fix and return to Phase 7.5. Cap the loop at 3 iterations — escalate via `Skill(\"confidence\", analysis)` on the 4th"), plus a closing checklist. Matches the anchor-5 example pattern of validate → fix → re-validate.

5 / 5

Progressive Disclosure

The index design is exemplary on paper — "This `SKILL.md` is a thin index... Detailed rules live in `rules/*.md` and load on demand", one level deep, clearly labeled — but scored against the actual bundle, nearly every referenced path is dead: `rules/` (17+ files), `templates/`, and `lens.md` do not exist; only `references/recipes.md` and `scripts/is-motion-diff.mjs` are present, and recipes.md itself links to the missing `../rules/state-choreography.md`. Navigation dead-ends on first use, which lands below the midpoint; not 1 because the structure is well organized, not a monolithic wall.

2 / 5

Total

14

/

20

Passed

Description

83%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: concrete capability statement, explicit trigger phrases, and a distinct web-animation niche. The main gaps are modest — only two action verbs, and a few natural trigger variations (janky, 60fps, microinteraction) are missing. Minor overlap risk with perceived-performance and native-motion skills keeps distinctiveness at 4.

Suggestions

Add one or two more concrete action verbs (e.g. 'reviews and debugs existing animations for jank') so the capability list matches the body's full scope.

Add natural trigger variations users say for motion problems — "janky", "laggy", "make it smooth", "60fps", "microinteraction" — to the trigger list.

DimensionReasoningScore

Specificity

"Authors performant CSS-first web animations and picks the right feedback for an interaction — transitions, View Transitions, scroll-driven motion, Motion for React, reduced motion, and perceived performance" names two concrete verbs plus a broad, specific technology scope. Not 5 because only two actions are stated (author, pick feedback) while "reduced motion" and "perceived performance" are domains rather than actions, and capabilities the body covers (review, debug, measure animations) are absent; well above the 1–2-action anchor at 3.

4 / 5

Completeness

Explicitly answers what ("Authors performant CSS-first web animations and picks the right feedback for an interaction") and when ("Triggers on 'animate this', 'hover effect', 'feel faster', 'skeleton loader', '/animations'"), matching the anchor-5 pattern of concrete trigger phrases attached to a clear capability statement. A weaker 'when' would drop it to 4, but the trigger list is explicit.

5 / 5

Trigger Term Quality

"Triggers on 'animate this', 'hover effect', 'feel faster', 'skeleton loader', '/animations'" are phrases a user would naturally say. Not 5 because common variations are missing — "janky", "laggy", "smooth", "60fps", "microinteraction", "add a transition"; comfortably above anchor 3 since several natural phrases, not generic keywords, are present.

4 / 5

Distinctiveness Conflict Risk

"CSS-first web animations" carves a clear niche with animation-specific triggers. Not 5: "skeleton loader" and "feel faster" are perceived-performance terms that could route performance-tuning queries here, and the description does not distinguish web from a sibling React Native motion skill (the body has to redirect), leaving minor overlap with closely related skills; far above the generic anchors at 2–3.

4 / 5

Total

17

/

20

Passed

Validation

81%

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

Validation — 13 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_field

'metadata' should map string keys to string values

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

relative_links

Relative link issues: 66 missing, 3 suspicious

Warning

Total

13

/

16

Passed

Repository

mthines/agent-skills

Path

skills/design/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.