motion-ui

Production-ready UI motion system for React/Next.js. Use when implementing animations, transitions, or motion patterns.

Quality

72%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No known issues

Fix and improve this skill with Tessl

tessl review fix ./skills/motion-ui/SKILL.md

Quality

Content

77%

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

The content is highly actionable with executable examples and clear checklists, but it is a long monolithic file that repeats some guidance and would benefit from splitting detailed material into referenced bundle files.

Suggestions

Split the full Modal example and the Advanced Patterns into separate reference files (e.g. MODAL.md, PATTERNS.md) linked from a concise overview, improving progressive disclosure.

De-duplicate the reduced-motion FadeIn example that appears in both the Accessibility section and the Examples section.

Remove or merge the "Philosophy" and "Final Rule" sections, which restate the existing When-to-Use / Avoid guidance.

Dimension	Reasoning	Score
Conciseness	The body is mostly lean with tokens, tables, and code, but it restates guidance (the reduced-motion FadeIn example appears twice; "Philosophy" and "Final Rule" repeat the When-to-Use/Avoid messaging) and could be tightened.	2 / 3
Actionability	It provides fully executable, copy-paste-ready code (motionTokens, Modal, Button, Parallax) plus scenario-to-pattern tables, giving concrete guidance rather than vague direction.	3 / 3
Workflow Clarity	Sections are clearly sequenced (Installation -> Version -> Tokens -> Patterns -> QA) with explicit Debugging and QA checklists; no destructive or batch operations are present that would require validation feedback loops.	3 / 3
Progressive Disclosure	The file is well-organized into sections, but at 577 lines it is monolithic with no bundle files or external references, and substantial content (the full Modal example, Advanced Patterns) that could live in separate reference files is inline.	2 / 3
	Total	10 / 12 Passed

Description

67%

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 cleanly answers both what the skill is and when to use it with an explicit "Use when" clause, but its capability list and trigger terms are only moderately specific and could overlap with sibling animation skills.

Suggestions

Add concrete actions to the capability clause, e.g. "Define motion tokens, implement hover/scroll/layout animations, and handle reduced-motion accessibility."

Broaden trigger terms with common user phrasings like "hover effects, page transitions, scroll-linked animation, or reduced motion."

Tighten the niche by mentioning the Motion/Framer Motion library explicitly to reduce overlap with generic CSS animation skills.

Dimension	Reasoning	Score
Specificity	"Production-ready UI motion system for React/Next.js" names the domain and "animations, transitions, or motion patterns" implies some actions, but it does not list multiple distinct concrete actions like the level-3 anchor requires.	2 / 3
Completeness	It explicitly states what ("Production-ready UI motion system for React/Next.js") and when via the explicit "Use when implementing animations, transitions, or motion patterns" trigger clause, satisfying both halves.	3 / 3
Trigger Term Quality	"implementing animations, transitions, or motion patterns" includes natural terms a user might say, but misses common variations such as hover effects, page transitions, or reduced motion, so coverage is partial.	2 / 3
Distinctiveness Conflict Risk	The React/Next.js scope gives it a niche, but the trigger terms (animations, transitions, motion patterns) are generic enough to overlap with a generic CSS-animation or Framer Motion skill.	2 / 3
	Total	9 / 12 Passed

Validation

87%

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

Validation for skill structure

Criteria	Description	Result
skill_md_line_count	SKILL.md is long (577 lines); consider splitting into references/ and linking	Warning
metadata_version	'metadata.version' is missing	Warning

	Total	14 / 16 Passed

Repository: affaan-m/ECC
Commit: 754b8dd

Reviewed: 3 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.