CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

interaction-design

Creates intuitive user experiences through feedback patterns, microinteractions, and accessible interaction design. Use when designing loading states, error handling UX, animation guidelines, or touch interactions.

64

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 ./plugins/interaction-design/skills/interaction-design/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

75%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, mostly lean pattern catalog with executable code examples and specific numeric guidance. Its weaknesses are minor: redundant guidance across the Accessibility, Animation Guidelines, and Best Practices sections, dependencies on undefined custom components, and no framing that tells the reader when to apply each pattern.

Suggestions

Consolidate the overlapping guidance: prefers-reduced-motion and keyboard-navigation advice currently appears in both the Accessibility/Animation Guidelines sections and the Best Practices list — merge into one place.

Note (or inline) the <Icon> and <Illustration> component dependencies in the JSX snippets, or replace them with plain SVG/text equivalents so the code is copy-paste ready.

Add a short intro or decision cue (e.g., "match the state you're designing: loading, error, or empty") that guides pattern selection, and trim the ~100-line body toward the lean simple-skill profile.

DimensionReasoningScore

Conciseness

The body is lean — a compact table, terse CSS/JSX snippets, and bullet lists with no explanation of concepts Claude already knows. Minor trimming is possible: "prefers-reduced-motion" and keyboard-navigation guidance each appear redundantly in the Accessibility/Animation Guidelines sections and again in Best Practices.

4 / 5

Actionability

Provides concrete, executable artifacts (the shimmer CSS skeleton, LoadingState/ErrorState/EmptyState JSX, aria-live announcer) with specific numeric guidance (100–200ms durations, >0.5s loading threshold). Minor gaps: snippets depend on undefined <Icon> and <Illustration> components without noting that dependency.

4 / 5

Workflow Clarity

As a pattern catalog rather than a multi-step process, no destructive/batch validation cap applies and the individual patterns are unambiguous to apply. However, it offers no guidance on choosing among the patterns or a suggested design sequence, keeping it below anchor 5.

4 / 5

Progressive Disclosure

No bundle files exist, and the ~100-line body is well-organized into clearly headed sections with no nested references. It slightly exceeds the under-50-line simple-skill bar and lacks an overview tying the sections together or signaling when to consult each pattern.

4 / 5

Total

16

/

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 solid description with an explicit "Use when" trigger clause and natural, domain-specific trigger terms. Its main weakness is the slightly fluffy opening ("Creates intuitive user experiences") in place of concrete capability verbs, and some missing synonyms for the trigger scenarios.

DimensionReasoningScore

Specificity

Names several concrete capability areas — "feedback patterns, microinteractions, and accessible interaction design" — but the leading verb "Creates intuitive user experiences" is a goal statement rather than a concrete action, so it falls just short of anchor 5's comprehensive action list.

4 / 5

Completeness

Both what and when are present — "Use when designing loading states, error handling UX, animation guidelines, or touch interactions" is an explicit trigger — but the "what" ("Creates intuitive user experiences") is somewhat padded and less concrete than anchor 5's exemplar of listed actions.

4 / 5

Trigger Term Quality

"loading states, error handling UX, animation guidelines, or touch interactions" are natural phrases a user would say when needing this skill, though common synonyms like "skeleton screens", "empty states", and "transitions" are missing.

4 / 5

Distinctiveness Conflict Risk

The interaction-design triggers (microinteractions, loading states, touch interactions) carve a reasonably clear niche, with only minor overlap risk against general frontend, accessibility, or design-system skills.

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

secondsky/claude-skills

Path

plugins/interaction-design/skills/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.