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

80%

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

85%

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

The content is a well-organized, concise overview with a clearly signaled one-level-deep reference and an unambiguous review workflow. Its only weakness is actionability: guidance is descriptive rather than executable.

Suggestions

Add an executable code snippet or concrete command for generating a favicon set (e.g., an npx favicons invocation or the exact <link> HTML declarations to insert) to raise actionability from 2 to 3.

Dimension	Reasoning	Score
Conciseness	The body is lean with a compact Quick Reference spec and terse Check/Fix/Explain/Code Review sections, assuming Claude's competence without padding or explaining basic concepts.	3 / 3
Actionability	Concrete specs and tool names are present ('favicon.ico (32x32) + apple-touch-icon.png (180x180)', 'RealFaviconGenerator', 'favicons npm package') but Fix/Check describe rather than instruct, with no executable commands or copy-paste code.	2 / 3
Workflow Clarity	For a simple single-purpose review skill, the Check/Fix/Explain/Code Review sequence is clear and well-organized with an unambiguous review procedure, satisfying the simple-skill allowance.	3 / 3
Progressive Disclosure	The body is a concise overview deferring full details to references/rule.md (verified to exist), referenced one level deep with a clear navigation signal.	3 / 3
	Total	11 / 12 Passed

Description

75%

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 answers both what it does and when to use it with an explicit trigger clause and a distinct favicon niche. It is held back from a perfect score by limited action enumeration and missing common keyword variations.

Suggestions

Add a few more concrete actions (e.g., 'generate icon sets', 'declare HTML link tags', 'build manifest.json') to lift specificity from 2 to 3.

Broaden trigger terms with natural variations users would say, such as 'icons', '.ico', 'apple-touch-icon', and 'web manifest'.

Dimension	Reasoning	Score
Specificity	Names the favicon domain and concrete review actions ('reviewing templates, rendered HTML, or shared components', 'Validate the final browser-facing markup') but does not enumerate multiple distinct concrete actions, so it stops short of a 3.	2 / 3
Completeness	An explicit 'Use when...' clause states when to invoke it, and the body of the description states what it does (validate browser-facing favicon markup), covering both what and when.	3 / 3
Trigger Term Quality	Includes natural terms a user would say ('favicons', 'templates', 'rendered HTML', 'browser-facing markup') but misses common variations like 'icons', '.ico', 'apple-touch-icon', or 'manifest'.	2 / 3
Distinctiveness Conflict Risk	Scoped to favicon-related HTML markup review ('related to Implement favicons for all devices'), a clear niche unlikely to trigger for unrelated skills.	3 / 3
	Total	10 / 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/favicons/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.