CtrlK
BlogDocsLog inGet started
Tessl Logo

favicon-generator

When the user wants to implement, optimize, or audit favicon and app icons. Also use when the user mentions "favicon," "app icon," "browser icon," "touch icon," "PWA icon," "favicon sizes," "apple-touch-icon," "favicon.ico," "site icon," or "tab icon." For visual system, use brand-visual-generator.

70

Quality

85%

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

75%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.

A well-structured, table-driven instructional skill with actionable HTML/Next.js guidance and appropriate cross-links to related skills. The main improvements are making the workflow sequence explicit, adding a concrete manifest.json example, and trimming the small amount of motivational padding.

Suggestions

Add a minimal manifest.json icons example (including the maskable purpose) so the PWA path is as copy-paste ready as the HTML link tags.

Make the working sequence explicit (assess stack → pick sizes/formats → implement → test via Search Console) with a verification checkpoint, rather than leaving the flow implicit across sections.

Trim motivational padding such as "Favicons help users identify sites; missing or incorrect icons hurt trust" and consider moving the detailed Google SERP table to a reference file to keep SKILL.md as a leaner overview.

DimensionReasoningScore

Conciseness

Mostly lean, table-driven content (Required Sizes, Formats, SERP requirements) with only minor padding such as "Favicons help users identify sites; missing or incorrect icons hurt trust" and the "When invoking" paragraph. Anchor 4 fits: efficient with a few trimmable tokens, below anchor 5's every-token-earns-its-place bar.

4 / 5

Actionability

Provides copy-paste HTML link tags, concrete Next.js file placement ("favicon.ico, icon.png, apple-icon.png" in /app), and named tools (RealFaviconGenerator, favicon.io, favicons npm). Minor gaps — the PWA manifest guidance ("Include icons array... with 192x192 and 512x512") lacks a concrete example — keep it at anchor 4 rather than 5.

4 / 5

Workflow Clarity

A clear assess (tech stack, PWA, existing assets) → sizes/formats → implement → test flow exists, with checkpoints in the "Test" bullet and the Output Format checklist. The sequence is implicit rather than explicitly ordered with validate/fix/retry loops, so anchor 4 rather than 5; checkpoints are present so above anchor 3.

4 / 5

Progressive Disclosure

Well-organized single-file structure with no buried or nested references; no bundle files exist, and nothing is deeply nested. At 96 lines with a sizable Google SERP table and implementation details, some content could arguably move to a reference file, so anchor 4 rather than 5.

4 / 5

Total

16

/

20

Passed

Description

95%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.

A strong description: it states concrete actions, has an explicit use-when clause with comprehensive trigger synonyms, and reduces conflict risk by redirecting visual-system requests to a sibling skill. The only gap is that the stated actions are slightly generic relative to the full scope (sizes, formats, manifests) the body covers.

DimensionReasoningScore

Specificity

"implement, optimize, or audit favicon and app icons" names the domain plus three concrete actions, but coverage has minor gaps (no mention of generating sizes, formats, or manifest icons). This matches anchor 4 rather than 3 (more than 1-2 actions) and falls short of 5 (not fully comprehensive).

4 / 5

Completeness

Explicitly answers what ("implement, optimize, or audit favicon and app icons") and when ("When the user wants to... Also use when the user mentions...") with concrete trigger phrases. Both elements are explicit, matching anchor 5 rather than anchor 4's softer 'when' clause.

5 / 5

Trigger Term Quality

Lists "favicon," "app icon," "browser icon," "touch icon," "PWA icon," "favicon sizes," "apple-touch-icon," "favicon.ico," "site icon," and "tab icon" — comprehensive natural synonyms plus the .ico file form users would actually say. Clearly the anchor-5 example pattern.

5 / 5

Distinctiveness Conflict Risk

Clear favicon niche with distinct trigger terms, and it actively disambiguates overlap ("For visual system, use brand-visual-generator"). Minimal conflict risk, matching anchor 5.

5 / 5

Total

19

/

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
kostja94/marketing-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.