CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

interaction-design

Design and implement microinteractions, motion design, transitions, and user feedback patterns. Use when adding polish to UI interactions, implementing loading states, or creating delightful user experiences.

Quality

78%

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 ./.agents/skills/04-develop/01-ui-skills-dot-com/interaction-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

71%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 well-organized, highly actionable pattern catalog whose code examples are nearly all executable and whose timing/easing reference adds real value. Weaknesses are the monolithic single-file structure with no progressive disclosure of advanced patterns, a couple of code gaps (undefined animate-ripple class, missing useState import), and prose sections that restate knowledge Claude already has.

Suggestions

Define the missing 'animate-ripple' keyframes in the CSS section (and add the useState import to RippleButton) so every example is copy-paste ready.

Split advanced patterns (gestures, page transitions, ripple) into references/ files and keep SKILL.md as an overview with one-level-deep links.

Trim or compress Core Principles / Best Practices / Common Issues into the pattern sections they govern to cut known-concept prose.

DimensionReasoningScore

Conciseness

The body is dominated by complete, uncommented code examples and a genuinely useful timing table/easing reference Claude would not recall precisely. The Core Principles, Best Practices, and Common Issues sections restate frontend knowledge Claude largely has, but each is brief — anchor 4 (efficient, minor over-explanation) rather than 3's 'some unnecessary explanation'.

4 / 5

Actionability

Nearly all examples are copy-paste executable (framer-motion button, toggle, page transition, swipe card, CSS keyframes, prefers-reduced-motion CSS and JS). Minor gaps keep it below anchor 5: the RippleButton uses an 'animate-ripple' class that is never defined in the CSS section and omits the useState import.

4 / 5

Workflow Clarity

This is a pattern catalog rather than a multi-step process, and each pattern is self-contained and unambiguous with a 'When to Use This Skill' selector; no destructive or batch operations, so no validation cap applies. It sits at anchor 4 — organization is clear, but there is no guidance on choosing between patterns or sequencing a full implementation, and the simple-skill 5 exemption (under 50 lines) does not apply to a ~320-line file.

4 / 5

Progressive Disclosure

No bundle files exist; the entire ~320-line catalog is inlined in SKILL.md with good section headers but no one-level-deep references. That matches anchor 3 — some structure, but content that could live in separate reference files (e.g., per-pattern pages) is inline — rather than 4's 'most content appropriately placed'.

3 / 5

Total

15

/

20

Passed

Description

75%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 strong description that clearly states capabilities and includes an explicit 'Use when...' trigger clause with natural phrases. Its main weaknesses are the vague 'delightful user experiences' filler and missing common trigger synonyms (animation, hover effects, skeleton screens) that would push it to the top anchor.

Suggestions

Replace 'creating delightful user experiences' with a concrete trigger such as 'adding hover/focus effects or skeleton screens'.

Add natural synonyms users would say, e.g., 'animations', 'page transitions', 'drag-and-drop', 'toasts'.

Tighten the 'when' clause to enumerate 2-3 concrete scenarios matching the body's 'When to Use This Skill' list.

DimensionReasoningScore

Specificity

Lists several concrete capabilities ('Design and implement microinteractions, motion design, transitions, and user feedback patterns'), though 'creating delightful user experiences' is vague filler. Closest to anchor 4 — several specific actions with minor gaps — rather than 5, which requires comprehensive coverage without padding.

4 / 5

Completeness

Explicitly answers both what ('Design and implement microinteractions, motion design, transitions...') and when ('Use when adding polish to UI interactions, implementing loading states...'). Not a 5 because the final trigger 'creating delightful user experiences' is too vague to serve as a concrete trigger phrase; clearly above the weak-'when' profile of anchor 4's low end and anchor 3's missing 'when'.

4 / 5

Trigger Term Quality

'adding polish to UI interactions' and 'implementing loading states' are phrases users naturally say, and 'microinteractions'/'motion design' are on-point domain terms. Missing common variations like 'animation', 'hover effects', or 'skeleton screens' (present only in the body), so it fits anchor 4 rather than 5.

4 / 5

Distinctiveness Conflict Risk

The motion/microinteraction niche is distinct with specific triggers, but it overlaps with general frontend, CSS, and UI-implementation skills (e.g., a hypothetical 'frontend-styling' skill could fire on 'polish to UI interactions'). Anchor 4 — mostly distinct with minor overlap risk — fits better than 5's minimal-conflict bar.

4 / 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

marchatton/agent-skills

Path

.agents/skills/04-develop/01-ui-skills-dot-com/interaction-design/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.