motion-advanced

Advanced motion patterns for React / Next.js — drag & drop, gestures, text animations, SVG path drawing, custom hooks, imperative sequences (useAnimate), loaders, and the full API decision tree. Requires motion-foundations.

Quality

80%

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-advanced/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.

A highly actionable, well-structured pattern catalog with strong decision guidance, held back by some repeated boilerplate across examples and a monolithic structure that makes no use of progressive disclosure despite its size.

Suggestions

Extract the larger code examples into files under references/ (e.g., references/examples.md) and link to them from the body to improve progressive disclosure and reduce inline token weight.

De-duplicate the visibilitychange-pause pattern by showing it once and referencing it from ShimmerSkeleton, PulseDot, and the End-to-End example rather than repeating the full listener block.

Move the drag-to-dismiss sheet to a single canonical location and have the End-to-End Example build on or reference it instead of restating it.

Dimension	Reasoning	Score
Conciseness	The body is mostly efficient and avoids explaining concepts Claude already knows, but it could be tightened: the drag-to-dismiss sheet recurs in both Code Examples and the End-to-End Example, and the visibilitychange-pause boilerplate is repeated across ShimmerSkeleton, PulseDot, and the End-to-End example.	2 / 3
Actionability	Every pattern ships as complete, import-bearing, copy-paste-ready TSX using shared tokens, plus scenario→API decision tables — fully executable guidance rather than pseudocode.	3 / 3
Workflow Clarity	Selection is clearly sequenced through the 'When to Activate' list and two decision tables (scenario→API, useSpring vs transition), and the End-to-End Example shows how to compose the patterns; no destructive/batch operations require validation checkpoints here.	3 / 3
Progressive Disclosure	Sections are well organized, but the skill is a single ~590-line monolithic file with no references/, scripts/, or assets/ bundle and no one-level-deep links to split out the large example catalog, so content that could be separate remains inline.	2 / 3
	Total	10 / 12 Passed

Description

82%

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 specific, well-scoped description with strong natural trigger terms and clear distinctiveness, weakened only by the absence of an explicit 'Use when...' clause that would have completed the trigger guidance.

Suggestions

Add an explicit 'Use when...' clause to the description (e.g., 'Use when the user needs drag-to-dismiss, swipe gestures, reorderable lists, SVG drawing, or imperative multi-step sequences beyond standard motion-patterns.') to lift completeness to 3.

Consider including a couple of common variation phrases users might say (e.g., 'swipe', 'reorder list', 'spinner') to broaden trigger coverage.

Dimension	Reasoning	Score
Specificity	Lists multiple specific concrete actions — 'drag & drop, gestures, text animations, SVG path drawing, custom hooks, imperative sequences (useAnimate), loaders, and the full API decision tree' — matching the top anchor.	3 / 3
Completeness	It clearly states what the skill does but has no explicit 'Use when...' trigger clause in the description itself; the 'when' is only implied, so per the guidelines completeness is capped at 2.	2 / 3
Trigger Term Quality	Natural user-facing terms are well covered: 'drag & drop', 'gestures', 'text animations', 'SVG path drawing', 'loaders' are phrases a user would actually say when needing these patterns.	3 / 3
Distinctiveness Conflict Risk	The 'Advanced motion patterns' niche, the explicit 'Requires motion-foundations' prerequisite, and scoping to patterns beyond motion-patterns make it clearly distinct and unlikely to trigger for the wrong skill.	3 / 3
	Total	11 / 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 (597 lines); consider splitting into references/ and linking	Warning
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	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.