CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

favicon

Use when checking whether a site has a correctly configured favicon, auditing `<link rel='icon'>` tags in the `<head>`, or setting up favicon infrastructure for a new project.

Quality

82%

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

71%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, actionable body with concrete file specifications, copy-paste HTML, explicit validation checkpoints, and a correctly signaled single-level reference file. Its main weakness is redundancy: the core criteria appear in both Quick Reference and Check, and Explain repeats the intro's rationale, which costs tokens without adding guidance.

Suggestions

Merge "Quick Reference" into "Check" and trim the "Explain" section's restatement of the intro — the 48×48px / robots.txt / HTTPS / ICO-fallback criteria currently appear three times.

Add the "how" for Fix step 1, e.g., an ImageMagick command to generate favicon.ico, favicon.svg, and apple-touch-icon.png from a source image, plus a `curl -I` command for the 200-response verification.

Add an explicit error-recovery loop after the Fix validation steps, e.g., "If the URL returns 404, confirm the href path matches the file location, fix, and re-verify."

DimensionReasoningScore

Conciseness

The 48×48px, robots.txt, HTTPS, and ICO+SVG/PNG criteria appear nearly verbatim in both "Quick Reference" ("at least 48×48px for Google's use", "not blocked by robots.txt") and "Check" ("The file is at least 48×48px", "not blocked by robots.txt"), and the "Explain" section restates both the intro's Google-SERP point and browser-tab basics Claude already knows ("Favicons appear next to your site's name in browser tabs, bookmarks..."). Mostly efficient, but the tripling of core criteria and the redundant Explain section mean it could be meaningfully tightened.

3 / 5

Actionability

Highly concrete: exact file specs ("favicon.ico (16×16 and 32×32, ICO format)", "apple-touch-icon.png (180×180 PNG)"), a copy-paste HTML `<link>` snippet, and specific verification criteria ("returns a 200", "URL Inspection tool in Search Console"). Not 5 because "Create favicon files" specifies targets without any method or command for generating them, and the verification steps (200 check, robots.txt) lack executable commands. Not 3 because the guidance is executable, not pseudocode or vague direction.

4 / 5

Workflow Clarity

"Fix" is a clearly numbered 1–6 sequence with explicit validation checkpoints (step 4 "Verify the favicon URL returns a 200 response", step 5 robots.txt check, step 6 Search Console test), and "Check" provides a numbered verification list. Not 5 because there is no explicit error-recovery feedback loop for when a validation step fails (e.g., what to do on a 404). Not 3 because checkpoints are explicit rather than merely implicit, and the operation is neither destructive nor batch.

4 / 5

Progressive Disclosure

The body is a well-sectioned overview (Quick Reference / Check / Fix / Explain / Code Review) that keeps implementation details in a clearly signaled one-level-deep reference ("For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`"), and `references/rule.md` exists in the bundle. Content is appropriately split and navigation is easy; no organization gaps, so it fits the top anchor rather than the 'minor organization gaps' anchor below it.

5 / 5

Total

16

/

20

Passed

Description

87%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 with an explicit "Use when..." trigger clause enumerating three concrete capabilities in a distinctive niche. Its only weakness is a few absent natural synonym trigger terms (e.g., "site icon", "favicon.ico"), which does not materially harm triggering given the dominance of "favicon" as the natural user term.

DimensionReasoningScore

Specificity

Three concrete actions are named — "checking whether a site has a correctly configured favicon", "auditing `<link rel='icon'>` tags in the `<head>`", and "setting up favicon infrastructure for a new project" — comparable to the 4-anchor's several specific actions. Not 5 because "setting up favicon infrastructure" is slightly generic and repair of an existing broken favicon is not an explicit distinct action; not 3 because coverage goes beyond 1–2 actions and the link-tag audit is highly concrete.

4 / 5

Completeness

The explicit "Use when checking ... or setting up ..." construction answers "when" with concrete trigger phrases, and the enumerated actions (checking configuration, auditing `<link rel='icon'>` tags, setting up infrastructure) explicitly state what the skill does. It is not the 4 anchor because the "when" is fully explicit and specific rather than weakly implied or in need of more precision.

5 / 5

Trigger Term Quality

"favicon" is the dominant natural user term and appears twice, paired with concrete trigger activities (checking configuration, auditing link tags, setting up). A few natural terms are missing — "site icon", "shortcut icon", "favicon.ico", "apple touch icon" — so it matches the 4 anchor (good coverage, a few natural terms missing) rather than the 5 anchor's synonym-and-extension comprehensiveness, and is well above the bare domain-naming of the 3 anchor.

4 / 5

Distinctiveness Conflict Risk

"favicon" is a clear niche trigger with distinct, specific trigger conditions (favicon configuration, `<link rel='icon'>` auditing, favicon setup), creating minimal conflict risk with other skills. It does not exhibit the minor overlap-with-related-skills weakness of the 4 anchor.

5 / 5

Total

18

/

20

Passed

Validation

93%

Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.

Validation — 15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository

thedaviddias/Front-End-Checklist

Path

skills/favicon/SKILL.md

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.