CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

73%

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

Fix and improve this skill with Tessl

tessl review fix ./skills/favicons/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

57%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 body is well structured with an exemplary progressive-disclosure split to references/rule.md, but its instructional sections are vague restatements: Check and Fix lack executable steps and checkpoints, leaving the Quick Reference as the only concrete guidance. Tightening the filler and grounding Check/Fix in verifiable actions would lift the weakest dimensions.

Suggestions

Replace the vague Check section with concrete verification steps, e.g., inspect the served/built HTML head for icon link tags and compare against the required set (favicon.ico 32x32, apple-touch-icon.png 180x180, SVG with dark mode, manifest.json icons).

Trim or merge the Explain section, which restates the intro's motivation without adding actionable content.

Add a validation checkpoint to the review workflow, such as confirming findings against the rendered page rather than the source template.

DimensionReasoningScore

Conciseness

The Quick Reference is dense and earns its tokens, but the Check section ("Verify that all necessary favicon formats and sizes are implemented correctly for optimal display across different browsers, devices, and platforms") and the Explain section are vague restatements of the title that could be trimmed. Two of five sections being filler is more than the 'minor instances' of the anchor-4 example, but the rest is efficient.

3 / 5

Actionability

Some concrete guidance exists ("favicon.ico (32x32) + apple-touch-icon.png (180x180)", "manifest.json", "RealFaviconGenerator or favicons npm package"), but the Check and Fix sections give high-level direction without executable steps — the actual HTML declarations and code live only in references/rule.md. Not 4 because the body itself is not mostly executable guidance.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections give a rough sequence, but checkpoints are implicit — the Check section never says how or where to verify rendered output (e.g., inspect the served page or built HTML). Sequence present with missing checkpoints matches anchor 3, not anchor 4.

3 / 5

Progressive Disclosure

A short, well-sectioned overview that clearly signals a one-level-deep pointer — "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and that file exists and holds the implementation detail. The split is appropriate and navigation is easy, matching the anchor-5 structure.

5 / 5

Total

14

/

20

Passed

Description

78%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 and a concrete, distinctive statement of what the skill validates. Its main weakness is limited action coverage — two actions rather than a comprehensive list — and a few missing natural synonyms like 'site icon'.

Suggestions

List the concrete validation actions the skill performs (e.g., checks ICO/PNG/SVG declarations, apple-touch-icon, and manifest.json icon entries) to broaden action coverage.

Add one or two natural synonyms such as 'site icon' or 'touch icon' to widen trigger-term coverage.

DimensionReasoningScore

Specificity

Names the domain (favicons for all devices) and two concrete actions — "reviewing templates, rendered HTML, or shared components" and "Validate the final browser-facing markup, not just the source framework abstraction" — but coverage of what the skill does is not comprehensive. Not a 4 because only two actions are listed rather than several with minor gaps.

3 / 5

Completeness

Explicitly answers both: "Use when reviewing templates, rendered HTML, or shared components related to Implement favicons for all devices" states when with concrete trigger phrases, and "Validate the final browser-facing markup, not just the source framework abstraction" states what. Both are clear and specific, matching the anchor-5 example structure; the 'when' is already explicit so this is not the anchor-4 case.

5 / 5

Trigger Term Quality

Good natural keyword coverage: "templates", "rendered HTML", "shared components", "favicons", "browser-facing markup" are phrases users would naturally say. A few natural synonyms are missing (e.g., "site icon", "touch icon"), keeping it below the comprehensive anchor 5.

4 / 5

Distinctiveness Conflict Risk

The favicon qualifier carves a clear niche with distinct triggers, but the generic "reviewing templates, rendered HTML, or shared components" phrasing is shared with sibling HTML-review skills, creating minor overlap risk. Mostly distinct, so not 5.

4 / 5

Total

16

/

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/favicons/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.