svg-icon-generator
Svg Icon Generator - Auto-activating skill for Visual Content. Triggers on: svg icon generator, svg icon generator Part of the Visual Content skill category.
36
3%
Does it follow best practices?
Impact
100%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/18-visual-content/svg-icon-generator/SKILL.mdQuality
Discovery
7%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 description is essentially a template placeholder with no substantive content. It restates the skill name, duplicates the trigger term, and provides no concrete actions, use cases, or explicit trigger guidance. It would be nearly indistinguishable from other visual content skills and gives Claude insufficient information to select it appropriately.
Suggestions
Add specific concrete actions the skill performs, e.g., 'Generates SVG icon markup from text descriptions, creates scalable vector icons with customizable colors, sizes, and styles.'
Add an explicit 'Use when...' clause with natural trigger terms, e.g., 'Use when the user asks to create an SVG icon, design a vector icon, generate icon markup, or needs a .svg file for UI elements.'
Remove the duplicated trigger term and expand with natural variations users would say, such as 'icon', 'vector graphic', 'SVG image', 'create an icon', 'icon design'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description contains no concrete actions. It only states 'Svg Icon Generator' and 'Visual Content' without describing what it actually does (e.g., creates SVG icons, designs vector graphics, generates icon sets). | 1 / 3 |
Completeness | The description fails to answer both 'what does this do' and 'when should Claude use it'. There is no explicit 'Use when...' clause, and the 'what' is essentially just the skill name restated without elaboration. | 1 / 3 |
Trigger Term Quality | The trigger terms are just 'svg icon generator' repeated twice. There are no natural variations users might say like 'create an icon', 'vector icon', 'SVG image', 'make me an icon', '.svg', or 'icon design'. | 1 / 3 |
Distinctiveness Conflict Risk | The mention of 'SVG' and 'icon' provides some specificity that distinguishes it from generic visual content skills, but the vague 'Visual Content' category label and lack of concrete scope could cause overlap with other image or design-related skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty template with no actual content about SVG icon generation. It contains only generic boilerplate text that provides no actionable guidance, no code examples, no SVG-specific knowledge, and no workflow. It fails on every dimension of the rubric.
Suggestions
Add concrete, executable SVG code examples showing how to generate common icon types (e.g., a complete SVG icon with viewBox, path data, and styling)
Define a clear workflow for icon generation: requirements gathering → SVG structure → path creation → optimization → validation, with specific tools or validation steps
Include specific SVG best practices such as viewBox sizing conventions, stroke vs fill approaches, accessibility attributes (aria-label, role), and optimization techniques (removing unnecessary attributes)
Replace all generic boilerplate sections ('When to Use', 'Capabilities', 'Example Triggers') with actual technical content about SVG icon patterns, common shapes, and reusable templates
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and boilerplate. It explains nothing Claude doesn't already know, contains no actual SVG knowledge, and every section is generic placeholder text that could apply to any skill. | 1 / 3 |
Actionability | There is zero concrete guidance—no SVG code, no commands, no examples of actual icon generation. Every bullet point is vague and abstract ('Provides step-by-step guidance' without any actual steps). | 1 / 3 |
Workflow Clarity | No workflow is defined at all. There are no steps, no sequences, no validation checkpoints—just generic claims about providing 'step-by-step guidance' without delivering any. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of generic text with no references to supporting files, no structured navigation, and no meaningful content organization. There are no bundle files to reference either. | 1 / 3 |
Total | 4 / 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 — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3a2d27d
- 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.