CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

81%

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

SKILL.md
Quality
Evals
Security

Quality

Content

71%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.

A well-structured overview body with excellent progressive disclosure: it stays lean, uses clear sections, and correctly pushes all executable SVGO commands and configs into a real, one-level-deep reference file. The weakness is that the body's own Check/Fix guidance stays generic, so an agent reading only SKILL.md knows what to do conceptually but not how to execute or verify without opening the reference.

Suggestions

Inline one copy-paste-ready command in the Fix section (e.g. `svgo input.svg -o output.svg` or a config-preserving variant) so the body is executable on its own.

Make the Check section concrete: name what to look for (editor metadata comments, `<!-- Generator: ... -->`, unused defs, width/height without viewBox) instead of "unnecessary metadata and formatting".

Add an explicit verification cue to the Fix step (e.g. visually compare optimized vs original, confirm viewBox/title preserved) rather than only the DevTools mention in Code Review.

DimensionReasoningScore

Conciseness

The body is lean overall — short sectioned checklists with no tutorial padding — but has minor trimmable redundancy: the 50-80% size-reduction claim appears in both "SVGO can reduce SVG file size by 50-80%" and "Explain how SVG optimization can reduce file sizes by 50-80%", and the intro sentence re-explains why SVG optimization matters, which Claude already knows. This matches anchor 4 (efficient, minor over-explanation) better than anchor 3's more substantial bloat.

4 / 5

Actionability

Guidance in the body is high-level — "Optimize SVG files using SVGO or similar tools to reduce file size" and "Check if SVG files are optimized by removing unnecessary metadata and formatting" — with no commands or concrete check criteria in the body itself; the executable detail (svgo CLI, configs) is entirely deferred to references/rule.md. This sits between anchor 2 (high-level hints only) and anchor 4 (mostly executable): some concrete anchors exist ("Preserve viewBox and accessibility attributes", the named tool SVGO), but key execution details are missing from the body.

3 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence gives a clear order for this simple single-purpose skill, and a verification cue is present ("describe how to confirm the fix in DevTools"), matching anchor 4's clear sequence with most checkpoints. Not 5 because the Check step never says how to detect unoptimized SVGs and the Fix step has no validation of the optimized output in the body; not 3 because the sequence is coherent and a confirmation step is explicitly called for.

4 / 5

Progressive Disclosure

The body is under 50 lines, cleanly sectioned, and defers all implementation detail via a single well-signaled, one-level-deep pointer: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and references/rule.md exists and delivers exactly that content with no further nesting. This matches anchor 5 and the rubric's simple-skill exception for well-organized short skills.

5 / 5

Total

16

/

20

Passed

Description

83%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, well-scoped "Use when" trigger and a concrete list of review dimensions (encoded/rendered size, loading strategy, above-the-fold impact). Its main gaps are the absence of the core optimizing action as a stated capability and missing natural synonyms like SVGO or vector graphics.

Suggestions

State the primary capability explicitly, e.g. "Optimizes SVG files by removing editor metadata and redundant code" before the Use-when clause.

Add natural synonyms users actually say — "SVGO", "vector graphics", ".svg" — to the trigger phrase.

Trim the generic "image assets, markup, and CDN or build transforms" framing slightly so the SVG-specific niche dominates and reduces overlap with sibling image rules.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "reviewing image assets, markup, and CDN or build transforms" and "Check encoded size, rendered size, loading strategy, and above-the-fold impact together" — which is more than the 1-2 actions of anchor 3, but it stops short of anchor 5's comprehensive coverage because it never states the core capability (e.g., optimizing SVGs with SVGO, removing metadata) as an explicit action.

4 / 5

Completeness

Both questions are explicitly answered: the "when" is a direct trigger clause ("Use when reviewing image assets, markup, and CDN or build transforms related to Optimize SVG files") and the "what" is concrete ("Check encoded size, rendered size, loading strategy, and above-the-fold impact together"), matching the anchor 5 pattern of explicit what + when with concrete trigger phrases. Not 4 because the "when" is already as explicit and specific as the good examples.

5 / 5

Trigger Term Quality

Natural terms users would say are present: "image assets", "markup", "CDN", "build", "Optimize SVG files", "loading strategy". Not anchor 5 because common variations and synonyms are missing — "SVGO", "vector graphics", ".svg" — while still better than anchor 3's partial coverage.

4 / 5

Distinctiveness Conflict Risk

The SVG-optimization niche is distinct ("Optimize SVG files"), but the broad framing "reviewing image assets, markup, and CDN or build transforms" creates minor overlap risk with sibling image-delivery rules (e.g., image format, lazy loading, CDN caching), matching anchor 4 rather than anchor 5's minimal-conflict profile.

4 / 5

Total

17

/

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