CtrlK
BlogDocsLog inGet started
Tessl Logo

favicon

Generate favicons from a source image

58

Quality

68%

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 ./plugins/AI-Agents-Safe-Coding-Skills-claude/skills/favicon/SKILL.md

The canonical home for this skill is favicon in administrakt0r/AI-Agents-Safe-Coding-Skills

SKILL.md
Quality
Evals
Security

Quality

Content

82%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 highly actionable, with executable commands and concrete framework-specific snippets organized into a clear 8-step workflow. Its main gap is the absence of an output-verification checkpoint after the batch file generation, which a destructive/batch operation should ideally include.

DimensionReasoningScore

Conciseness

The body is task-focused with no padding about what favicons are or how ImageMagick works; every section delivers actionable reference (detection table, commands, snippets), with only minor stretches (the 12-framework table) that could be trimmed — fitting 'efficient; minor instances of over-explanation that could be trimmed'.

4 / 5

Actionability

It provides fully executable, copy-paste-ready magick commands with exact flags, cp commands, complete JSON manifest content, and framework-specific HTML/TS snippets covering the common cases (Rails, Next.js, static HTML), matching the 'fully executable; copy-paste ready' anchor.

5 / 5

Workflow Clarity

Steps 1–8 are clearly sequenced with explicit input checkpoints (verify magick installed via 'which magick', validate source exists and format, 'when in doubt ask') plus an Error Handling section, but it lacks a post-generation verification step confirming the output files were written, fitting 'clear sequence with most checkpoints present; minor validation gaps'.

4 / 5

Progressive Disclosure

The skill is a single cohesive file with well-organized section headers (Prerequisites, Steps 1–8, Error Handling) and no nested or buried references, but all content lives inline with no external reference split, fitting 'good structure; most content appropriately placed; minor organization gaps'.

4 / 5

Total

17

/

20

Passed

Description

53%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 is clear and distinct about what the skill does (generate favicons), but it is terse and entirely lacks a 'when to use it' trigger clause. Adding an explicit 'Use when...' clause with natural synonyms (app icon, .ico) would raise both completeness and trigger-term quality.

Suggestions

Add an explicit trigger clause, e.g. 'Use when the user asks to generate or create favicons, app icons, or site icons from an image.'

Include natural synonyms and file extensions users say — 'favicons, app icons, site icons, .ico' — to broaden trigger-term coverage.

Name the broader concrete actions (generate icon sizes, create webmanifest, inject HTML link tags) so the 'what' reads as comprehensive rather than a single action.

DimensionReasoningScore

Specificity

The description 'Generate favicons from a source image' names the domain (favicons) and one concrete action (generate), but offers only a single action with no breadth — matching the anchor for naming a domain plus 1-2 concrete actions without being comprehensive.

3 / 5

Completeness

It has a clear 'what' (generate favicons from a source image) but no 'when' / 'Use when...' clause at all; per the guidelines a missing trigger clause caps completeness at 3, matching the 'clear what, when missing' anchor.

3 / 5

Trigger Term Quality

'favicon' is a natural term a user would say, but the description omits common variations and synonyms (e.g., 'app icon', 'icons', '.ico'), placing it at 'some relevant keywords but missing common variations'.

3 / 5

Distinctiveness Conflict Risk

Favicon generation is a clear, narrow niche unlikely to conflict with unrelated skills, though the thin trigger phrasing leaves minor overlap risk with general image-handling skills, fitting 'mostly distinct; minor overlap risk' rather than the fully distinct 5 anchor.

4 / 5

Total

13

/

20

Passed

Validation

87%

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

Validation14 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

allowed_tools_field

'allowed-tools' contains unusual tool name(s)

Warning

frontmatter_unknown_keys

Unknown frontmatter key(s) found; consider removing or moving to metadata

Warning

Total

14

/

16

Passed

Repository
administrakt0r/AI-Agents-Safe-Coding-Skills
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.