iconsax-library

Extensive icon library and AI-driven icon generation skill for premium UI/UX design.

Quality

37%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/iconsax-library/SKILL.md

Quality

Content

38%Scale 1-5

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

This skill reads more like a marketing brief for Iconsax than actionable technical guidance. It lacks any concrete code examples, import patterns, or integration snippets that would allow Claude to actually implement icons from the library. The tone is aspirational ('premium', 'highest-tier', 'stunning') rather than instructional, wasting tokens on subjective adjectives instead of executable guidance.

Suggestions

Add concrete code examples showing how to import and use Iconsax icons (e.g., SVG inline usage, React/Vue component imports, or CDN link setup).

Remove marketing language ('premium', 'highest-tier', 'ultra-minimalism') and replace with specific, actionable technical details like icon naming conventions, file paths, or API parameters for the AI generator.

Include a concrete example of using Iconsax AI — what the input looks like, what output to expect, and how to integrate the generated result.

Add a verification step in the workflow (e.g., 'Confirm the icon renders at the correct size and style by previewing in the browser').

Dimension	Reasoning	Score
Conciseness	The content is noticeably verbose with unnecessary explanations Claude already knows (e.g., what Iconsax is, what icons are for, explaining that icons should 'feel intentional and premium'). Phrases like 'intuitive and comprehensive icon library designed for modern digital products' and 'distinctly premium feel' are marketing fluff, not actionable guidance.	2 / 5
Actionability	The skill provides no concrete code, no SVG examples, no import statements, no web component usage patterns, and no actual implementation guidance. It tells Claude to 'use SVGs or web components' without showing how. The workflow is entirely abstract with no executable steps.	2 / 5
Workflow Clarity	There is a numbered sequence (Identify → Choose → Search/Generate → Integration), but the steps are vague and lack validation checkpoints. There's no verification step to confirm the icon renders correctly, no fallback if the AI generation fails, and the integration step is hand-wavy.	3 / 5
Progressive Disclosure	For a skill of this size (~40 lines) with no bundle files, the structure is reasonable with clear sections (Context, When to Use, Workflow, Rules). It doesn't need external files given its brevity, and the sections are well-labeled and navigable. However, it could benefit from linking to an examples file showing actual integration code.	4 / 5
	Total	11 / 20 Passed

Description

36%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.

The description identifies the domain (icons) but relies on vague, marketing-style language ('extensive', 'premium', 'AI-driven') rather than concrete actions. It completely lacks a 'Use when...' clause, making it difficult for Claude to know when to select this skill over other design-related skills. The buzzwords add no discriminative value and should be replaced with specific capabilities and trigger conditions.

Suggestions

Add an explicit 'Use when...' clause with trigger terms like 'icon', 'SVG', 'pictogram', 'UI icons', 'generate icon', 'icon set'.

Replace vague language ('extensive', 'premium', 'AI-driven') with concrete actions such as 'Search icon libraries, generate custom SVG icons, customize icon size/color/style for UI components'.

Include file formats or output types (e.g., SVG, PNG) to improve distinctiveness and trigger term coverage.

Dimension	Reasoning	Score
Specificity	Names the domain (icon library, icon generation) but actions are minimal and generic. 'AI-driven icon generation' is somewhat specific but 'extensive icon library' and 'premium UI/UX design' are vague marketing language rather than concrete actions.	2 / 5
Completeness	Has a vague 'what' (icon library and icon generation) but completely lacks a 'when' clause. There is no explicit guidance on when Claude should select this skill, which per the rubric should cap completeness at 3, and the weak 'what' brings it down to 2.	2 / 5
Trigger Term Quality	Includes some relevant keywords like 'icon', 'icon library', 'icon generation', and 'UI/UX design' that users might naturally say. However, it misses common variations like 'SVG', 'pictogram', 'glyph', specific icon formats, or phrases like 'create icons' or 'find icons'.	3 / 5
Distinctiveness Conflict Risk	Somewhat specific to icons and icon generation, which narrows the domain, but 'UI/UX design' is broad and could overlap with other design-related skills. The lack of specific triggers increases potential conflict with general design or asset creation skills.	3 / 5
	Total	10 / 20 Passed

Validation

90%

Warnings & errors only

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 10 / 11 Passed

Validation for skill structure

Criteria	Description	Result
frontmatter_unknown_keys	Unknown frontmatter key(s) found; consider removing or moving to metadata	Warning

	Total	10 / 11 Passed

Repository: administrakt0r/AI-Agents-Safe-Coding-Skills
Path: skills/iconsax-library/SKILL.md
Commit: 57c135b

Reviewed: 4 days ago

Table of Contents

Discovery Implementation Validation

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.