emilkowalski-motion

Motion-design follow-up skill inspired by Emil Kowalski's animation guidance. Use after an interface exists to add tasteful micro-interactions, state transitions, and page motion with product-grade restraint.

Quality

76%

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/emilkowalski-motion/SKILL.md

Quality

Content

86%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 content is a tight, well-structured instruction skill that respects the context budget and gives concrete, opinionated motion rules without over-explaining fundamentals. The only meaningful gap is the absence of a small executable CSS/code example to make the guidance copy-paste ready.

Suggestions

Add one short CSS snippet showing a canonical entry reveal with a prefers-reduced-motion fallback to lift actionability to copy-paste ready.

Optional: surface the trigger keywords from the frontmatter as a short 'Use when...' line in the body so the workflow context matches invocation.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence: it never explains what transforms, easings, or prefers-reduced-motion are, and every line carries actionable guidance with no padding.	5 / 5
Actionability	Guidance is concrete and specific (140-220ms durations, prefer transform/opacity, avoid top/left/width/height, prefers-reduced-motion fallbacks), but there are no copy-paste code or CSS snippets to anchor the common cases.	4 / 5
Workflow Clarity	A clear six-step workflow sequences the work and the task is additive/non-destructive (it explicitly preserves layout), so the destructive-operation validation cap does not apply; it falls just short of 5 only because explicit checkpoints are not called out.	4 / 5
Progressive Disclosure	Under 50 lines with no bundle files, the skill is cleanly split into well-organized sections (Workflow, Motion Rules, Implementation Notes), satisfying the simple-skill exception for progressive disclosure.	5 / 5
	Total	18 / 20 Passed

Description

67%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 concise, domain-specific, and answers both what the skill does and when to use it, with a distinct identity tied to a named style. Its main weakness is that natural trigger keywords are weaker inside the description itself than in the separate triggers list.

Suggestions

Fold one or two natural trigger phrases (e.g. 'motion polish', 'micro-interaction animation') into the description so the when-clause matches how users actually phrase the request.

Add the artifact context to the when-clause (e.g. 'Use after a web interface exists') to sharpen distinctiveness from generic animation skills.

Replace the abstract qualifier 'tasteful' with a concrete restraint cue (e.g. 'restrained, purposeful motion') to strengthen specificity.

Dimension	Reasoning	Score
Specificity	The description lists several concrete actions ('micro-interactions, state transitions, and page motion') tied to a clear domain, but stops short of fully comprehensive coverage and leans on the mildly abstract qualifier 'tasteful'.	4 / 5
Completeness	It clearly states both the 'what' (micro-interactions, state transitions, page motion) and an explicit 'when' ('Use after an interface exists'), though the 'when' lacks concrete trigger phrases users would say.	4 / 5
Trigger Term Quality	Natural motion keywords ('micro-interactions', 'state transitions', 'page motion') appear but the richer trigger variations (e.g. 'animation', 'motion polish') live in a separate triggers field rather than the description itself, leaving common synonyms out of the description text.	3 / 5
Distinctiveness Conflict Risk	Tying the skill to Emil Kowalski's animation guidance carves a clear niche with minimal conflict risk, though it could still lightly overlap with generic animation/motion skills.	4 / 5
	Total	15 / 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
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	15 / 16 Passed

Repository: nexu-io/open-design
Path: skills/emilkowalski-motion/SKILL.md
Commit: 1a7a23d

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