CtrlK
BlogDocsLog inGet started
Tessl Logo

add-icon-mapping

Add or modify icon keyword mappings for providers, models, or agents in lobe-icons. Use this whenever a task involves mapping a provider/model id to an icon, adding a new entry to ModelProvider enum or providerMappings/modelMappings/agentMappings, or fixing a provider/model that renders the fallback (default) icon in LobeHub. Trigger even if the request only says "add icon for X provider" or references a Linear issue about icon keyword mapping — the actual icon component usually already exists; only the mapping is missing.

80

Quality

100%

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

SKILL.md
Quality
Evals
Security

Quality

Content

100%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 content is a strong example of a focused, repo-specific skill: executable code, exact commands, a sequenced workflow with explicit validation, and tight prose that assumes Claude's intelligence. It maximizes every dimension without verbosity or padding.

DimensionReasoningScore

Conciseness

The body is lean and assumes Claude's competence — it never explains what TypeScript, regex, or git are, and every section (mapping tables, matching semantics, pitfalls) earns its place with non-obvious, repo-specific detail.

5 / 5

Actionability

It provides copy-paste-ready code for the enum member, imports, and mapping entry, exact verification commands (`bun run type-check`, the grep with expected '2×2' hits), and concrete precedent entries to follow for the append-vs-new-entry decision.

5 / 5

Workflow Clarity

The provider workflow is a clearly numbered sequence with an explicit RN-repeat step, and the Verification and Commit pitfalls sections add real validation checkpoints (type-check, grep completeness check, `git show --stat HEAD`) with feedback loops for a batch/duplicated operation.

5 / 5

Progressive Disclosure

No bundle files are present (references/scripts/assets are absent), so the single self-contained SKILL.md is correctly organized into well-signaled sections with no nested or buried references; nothing that belongs in a separate file is inlined.

5 / 5

Total

20

/

20

Passed

Description

100%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 is exemplary: it states concrete actions, gives explicit 'use when' and 'trigger even if' guidance, and targets a distinct niche with realistic user phrasings. It is concise yet comprehensive, hitting the top anchor on every dimension.

DimensionReasoningScore

Specificity

The description lists multiple concrete actions — 'Add or modify icon keyword mappings', 'adding a new entry to ModelProvider enum or providerMappings/modelMappings/agentMappings', and 'fixing a provider/model that renders the fallback (default) icon' — giving comprehensive, specific coverage of what the skill does.

5 / 5

Completeness

It explicitly answers both 'what' (add/modify icon keyword mappings, enum entries, config tables) and 'when' with concrete trigger clauses: 'Use this whenever a task involves...' and 'Trigger even if the request only says...'.

5 / 5

Trigger Term Quality

It captures natural user phrasings users would actually say — 'add icon for X provider', 'renders the fallback (default) icon', and 'Linear issue about icon keyword mapping' — alongside technical ids (ModelProvider, providerMappings), covering synonyms and realistic request shapes.

5 / 5

Distinctiveness Conflict Risk

The niche is sharply defined — lobe-icons provider/model/agent id-to-icon mappings and the ModelProvider enum — with triggers unlikely to fire for unrelated skills, so conflict risk is minimal.

5 / 5

Total

20

/

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.

Validation16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
lobehub/lobe-icons
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.