CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

framer-motion

Use when implementing Disney's 12 animation principles with Framer Motion in React applications

Quality

80%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./.claude/skills/framer-motion/SKILL.md

The canonical home for this skill is framer-motion in calesthio/OpenMontage

SKILL.md
Quality
Evals
Security

Quality

Content

76%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.

A lean, highly actionable pattern catalog with excellent token efficiency and concrete executable snippets. Its weaknesses are the absence of any selecting/combining workflow and a modest structure gap where reference-quality material (the features/API list) is inlined rather than split out.

Suggestions

Add a short 'choosing an approach' note (e.g., when to use springs vs. duration-based transitions, or how to combine principles) to give the catalog a decision workflow.

Move the 'Key Framer Motion Features' API listing into a references/ file (or make the stagger example self-contained by defining itemVariant) to tighten the main file.

DimensionReasoningScore

Conciseness

Each of the 12 principles is a header plus a minimal snippet, with terse purposeful comments ('// low damping = overshoot', '// hair', '// cape') and zero explanation of Framer Motion, React, or animation concepts Claude already knows. Lean and efficient; every token earns its place.

5 / 5

Actionability

Concrete, realistic JSX per principle (e.g., 'animate={{ scaleX: [1, 1.2, 1], scaleY: [1, 0.8, 1] }}' and 'whileHover={{ scale: 1.02, boxShadow: ... }}') with real prop values. Minor gaps keep it below fully copy-paste ready: the stagger example references an undefined 'itemVariant' and 'items.map(...)' without a complete component.

4 / 5

Workflow Clarity

The body is a well-numbered catalog of per-principle patterns, but there is no workflow: no guidance on choosing or combining principles, no sequencing, and the extra sections (Stagger Children, Key Features) appear without integration guidance. It sits at anchor 3 (organized structure present but process checkpoints absent); the under-50-line simple-skill exception does not apply to this ~180-line catalog, though no risky operations exist that would demand validation.

3 / 5

Progressive Disclosure

No bundle files exist and none are referenced, and the single file is flat and well-sectioned with no nested references. However, the inline 'Key Framer Motion Features' API listing and 180 lines of snippets are bulk material that a 5-star skill would split into a one-level-deep reference file; this matches anchor 4 (good structure, minor organization gaps).

4 / 5

Total

16

/

20

Passed

Description

73%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.

A concise, distinctive trigger with a well-named domain, but it is a single fused clause rather than a what-plus-when structure with concrete capability phrases. Adding explicit capability verbs (e.g., 'create page transitions, spring animations, gesture feedback') would raise specificity and completeness.

Suggestions

Add 2-3 concrete capability phrases (e.g., 'create page transitions, staggered lists, spring-based gesture animations') so the 'what' is explicit and not just a re-statement of the trigger.

Broaden trigger coverage with natural synonyms users would say, such as 'motion', 'transitions', 'spring animations', or 'React animation library'.

DimensionReasoningScore

Specificity

The description names the domain precisely ('Disney's 12 animation principles with Framer Motion in React applications') and one action ('implementing'), but lists no concrete capabilities such as page transitions, spring physics, or gesture animations. It matches anchor 3: domain plus 1-2 actions, not comprehensive.

3 / 5

Completeness

Both what ('implementing Disney's 12 animation principles with Framer Motion') and when ('Use when ... in React applications') are present, but they are fused into a single clause with no separate capability statement. This matches anchor 4 (both present, could be more explicit) rather than the fully separated two-part structure of anchor 5.

4 / 5

Trigger Term Quality

Natural user phrases are present ('animation principles', 'Framer Motion', 'React', 'animation'), giving good keyword coverage. A few natural terms users would say are missing (e.g., 'motion', 'transitions', 'spring animations'), so it falls just short of the comprehensive-synonym coverage of anchor 5.

4 / 5

Distinctiveness Conflict Risk

Naming a specific library ('Framer Motion') and framework ('React') gives a clear niche with distinct triggers and minimal conflict risk with other skills, matching anchor 5.

5 / 5

Total

16

/

20

Passed

Validation

100%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

calesthio/OpenMontage

Path

.claude/skills/framer-motion/SKILL.md

Reviewed

Table of Contents

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.