CtrlK
BlogDocsLog inGet started
Tessl Logo

favicon-gen

Generate custom favicons from logos, text, or brand colours. Produces favicon.svg, favicon.ico, apple-touch-icon.png, icon-192/512.png, and web manifest. Use whenever the user wants a favicon, mentions replacing a CMS default favicon, converting a logo into a favicon, creating branded initials icons, or troubleshooting favicon not displaying / iOS black square / missing manifest.

75

Quality

94%

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

86%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 body is a well-structured, actionable favicon-generation workflow with copy-paste code, a clear decision tree, and properly offloaded reference material. Main weaknesses are mild redundancy between the quick-reference table and the step bodies, and verification steps that sit in Critical Rules rather than as inline workflow checkpoints.

Suggestions

Fold the "Format Quick Reference" table into Step 3 (or trim it to only the transparency/purpose column) to remove the size duplication with the convert commands and Critical Rules.

Promote "Test at 16x16" and "verify all five formats generated" into an explicit Step 6 verification checkpoint with a fix/retry loop, so validation is inline in the workflow rather than only in Critical Rules.

Either add a hexagon SVG asset to match the "hexagon (tech)" shape mentioned in Step 2, or drop hexagon from the shape list to keep the Asset Files section and the body consistent.

DimensionReasoningScore

Conciseness

The body is efficient and assumes Claude's competence (no explanation of what favicons/SVG are), but the "Format Quick Reference" table partly duplicates sizes and transparency info already conveyed in Step 3 commands and the Critical Rules. Matches the 'efficient; minor instances that could be trimmed' anchor; not a 5 because of that redundancy, not a 3 because there is no padding or over-explanation of known concepts.

4 / 5

Actionability

Provides copy-paste-ready, executable artifacts: a complete monogram SVG template, ImageMagick `convert` commands with install instructions and a favicon.io fallback, a full manifest JSON, and HTML link tags. Covers the common cases (logo, monogram, branded shape); matches the fully-executable top anchor. Not a 4 because the guidance is complete and copy-paste ready rather than having minor gaps.

5 / 5

Workflow Clarity

A clear 5-step sequence with an upfront decision tree (Step 1) and a verification rule ("Test at 16x16 — if it's not legible, simplify") plus a completeness rule ("Always generate ALL formats"). Matches the 'clear sequence with most checkpoints present; minor validation gaps' anchor. Not a 5 because validation lives in Critical Rules rather than as an inline checkpoint with an explicit fix/retry feedback loop in the step sequence; not a 3 because a verification step does exist so the batch-operation cap is not triggered.

4 / 5

Progressive Disclosure

SKILL.md is a concise overview with dedicated "Asset Files" and "Reference Files" sections listing each bundle file with a one-line description; all referenced files (4 assets, 4 references) exist and are one level deep. Detailed material (extraction methods, advanced monogram patterns, shape templates with full SVG, complete format specs) is correctly offloaded to references. Matches the clear-overview top anchor; not a 4 because navigation is explicit and the split is appropriate.

5 / 5

Total

18

/

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 strong: third-person voice, concrete capabilities, comprehensive output list, and an explicit 'Use whenever...' clause with natural trigger phrases including troubleshooting scenarios. It cleanly satisfies the top anchor on every dimension.

DimensionReasoningScore

Specificity

Names multiple concrete actions and inputs ("Generate custom favicons from logos, text, or brand colours") and comprehensively enumerates outputs ("favicon.svg, favicon.ico, apple-touch-icon.png, icon-192/512.png, and web manifest"), matching the comprehensive-coverage anchor. It is not a 4 because the output list is exhaustive rather than having minor gaps.

5 / 5

Completeness

Explicitly answers both what (generate favicons + the named format outputs) and when ("Use whenever the user wants a favicon, mentions replacing a CMS default favicon, ... or troubleshooting favicon not displaying / iOS black square / missing manifest") with concrete trigger phrases, matching the top anchor. Not a 4 because both halves are explicit and specific rather than merely present.

5 / 5

Trigger Term Quality

Includes natural user phrasings and synonyms such as "favicon", "replacing a CMS default favicon", "converting a logo into a favicon", "branded initials icons", and troubleshooting terms ("favicon not displaying", "iOS black square", "missing manifest"). Comprehensive coverage incl filename extensions and edge-case triggers; not a 4 because no common variants are missing.

5 / 5

Distinctiveness Conflict Risk

Favicon generation is a clear niche with highly specific triggers (iOS black square, CMS default favicon, missing manifest), giving minimal conflict risk with other skills. Not a 4 because the triggers are sharply favicon-specific with no real overlap risk.

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.

Validation — 16 / 16 Passed

Validation for skill structure

No warnings or errors.

Repository
jezweb/claude-skills
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.