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

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

Quality

Content

57%

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

A lean, well-structured overview that delegates implementation detail to a real one-level-deep reference, but the body itself lacks executable guidance and validation checkpoints, and the Check/Fix/Explain template adds mild redundancy.

Suggestions

Add at least one concrete executable command to the Fix section (e.g. `svgo input.svg -o output.svg`) so the body is actionable before consulting the reference.

Include an explicit verification step (e.g. visually compare the optimized SVG against the original and confirm animations/accessibility attributes survive) to satisfy the validation checkpoint the rubric expects for a file-modifying operation.

Consolidate the redundant Check/Fix/Explain framings so the 50-80% reduction figure and the 'remove metadata' idea each appear once.

Dimension	Reasoning	Score
Conciseness	The body is short and avoids long conceptual explanations, but the templated Check/Fix/Explain sections restate the same 'optimize SVGs to reduce size' idea redundantly (e.g. the 50-80% figure appears in both Quick Reference and Explain).	2 / 3
Actionability	The body names the specific tool (SVGO) and gives concrete review instructions ('Flag exact files or components... describe how to confirm the fix in DevTools'), but provides no executable commands or config in the body itself, deferring all code to references/rule.md.	2 / 3
Workflow Clarity	Check/Fix/Code Review sections imply a loose sequence, but there is no explicit validation/verification checkpoint in the body for an operation that can break SVG rendering; per the rubric, missing validation for a destructive/batch operation caps this at 2.	2 / 3
Progressive Disclosure	The body is a concise overview with a clearly signaled one-level-deep reference ('see references/rule.md' for full implementation details), and that reference file exists with the detailed content — an appropriately split, easy-to-navigate structure.	3 / 3
	Total	9 / 12 Passed

Description

67%

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 complete description with an explicit 'Use when' trigger covering both what and when, but it is framed as a review/checklist task rather than the skill's actual optimization actions and uses broad peripheral terms that raise overlap risk.

Suggestions

Lead with the skill's concrete optimization actions (e.g. 'Optimize SVG files with SVGO, configure plugins, and integrate into the build process') rather than only review/check verbs.

Add common trigger variations users would naturally say — 'SVG', 'SVGs', '.svg', 'vector graphics' — alongside 'SVG files'.

Tighten the peripheral scope (image assets, CDN, build transforms) so the trigger stays anchored to SVG optimization and does not conflict with general image or build-tooling skills.

Dimension	Reasoning	Score
Specificity	It names the domain (SVG files, image assets, markup, CDN/build transforms) and several concrete checks ('encoded size, rendered size, loading strategy, and above-the-fold impact'), but the verbs are limited to 'reviewing'/'Check' and it omits the skill's core optimization actions, so it is not comprehensive.	2 / 3
Completeness	It explicitly answers both what ('Check encoded size, rendered size, loading strategy, and above-the-fold impact together') and when ('Use when reviewing image assets, markup, and CDN or build transforms related to Optimize SVG files') with an explicit trigger clause.	3 / 3
Trigger Term Quality	It includes relevant natural terms ('SVG files', 'image assets') and an explicit 'Use when' trigger, but misses common variations a user might say such as 'SVG', 'SVGs', '.svg', or 'vector graphics'.	2 / 3
Distinctiveness Conflict Risk	'Optimize SVG files' is a fairly specific niche, but the peripheral 'image assets, markup, CDN or build transforms' language broadens the trigger and could overlap with general frontend image-optimization or build-configuration skills.	2 / 3
	Total	9 / 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/svg-optimization/SKILL.md
Commit: 48405aa

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