icon-design
Select semantically appropriate icons for websites using Lucide, Heroicons, or Phosphor. Covers concept-to-icon mapping, React/HTML templates, and tree-shaking patterns. Use when: building feature sections, service grids, contact info, navigation, or any UI needing icons. Prevents emoji usage, ensures consistency.
98
Does it follow best practices?
Validation for skill structure
Discovery
100%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 well-crafted skill description that excels across all dimensions. It provides specific capabilities (icon selection, templates, tree-shaking), names concrete icon libraries, includes an explicit 'Use when' clause with natural trigger contexts, and carves out a distinct niche that won't conflict with other skills. The description uses proper third-person voice throughout.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple concrete actions: 'Select semantically appropriate icons', 'concept-to-icon mapping', 'React/HTML templates', and 'tree-shaking patterns'. Covers both the selection process and implementation details. | 3 / 3 |
Completeness | Clearly answers both what ('Select semantically appropriate icons... concept-to-icon mapping, React/HTML templates, tree-shaking patterns') and when ('Use when: building feature sections, service grids, contact info, navigation, or any UI needing icons'). | 3 / 3 |
Trigger Term Quality | Includes natural terms users would say: 'icons', 'Lucide', 'Heroicons', 'Phosphor', 'feature sections', 'service grids', 'contact info', 'navigation', 'UI'. Good coverage of both library names and use case contexts. | 3 / 3 |
Distinctiveness Conflict Risk | Highly specific niche focused on icon selection with named libraries (Lucide, Heroicons, Phosphor). The explicit mention of preventing emoji usage and specific UI contexts makes it clearly distinguishable from general UI or design skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
100%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is an exemplary skill file that maximizes information density while maintaining clarity. The quick reference table covers 80% of use cases immediately, the tree-shaking code example prevents a critical mistake, and the decision tree handles edge cases elegantly. References are well-organized and clearly signaled.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Extremely lean and efficient. Uses tables for quick reference, avoids explaining what icons are or how React works. Every section delivers actionable information without padding. | 3 / 3 |
Actionability | Provides concrete icon names across three libraries, executable code examples showing good vs bad patterns, specific Tailwind classes with pixel values, and a clear decision tree for selection. | 3 / 3 |
Workflow Clarity | Clear 5-step selection process with explicit sequence. The decision tree provides excellent guidance for uncertain cases. For a non-destructive task like icon selection, validation checkpoints aren't critical. | 3 / 3 |
Progressive Disclosure | Perfect structure: quick reference table upfront for common cases, detailed guidance in main content, and clear one-level-deep references to semantic-mapping.md, icon-templates.md, and other resources for advanced needs. | 3 / 3 |
Total | 12 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
body_output_format | No obvious output/return/format terms detected; consider specifying expected outputs | Warning |
Total | 13 / 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.