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.
Install with Tessl CLI
npx tessl i github:secondsky/claude-skills --skill interaction-design83
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
N/ABased on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
Something went wrong
Implementation
79%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a solid interaction design reference with excellent, executable code examples and efficient presentation. The main weaknesses are the lack of workflow guidance for implementing these patterns together and the monolithic structure that could benefit from splitting detailed topics into separate referenced files.
Suggestions
Add a brief workflow section explaining the order of implementation (e.g., 'Start with loading states, then add error handling, then empty states') with validation checkpoints
Consider splitting detailed accessibility patterns and animation guidelines into separate referenced files (e.g., ACCESSIBILITY.md, ANIMATIONS.md) to improve progressive disclosure
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting patterns, code examples, and guidelines without unnecessary explanation. No verbose descriptions of what interactions are or how CSS/React work. | 3 / 3 |
Actionability | Provides fully executable CSS and JSX code examples that are copy-paste ready. The skeleton loader, error state, empty state, and accessibility components are all concrete and implementable. | 3 / 3 |
Workflow Clarity | This is a pattern reference skill rather than a multi-step workflow, but the content lacks explicit guidance on when/how to combine these patterns or validation steps for testing implementations. The best practices are listed but not sequenced. | 2 / 3 |
Progressive Disclosure | Content is well-organized with clear sections, but everything is inline in one file. For a skill of this scope covering multiple interaction patterns, some content (like detailed animation guidelines or accessibility patterns) could be split into referenced files. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
87%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 |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
body_steps | No step-by-step structure detected (no ordered list); consider adding a simple workflow | Warning |
Total | 14 / 16 Passed | |
- 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.