CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

solar-duotone-bold

Use Iconify Solar Duotone Bold icon style.

Quality

71%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide
SecuritybySnyk

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./agent-skills/web-design/solar-duotone-bold/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%Weight 40%Scale 1-5

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

The body is an exemplar of brevity and organization — no padding, clean sections, useful guardrails — but its guidance stays at the principle level. Concrete specifics (default icon sizes, naming, opacity values, or how to fetch icons from Iconify) would make it directly executable rather than merely directional.

Suggestions

Add concrete defaults, e.g., a standard icon size (such as 24px) and a small size scale for component groups, instead of the abstract "Keep icon sizes consistent".

Include the specific mechanism for applying the style — an Iconify usage snippet, icon naming pattern, or CSS/component example — so the guidance is executable rather than directional.

Convert the five parallel Workflow principles into a short ordered checklist with a final verification step (e.g., 'Confirm every icon in the set is from Solar Duotone Bold and sizes match').

DimensionReasoningScore

Conciseness

The body is ~20 lean lines with zero padding: every line is guidance Claude does not already know ("Use Iconify Solar Duotone Bold as the default icon family", "Keep icon sizes consistent within a component group"), and it explains no general concepts. This matches 'Lean and efficient; every token earns its place'.

5 / 5

Actionability

Some guidance is concrete (consistent sizes within a component group, pairing icons with labels), but directives like "Use duotone opacity intentionally so secondary fills support the main glyph shape" and "Match stroke, fill, and color treatment to the surrounding surface contrast" are high-level with no specifics — no default sizes, icon naming conventions, or how to actually fetch/apply Iconify icons. This matches 'Some concrete guidance but incomplete'.

3 / 5

Workflow Clarity

The content is clearly organized into Use When, Workflow, and Guardrails with unambiguous rules, but the five numbered Workflow items are parallel principles rather than a sequenced process, and there is no checkpoint for verifying consistent application. It exceeds anchor 3 (which would have gaps or implicit checkpoints) but falls short of anchor 5's explicit feedback loops.

4 / 5

Progressive Disclosure

The skill is under 50 lines, has no bundle files to disclose, and is well organized into clearly signaled sections (Use When / Workflow / Guardrails). Per the judging guidelines, skills under 50 lines with no need for external references score 5 with well-organized sections.

5 / 5

Total

17

/

20

Passed

Description

48%Weight 40%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 a specific, niche icon family but does almost nothing else: it has one generic verb, no 'Use when' trigger clause, and no concrete capability statements. It is serviceable for matching on the icon family name but weak as a routing and capability signal.

Suggestions

Add a 'Use when...' trigger clause (e.g., 'Use when picking, styling, or applying UI icons, or when the user mentions duotone, bold, or Solar icon sets').

Replace the single generic verb with concrete actions, e.g., 'Apply Iconify Solar Duotone Bold icons to UI components: select icons, set consistent sizes, tune duotone opacity, and match colors to surfaces'.

Include natural synonyms and variations users would say, such as 'icon set', 'duotone icons', and 'bold icons', to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description names the domain ("Iconify Solar Duotone Bold icon style") but its only action is the generic verb "Use", matching the anchor 'Names the domain but actions are minimal or generic'. It does not reach level 3 because no concrete actions like applying, sizing, or coloring icons are stated.

2 / 5

Completeness

The 'what' is stated ("Use Iconify Solar Duotone Bold icon style") but the 'when' is entirely absent — there is no 'Use when...' clause or equivalent trigger guidance, which caps completeness at 3 per the judging guidelines. It is not level 2 because the 'what' is specific rather than vague.

3 / 5

Trigger Term Quality

"icon style", "Iconify", and "Solar Duotone Bold" are relevant keywords, but common natural variations users would say ("duotone icons", "icon set", "bold icons", "SVG icons") are missing, matching 'Some relevant keywords but missing common variations or synonyms'. Level 4 requires fuller keyword coverage including synonyms.

3 / 5

Distinctiveness Conflict Risk

Naming a specific icon family ("Iconify Solar Duotone Bold") carves out a clear niche, but it risks minor overlap with closely related skills such as Solar Bold, Solar Duotone Light, or other icon-style skills, matching 'Mostly distinct; minor overlap risk with closely related skills'. It is not level 5 because the description lacks distinct trigger phrases to disambiguate.

4 / 5

Total

12

/

20

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 — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository

MengTo/Skills

Path

agent-skills/web-design/solar-duotone-bold/SKILL.md

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.