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

90%

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

87%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is concise, well-structured, and gives concrete actionable motion guidance without over-explaining. Its main gap is the lack of explicit validation/verification steps in the workflow.

Suggestions

Add a final verification step to the Workflow, e.g., 'Confirm each automatic or scroll-linked motion has a working prefers-reduced-motion fallback before finishing.'

Include a short checkpoint to re-inspect the artifact after adding motion to ensure copy, data, and layout intent remain intact (turning step 6 from a constraint into an explicit verify step).

Optionally provide one minimal executable snippet (a transform/opacity entry reveal with a prefers-reduced-motion media query) to make the implementation guidance copy-paste ready.

Dimension	Reasoning	Score
Conciseness	The body is lean and assumes Claude's competence — it does not explain what transform/opacity, CSS keyframes, or prefers-reduced-motion are, and every line carries actionable guidance with no padding.	3 / 3
Actionability	Guidance is concrete and specific ("Prefer transform and opacity. Avoid animating layout properties such as top, left, width, or height", "140-220ms for most controls", "Always clean up observers, timers, and animation instances"); as an instruction-only skill, absent code is not penalized when guidance is this actionable.	3 / 3
Workflow Clarity	The numbered Workflow (steps 1-6) is clearly sequenced, but there are no explicit validation or verification checkpoints (e.g., confirming the reduced-motion fallback works or re-checking the artifact after motion is added), matching the anchor for sequence-present-but-checkpoints-implicit.	2 / 3
Progressive Disclosure	The skill is under 50 lines with no bundle files and no nested references, organized into clean Workflow / Motion Rules / Implementation Notes sections, which earns a 3 for a simple skill with no need for external references.	3 / 3
	Total	11 / 12 Passed

Description

92%

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 strong: concrete actions, explicit when-guidance, and good natural trigger coverage. The only soft spot is moderate overlap risk between its generic motion triggers and broader animation skills.

Dimension	Reasoning	Score
Specificity	The description lists multiple concrete action types — "add tasteful micro-interactions, state transitions, and page motion" — matching the anchor for listing several specific concrete actions rather than a single vague domain.	3 / 3
Completeness	It answers both what ("add tasteful micro-interactions, state transitions, and page motion with product-grade restraint") and when ("Use after an interface exists"), an explicit trigger clause, so it is not capped at 2.	3 / 3
Trigger Term Quality	The triggers cover natural user phrasing across variations ("motion polish", "micro interaction", "tasteful animation", "emil kowalski", "动效润色"), giving good coverage of terms a user would actually say.	3 / 3
Distinctiveness Conflict Risk	The "emil kowalski" attribution is distinctive, but generic motion terms like "motion polish" and "tasteful animation" could overlap with general animation or GSAP skills referenced in the body, so it is not a fully unconflicted niche.	2 / 3
	Total	11 / 12 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: f2760fd

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