CtrlK
BlogDocsLog inGet started
Tessl Logo

suggest-lucide-icons

Suggest relevant Lucide icons for concepts or UI placements. Searches lucide.dev to find actual icons that symbolize ideas or fit design contexts. Use when needing icons for UI work, documentation, or symbolic representation.

76

Quality

95%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

SecuritybySnyk

Low

Low-risk findings worth noting

SKILL.md
Quality
Evals
Security

Quality

Content

100%

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

An exemplary instruction-only skill body: concise, fully actionable with a concrete verification URL, a clear validated workflow with retry logic, and well-organized sections needing no external bundle files.

DimensionReasoningScore

Conciseness

The body is lean and concrete throughout — Lucide naming rules, a verification URL template, and a numbered process — with no concept-explanation bloat; the only soft spot is a brief persona line ("I am skilled in symbolic interpretation...") which is unnecessary but minor.

3 / 3

Actionability

It gives copy-paste-ready guidance: the exact unpkg URL pattern `https://unpkg.com/lucide-static@latest/icons/[icon-name].svg`, WebFetch/`curl -L` instructions, and concrete naming examples, so Claude knows exactly what to execute.

3 / 3

Workflow Clarity

The Process is a clear four-step sequence with an explicit validation checkpoint (SVG present = exists, 404 = discard) and a feedback loop (try alternate names, brainstorm more if fewer than 3 survive), matching the level-3 anchor.

3 / 3

Progressive Disclosure

At roughly 50 lines with no need for external references, the well-organized sections (Input, Naming conventions, Process, Guidelines, Output Format) satisfy the simple-skill allowance for a top progressive-disclosure score.

3 / 3

Total

12

/

12

Passed

Description

90%

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 strong, concise description with explicit trigger guidance and a distinct Lucide-icon niche. Its only weakness is that the capability is essentially a single action phrased two ways rather than a list of several concrete actions.

Suggestions

To reach full specificity, enumerate a few distinct concrete actions (e.g. "Suggest Lucide icons for concepts, match icons to UI placements, and verify candidates exist on lucide.dev") rather than restating 'suggest/find icons' twice.

Add a couple more natural trigger variations users might say, such as 'icon picker' or 'find an icon for', to broaden trigger coverage marginally.

DimensionReasoningScore

Specificity

The description names the domain and mechanism ("Searches lucide.dev to find actual icons that symbolize ideas or fit design contexts") but this restates a single capability rather than listing multiple distinct concrete actions, so it stops short of the level-3 anchor.

2 / 3

Completeness

It states what the skill does (suggest/find Lucide icons) and includes an explicit "Use when needing icons for UI work, documentation, or symbolic representation" trigger clause, clearly answering both what and when.

3 / 3

Trigger Term Quality

Natural user-facing terms like "Lucide icons", "icons", "UI placements", "UI work", and "documentation" give good coverage of what a user would actually say when needing this skill.

3 / 3

Distinctiveness Conflict Risk

The Lucide-specific niche ("Lucide icons", lucide.dev) with icon-design triggers is clearly distinguishable and unlikely to fire for unrelated skills.

3 / 3

Total

11

/

12

Passed

Validation

93%

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

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

15

/

16

Passed

Repository
graphif/project-graph
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.