design
Intentional design thinking for interfaces, components, and systems. Use when the user asks to "build a UI", "design a page", "create a component", "make this look good", "design an API", "design a system", or any task where aesthetic or structural design decisions matter.
86
Quality
83%
Does it follow best practices?
Impact
Pending
No eval scenarios have been run
Passed
No known issues
Quality
Discovery
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.
This is a solid description with excellent trigger term coverage and complete what/when structure. The main weakness is the lack of specific concrete actions beyond the domain statement, and the broad scope spanning UI aesthetics to system design could create conflicts with more specialized skills.
Suggestions
Add specific concrete actions like 'create wireframes, define visual hierarchies, establish component patterns, structure API contracts' to improve specificity.
Consider narrowing scope or adding distinguishing details to reduce overlap with potential architecture/backend system design skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (design thinking for interfaces, components, systems) and implies actions like building UIs and designing APIs, but doesn't list concrete specific actions like 'create wireframes', 'define color schemes', or 'structure component hierarchies'. | 2 / 3 |
Completeness | Clearly answers both what ('Intentional design thinking for interfaces, components, and systems') and when ('Use when the user asks to...' with explicit trigger phrases), plus includes the catch-all 'any task where aesthetic or structural design decisions matter'. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural user phrases: 'build a UI', 'design a page', 'create a component', 'make this look good', 'design an API', 'design a system' - these are terms users would naturally say when needing design help. | 3 / 3 |
Distinctiveness Conflict Risk | While it has specific triggers, 'design a system' and 'design an API' could overlap with architecture or backend skills. The broad scope covering both UI aesthetics and system design increases potential conflict with more specialized skills. | 2 / 3 |
Total | 10 / 12 Passed |
Implementation
85%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-crafted design principles skill that excels at conciseness and organization. It provides clear mental frameworks and validation criteria for design decisions. The main weakness is the lack of concrete, executable examples—particularly for visual design where CSS snippets or API design where interface code would make the guidance more immediately actionable.
Suggestions
Add a concrete CSS example showing color palette implementation with CSS variables and a distinctive font pairing
Include a brief API design example showing good vs. bad naming/structure patterns
Add one executable motion/animation CSS snippet demonstrating the 'staggered reveals' concept
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is lean and efficient, presenting design principles without explaining concepts Claude already knows. Every section delivers actionable guidance without padding or unnecessary context. | 3 / 3 |
Actionability | Provides clear principles and guidelines but lacks concrete, executable examples. No code snippets for CSS variables, motion implementations, or API patterns. The guidance is specific but descriptive rather than copy-paste ready. | 2 / 3 |
Workflow Clarity | For a principles-based skill, the workflow is clear: Design Thinking provides a 4-step sequence, and 'The Test' section provides explicit validation checkpoints. The single-task nature (design decision-making) is unambiguous. | 3 / 3 |
Progressive Disclosure | Well-organized with clear sections and appropriate 'See Also' references to related skills. Content is appropriately scoped for a SKILL.md overview without being monolithic or requiring deep nesting. | 3 / 3 |
Total | 11 / 12 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 — 11 / 11 Passed
Validation for skill structure
No warnings or errors.
- Repository
- tslateman/duet
- Commit
96a72fa
- 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.