favicons

Use when reviewing templates, rendered HTML, or shared components related to Implement favicons for all devices. Validate the final browser-facing markup, not just the source framework abstraction.

Quality

62%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/favicons/SKILL.md

Quality

Content

61%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 skill body is concise and well-structured as an overview that defers detail to references/rule.md. It is held back by limited actionability (no inline executable HTML/code examples) and implicit rather than explicit validation checkpoints in the workflow.

Suggestions

Add a copy-paste-ready HTML snippet showing the canonical favicon markup (link rel='icon', apple-touch-icon, SVG with media query for dark mode) so guidance is executable without opening the reference.

Make the workflow's verification step explicit, e.g., 'Validate: open the rendered page and confirm each declared icon path resolves with HTTP 200 and correct dimensions.'

Briefly state what references/rule.md contains (e.g., 'full size matrix and framework-specific snippets') so the reader knows when to consult it.

Dimension	Reasoning	Score
Conciseness	The body is brief and well-organized with minimal over-explanation, only stating the rationale and concrete requirements; it is slightly above the 'efficient; minor instances of over-explanation' anchor because the 'Explain' section restates an obvious benefit (brand recognition/trust).	4 / 5
Actionability	It gives high-level guidance ('Generate and implement a complete favicon set including ICO, PNG, SVG, and mobile/PWA icons with proper HTML declarations') and points to a reference, but provides no executable code or copy-paste HTML snippets inline, fitting the 'some concrete guidance but incomplete; pseudocode/missing key details' anchor.	3 / 5
Workflow Clarity	Check/Fix/Explain/Code Review sections imply a sequence but there are no explicit validation checkpoints or feedback loops, and the destructive/batch cap does not apply here; this matches 'steps listed but validation gaps; checkpoints missing or implicit'.	3 / 5
Progressive Disclosure	The body is a concise overview that signals a single one-level-deep reference ('see references/rule.md', which exists) plus the source rule page; structure is good and navigation is clear, with only minor gaps in signaling the reference's contents.	4 / 5
	Total	14 / 20 Passed

Description

63%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 clearly states both what to do (validate rendered favicon markup) and when to use it (reviewing templates/HTML/components for the favicons rule), with a proper 'Use when' trigger. It is slightly under-comprehensive on concrete actions and could add a few natural synonyms (icons, manifest, apple-touch).

Dimension	Reasoning	Score
Specificity	The description names the domain ('reviewing templates, rendered HTML, or shared components related to Implement favicons') and one concrete action ('Validate the final browser-facing markup'), but does not enumerate multiple specific actions, matching the 'domain and 1-2 concrete actions, but not comprehensive' anchor.	3 / 5
Completeness	It has an explicit 'Use when...' trigger clause and a clear 'what' ('Validate the final browser-facing markup, not just the source framework abstraction'), satisfying both what and when, though the 'when' could be slightly more specific about favicon scenarios.	4 / 5
Trigger Term Quality	It includes natural phrases users would say ('reviewing templates', 'rendered HTML', 'shared components', 'favicons') with good keyword coverage; a few natural synonyms (e.g., 'icons', 'manifest') are missing, placing it just above the midpoint anchor.	4 / 5
Distinctiveness Conflict Risk	The favicon/template-review niche is mostly distinct with a clear trigger tied to 'Implement favicons for all devices'; minor overlap risk exists with general HTML-review skills, fitting the 'mostly distinct; minor overlap risk' anchor.	4 / 5
	Total	15 / 20 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/favicons/SKILL.md
Commit: 30756a7

Reviewed: 22 days 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.