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

85%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Quality

Content

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, actionable, and uses progressive disclosure effectively with a real one-level reference. The only weakness is redundant motivational prose about why favicons matter that Claude already knows.

Suggestions

Remove or merge the duplicate 'why favicons matter in SERP' rationale currently split between the intro and the 'Explain' section, since it is general knowledge.

Tighten the 'Explain' section to only the non-obvious detail (Google's explicit use of `<link rel='icon'>`), dropping the restated brand-recognition motivation.

Dimension	Reasoning	Score
Conciseness	The intro and the 'Explain' section both restate why favicons matter in SERP — general knowledge Claude already has — so the body could be tightened despite being mostly efficient.	2 / 3
Actionability	The Fix section provides copy-paste-ready HTML (`<link rel='icon' href='/favicon.ico' sizes='any'>`, SVG and apple-touch-icon links) plus concrete verification commands, matching the fully-executable anchor.	3 / 3
Workflow Clarity	Fix is a numbered 6-step sequence with explicit validation checkpoints — 200 response check, robots.txt check, and Search Console URL Inspection — and the Check section acts as a verification checklist.	3 / 3
Progressive Disclosure	The body is organized into clear sections and points to a single, well-signaled one-level-deep reference (`references/rule.md`), which exists and holds the detailed code examples.	3 / 3
	Total	11 / 12 Passed

Description

85%

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 explicit triggers, concrete actions, and a distinct favicon niche. Its main weakness is limited keyword variation — it leans on 'favicon' without natural synonyms a user might say.

Suggestions

Add natural trigger synonyms such as 'site icon', 'browser tab icon', or 'bookmark icon' so the description matches more user phrasings.

Consider adding a verb-form user utterance like 'add a favicon' or 'favicon not showing' to broaden trigger-term coverage.

Dimension	Reasoning	Score
Specificity	Lists three concrete actions — 'checking whether a site has a correctly configured favicon', 'auditing `<link rel='icon'>` tags in the `<head>`', and 'setting up favicon infrastructure' — matching the 'multiple specific concrete actions' anchor.	3 / 3
Completeness	An explicit 'Use when...' clause answers when, and the three action clauses answer what, satisfying both halves with explicit triggers.	3 / 3
Trigger Term Quality	'favicon' is a natural keyword users would say, but the description lacks common variations like 'site icon', 'browser tab icon', or 'bookmark icon', so coverage is partial rather than comprehensive.	2 / 3
Distinctiveness Conflict Risk	The scope is narrowly scoped to favicons and `<link rel='icon'>` configuration, a clear niche unlikely to trigger competing skills.	3 / 3
	Total	11 / 12 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/favicon/SKILL.md
Commit: 48405aa

Reviewed: about 9 hours ago

Table of Contents

Discovery Implementation Validation

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.