transitions-polish

Polish and refine existing motion against the transitions.dev motion-token scale — duration, distance, scale, blur, and easing — plus the rules for WHEN each token applies (open/close asymmetry, hover-in vs hover-out, stagger offsets, and intent delays). An add-on to the transitions-dev skill, focused on tuning what already animates rather than adding new transitions. Use when the user asks to "polish my transitions", "refine the motion", "tune the timing / easing", "make the animation feel better / less janky", "tighten the durations", "fix the stagger", "align to the motion tokens", "audit the motion", "review my animations", "scan for ad-hoc transitions", "tokenize my animations", or runs the commands transitions review or transitions polish. Also drives the Refine panel's Small refinement feature. Triggers on "motion polish", "transition polish", "refine motion", "timing feels off", "too slow / too fast", "stagger", "delay", "open close timing", "hover in out".

Quality

85%

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

Quality

Content

71%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-structured and highly actionable, with dense token tables and clearly sequenced review/polish commands. Its main weakness is progressive disclosure: two referenced bundle files (_root.css, _refine-rules.md) are cited but do not exist in the skill bundle.

Suggestions

Add the missing ./_root.css file to the bundle (or a references/ dir) so the repeatedly-cited token definitions actually ship with the skill.

Add the missing ./_refine-rules.md file referenced by the Refine panel section, or remove that reference until the file exists.

Tighten the prose rules (e.g. the "Opening is an invitation" line) into pure directives to lift conciseness toward a 5.

Dimension	Reasoning	Score
Conciseness	Mostly lean and dense — token tables carry exact value/usage with no padding and assume Claude's CSS knowledge — but a few prose passages ("Opening is an invitation; closing should get out of the way") could be trimmed. Not a 5 due to minor over-explanation in the doctrine and rules prose.	4 / 5
Actionability	Provides concrete token tables with exact values/usages and two numbered commands with specific example output lines ("modal close: 300ms → var(--duration-quick) (150ms)"). Mostly executable guidance with only minor gaps; a 5 would need fuller copy-paste-ready snippets for the polish application itself.	4 / 5
Workflow Clarity	Both commands have explicit numbered sequences; transitions polish includes a confirmation-before-edit checkpoint and constraints ("Touch only the motion values being polished"). Not a 5 because validation/checkpoint guidance is partly implicit rather than an explicit validate-retry loop.	4 / 5
Progressive Disclosure	Section structure is clear, but the body references ./_root.css and ./_refine-rules.md which are not present in the bundle (no references/, scripts/, or assets/ directories exist), so the signaled references are broken. Broken/missing referenced files keep this below a 4.	3 / 5
	Total	15 / 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 concrete capabilities across five named dimensions, pairs them with higher-order usage rules, and provides an extensive set of natural trigger phrases and command names. It cleanly distinguishes itself from the related transitions-dev skill.

Dimension	Reasoning	Score
Specificity	Lists multiple concrete actions across all five motion-token dimensions ("duration, distance, scale, blur, and easing") plus the higher-order rules for when each applies, giving comprehensive coverage rather than vague language.	5 / 5
Completeness	Explicitly answers both what (polish/refine motion against the token scale across five dimensions and when-rules) and when (a long "Use when the user asks..." clause with concrete trigger phrases and command names).	5 / 5
Trigger Term Quality	Comprehensive natural phrases users would actually say ("polish my transitions", "tune the timing / easing", "make the animation feel better / less janky", "fix the stagger") plus command triggers, with broad synonym coverage.	5 / 5
Distinctiveness Conflict Risk	Occupies a clear niche (tuning existing motion) explicitly distinguished from the sibling transitions-dev skill ("focused on tuning what already animates rather than adding new transitions"), minimizing wrong-skill triggering.	5 / 5
	Total	20 / 20 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, 1 suspicious	Warning

	Total	15 / 16 Passed

Repository: Jakubantalik/transitions.dev
Path: skills/transitions-polish/SKILL.md
Commit: 0f8540f

Reviewed: ~21 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.