favicon
Generate a complete set of favicons from a source image and update HTML. Use when setting up favicons for a web project.
84
76%
Does it follow best practices?
Impact
100%
1.35xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./skills/favicon/SKILL.mdQuality
Discovery
75%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 functional with a clear 'Use when' clause and distinct purpose, earning strong marks for completeness and distinctiveness. However, it could be improved by listing more specific capabilities (e.g., sizes, formats) and including additional trigger terms users might naturally use when requesting favicon help.
Suggestions
Add specific capabilities like 'generates multiple sizes (16x16, 32x32, 180x180), creates favicon.ico, apple-touch-icon, and webmanifest icons'
Expand trigger terms to include variations like 'favicon.ico', 'site icon', 'browser icon', 'apple-touch-icon', or 'PWA icons'
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | Names the domain (favicons) and mentions two actions ('generate favicons' and 'update HTML'), but lacks comprehensive detail about specific capabilities like sizes generated, formats supported, or what HTML updates entail. | 2 / 3 |
Completeness | Clearly answers both what ('Generate a complete set of favicons from a source image and update HTML') and when ('Use when setting up favicons for a web project') with an explicit trigger clause. | 3 / 3 |
Trigger Term Quality | Includes 'favicons' and 'web project' which are relevant, but misses common variations users might say like 'favicon.ico', 'site icon', 'browser icon', 'app icons', or 'touch icons'. | 2 / 3 |
Distinctiveness Conflict Risk | Favicon generation is a clear niche with distinct triggers; unlikely to conflict with other skills as it specifically targets favicon creation from source images for web projects. | 3 / 3 |
Total | 10 / 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 clear workflows and validation steps. The main weakness is length—the framework-specific HTML update sections are repetitive and could be consolidated or externalized. The skill excels at providing executable commands and handling edge cases.
Suggestions
Consider extracting framework-specific HTML update instructions into a separate reference file (e.g., FRAMEWORK_HTML.md) to reduce the main skill's length
Consolidate the repeated HTML snippet by showing it once and noting only the differences per framework (file location, metadata format for Next.js)
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some redundancy (e.g., repeating HTML snippets for different frameworks with minor variations, explaining basic concepts like title case conversion). The framework detection table is efficient, but the overall document could be tightened. | 2 / 3 |
Actionability | Provides fully executable ImageMagick commands, complete JSON for webmanifest, and copy-paste ready HTML/TypeScript snippets. All commands are specific with exact flags and parameters. | 3 / 3 |
Workflow Clarity | Clear 8-step sequence with explicit validation checkpoints (verify ImageMagick, validate source image, confirm directory). Includes error handling section and 'when in doubt, ask' guidance for ambiguous situations. | 3 / 3 |
Progressive Disclosure | Content is well-organized with clear sections and a helpful table, but it's a monolithic document (~200 lines) that could benefit from splitting framework-specific HTML updates into separate files or collapsible sections. | 2 / 3 |
Total | 10 / 12 Passed |
Validation
90%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 10 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 10 / 11 Passed | |
- Repository
- brianlovin/claude-config
- Commit
1a9819e
- 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.