favicon-gen
Generate custom favicons from logos, text, or brand colors - prevents launching with CMS defaults. Extract icons from logos, create monogram favicons from initials, or use branded shapes. Outputs all required formats: favicon.svg, favicon.ico, apple-touch-icon.png, and web app manifest. Use when: initializing new websites, replacing WordPress/CMS default favicons, converting logos to favicons, creating branded icons from text only, or troubleshooting favicon not displaying, iOS icon transparency, or missing manifest files.
Overall
score
87%
Does it follow best practices?
If you maintain this skill, you can automatically optimize it using the tessl CLI to improve its score:
npx tessl skill review --optimize ./path/to/skillValidation for skill structure
Discovery
100%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 is an excellent skill description that clearly articulates specific capabilities (extracting icons, creating monograms, outputting multiple formats), includes comprehensive natural trigger terms users would actually say, and provides explicit 'Use when' guidance covering multiple scenarios. The description is well-structured, uses proper third-person voice, and carves out a distinct niche that won't conflict with other skills.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Lists multiple specific concrete actions: 'Extract icons from logos, create monogram favicons from initials, or use branded shapes' and specifies exact output formats (favicon.svg, favicon.ico, apple-touch-icon.png, web app manifest). | 3 / 3 |
Completeness | Clearly answers both what (generate favicons from various sources, output specific formats) AND when with explicit 'Use when:' clause covering initialization, replacement, conversion, creation, and troubleshooting scenarios. | 3 / 3 |
Trigger Term Quality | Excellent coverage of natural terms users would say: 'favicons', 'logos', 'brand colors', 'WordPress/CMS default', 'initials', 'iOS icon', 'manifest files', plus specific file extensions and common troubleshooting phrases. | 3 / 3 |
Distinctiveness Conflict Risk | Very clear niche focused specifically on favicon generation with distinct triggers like 'favicon', 'apple-touch-icon', 'web app manifest' - unlikely to conflict with general image or logo skills. | 3 / 3 |
Total | 12 / 12 Passed |
Implementation
77%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This is a well-structured, highly actionable skill with excellent workflow clarity and concrete examples. The main weaknesses are verbosity (production statistics, extensive known issues documentation, metadata headers) and a monolithic structure that could benefit from splitting detailed reference content into separate files. The core favicon generation guidance is solid and immediately usable.
Suggestions
Move the 'Known Issues Prevention' section to a separate reference file - the prevention rules are already embedded in the 'Critical Rules' section
Remove or minimize the metadata header (Status, Last Updated, Dependencies) - this adds tokens without instructional value
Move industry-specific shape recommendations and color guidelines to references/ - these are lookup tables, not core workflow
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some unnecessary verbosity - the status/metadata header, extensive known issues section with sources, and production statistics add tokens without proportional value. The core instructions are reasonably efficient but could be tightened. | 2 / 3 |
Actionability | Provides fully executable code examples including complete SVG templates, bash commands for ImageMagick, copy-paste ready HTML integration, and complete manifest JSON. Examples are concrete and immediately usable. | 3 / 3 |
Workflow Clarity | Clear 4-step process with explicit validation checkpoints (visual testing checklist, technical validation commands). Decision tree at start guides method selection. File delivery checklist ensures completeness. Troubleshooting section provides error recovery paths. | 3 / 3 |
Progressive Disclosure | References external files (templates/, references/) appropriately, but the main skill file is quite long (~500 lines) with content that could be split out (known issues, industry tables, real-world examples). The structure is good but the file itself is monolithic. | 2 / 3 |
Total | 10 / 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 — 13 / 16 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
skill_md_line_count | SKILL.md is long (615 lines); consider splitting into references/ and linking | Warning |
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
Total | 13 / 16 Passed | |
- 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.