svg-optimization

Use when reviewing image assets, markup, and CDN or build transforms related to Optimize SVG files. Check encoded size, rendered size, loading strategy, and above-the-fold impact together.

Quality

50%

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/svg-optimization/SKILL.md

Quality

Content

38%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 as a thin overview that correctly delegates detail to a real references/rule.md file, so progressive disclosure is strong. However it is padded with concepts Claude already knows and lacks any executable command or code in the body itself, weakening conciseness and actionability.

Suggestions

Cut or trim the opening paragraph and the repeated 50-80% claim across Quick Reference, Fix, and Explain; Claude already understands SVG bloat.

Add at least one concrete executable snippet in the Fix section (e.g. `svgo input.svg -o output.svg` or a minimal svgo.config.js) instead of deferring all runnable guidance to the reference.

Add a brief verification step in the Check/Fix flow (e.g. visually compare optimized vs original, confirm viewBox/accessibility attributes preserved) to give the workflow an explicit checkpoint.

Dimension	Reasoning	Score
Conciseness	The body restates context Claude already knows ('SVGs exported from design tools contain unnecessary metadata... often cutting file size in half'), repeats the 50-80% figure across Quick Reference, Fix, and Explain sections, and recapitulates metadata-removal concepts that the reference file already covers, making it noticeably padded.	2 / 5
Actionability	The Check/Fix/Explain sections give only high-level hints ('Optimize SVG files using SVGO or similar tools') with no executable command, config, or code in the body itself; concrete runnable guidance is deferred entirely to the reference file.	2 / 5
Workflow Clarity	It lists distinct phases (Check, Fix, Explain, Code Review) giving a rough sequence, but there are no validation checkpoints and no verify-after-optimizing loop in the body; the cap-for-missing-validation guidance does not apply because this is not a destructive/batch operation, so 3 rather than lower.	3 / 5
Progressive Disclosure	The body is a lean overview with a single clearly signaled one-level-deep pointer ('see references/rule.md'), the referenced file exists, and bulk detail is correctly offloaded there; only minor organization gaps (the trailing rule-page URL duplicates the frontmatter url) keep it from a 5.	4 / 5
	Total	11 / 20 Passed

Description

62%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 third-person, has an explicit 'Use when' trigger, and scopes a clear niche around SVG optimization review. Its main weaknesses are partial trigger-term coverage (missing common synonyms like 'SVG files', '.svg', 'svgo', 'icons') and review-oriented rather than operationally specific action language.

Suggestions

Add natural trigger synonyms users would actually say, e.g. 'SVG files', '.svg', 'icons', or 'svgo', to broaden keyword coverage.

Sharpen the 'what' from review framing to concrete actions, e.g. 'Optimize SVG files by stripping editor metadata and redundant attributes, preserving viewBox and accessibility attributes.'

Tighten the 'when' clause with concrete user phrasings such as 'Use when the user asks to optimize or shrink SVGs, icons, or .svg assets.'

Dimension	Reasoning	Score
Specificity	It names the domain (SVG image assets, markup, CDN/build transforms) and several concrete review actions ('Check encoded size, rendered size, loading strategy, and above-the-fold impact'), but the actions are review-oriented and somewhat generic rather than a comprehensive list of distinct operations.	3 / 5
Completeness	It has an explicit 'Use when...' trigger clause and a clear 'what' (reviewing SVG asset optimization across encoded/rendered size and loading), so both what and when are present, though the 'when' leans on the rule title rather than concrete user phrasings.	4 / 5
Trigger Term Quality	It surfaces relevant terms ('image assets', 'markup', 'CDN or build transforms', 'SVG') but omits common natural phrasings and synonyms a user would say (e.g. 'SVG files', 'icons', '.svg', 'svgo'), so keyword coverage is partial.	3 / 5
Distinctiveness Conflict Risk	The focus on SVG optimization with size/loading/above-the-fold framing is a fairly distinct niche with only minor overlap risk against broader image-optimization skills.	4 / 5
	Total	14 / 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/svg-optimization/SKILL.md
Commit: 30756a7

Reviewed: 5 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.