favicon
Generate a complete set of favicons from a source image and update HTML. Use when setting up favicons for a web project.
Overall
score
79%
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
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 is a functional description that clearly communicates its purpose and includes an explicit 'Use when' clause. However, it could benefit from more specific capability details and additional trigger terms that users might naturally use when requesting favicon help.
Suggestions
Add more specific capabilities like 'generates multiple sizes (16x16, 32x32, 180x180), creates favicon.ico, apple-touch-icon, and manifest 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, specific niche that is unlikely to conflict with other skills. The combination of 'favicons', 'source image', and 'web project' creates distinct triggers. | 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-crafted, highly actionable skill with excellent workflow clarity and executable commands throughout. The main weakness is length - the comprehensive framework detection table and multiple framework-specific update instructions make it verbose. The content could benefit from splitting framework-specific details into separate reference files.
Suggestions
Consider moving the framework detection table and framework-specific HTML update instructions to a separate FRAMEWORKS.md reference file to reduce the main skill's length
Remove explanatory phrases like 'Important:' annotations where the instruction itself is self-evident to reduce token count
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The skill is comprehensive but includes some verbosity that could be tightened. The framework detection table is useful but lengthy, and some explanations (like the HTML placement notes) repeat information Claude would infer. | 2 / 3 |
Actionability | Provides fully executable bash commands for ImageMagick, complete JSON for the manifest, and ready-to-use HTML/TypeScript snippets. All code is copy-paste ready with clear placeholders. | 3 / 3 |
Workflow Clarity | Clear 8-step sequence with explicit validation (check ImageMagick, validate source image, confirm directory). Includes error handling section and explicit checkpoints like 'When in doubt, ask' for ambiguous situations. | 3 / 3 |
Progressive Disclosure | Content is well-structured with clear sections and a logical flow, but the skill is monolithic at ~200 lines. The framework-specific HTML update instructions could be split into separate reference files to reduce cognitive load. | 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 |
|---|---|---|
metadata_version | 'metadata' field is not a dictionary | Warning |
license_field | 'license' field is missing | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | 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.