CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

svg-inline

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

Quality

77%

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/svg-inline/SKILL.md
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 review skill body: concrete check/fix procedures, a coherent workflow with a before/after verification step, and clean one-level progressive disclosure to references/rule.md. The main cost is token duplication — the intro repeats the reference file's rationale and the Explain section teaches SVG trade-offs Claude already knows.

Suggestions

Cut the "Explain" section's general SVG trade-off tutorial down to the one-line decision rule (inline only for CSS/JS interactivity; otherwise <img> or sprite), since references/rule.md already carries the full rationale and decision table.

Replace the duplicated intro paragraph with a one-sentence statement of the rule and rely on the existing reference link for the "why".

Add the concrete SVGO command (e.g., `npx svgo input.svg`) and a re-measure step after fixes to close the actionability and validation gaps in the Fix workflow.

DimensionReasoningScore

Conciseness

The body is mostly tight ("Keep inline SVGs under 1KB (ideally under 500 bytes) after SVGO optimisation"), but the "Explain" section restates well-known trade-offs Claude already knows ("Inline SVG allows CSS styling (fill, stroke) and JavaScript animation on individual paths, which external SVG files or <img> elements cannot support"), and the intro paragraph duplicates the "Why It Matters" text in references/rule.md verbatim. This matches the 3 anchor ("mostly efficient but includes some unnecessary explanation or could be tightened") better than 4, where such redundancy would be only a minor trim.

3 / 5

Actionability

The Check and Fix sections give concrete, executable instruction — "Measure its character count—flag any over 1KB", "look for redundant attributes, inline styles that could be CSS classes, or editor comments", "extract to .svg file and reference with <img src='illustration.svg' alt='...'>", "use SVGR to import SVGs as components" — with minor gaps: no actual SVGO command is given in the body (it lives in the reference), and "Show before/after size comparison" names the step without showing how. Fits the 4 anchor ("mostly executable guidance; concrete code or commands with minor gaps") rather than 5.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sequence is coherent and ordered per-SVG (measure, check reuse, check SVGO, check inline need, then apply the matching fix), and the Fix step "Show before/after size comparison" acts as an explicit verification checkpoint. It stops short of 5 because there is no feedback loop (e.g., re-measure and re-flag if the extracted file still exceeds the budget) and no explicit validation that the page still renders correctly after extraction. This is a review/reporting skill, not a destructive or batch operation, so the workflow cap at 3 does not apply.

4 / 5

Progressive Disclosure

The body is a ~46-line overview with well-organized sections (Quick Reference, Check, Fix, Explain, Code Review) and a single clearly signaled, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — which exists and contains the deeper code examples and decision table. This matches the 5 anchor ("clear overview with well-signaled one-level-deep references; content appropriately split") and also fits the simple-skill note allowing 5 for short, well-organized skills.

5 / 5

Total

16

/

20

Passed

Description

75%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 solid description with an explicit "Use when..." trigger, a clear check-oriented what, and distinctive inline-SVG terminology. Its main weaknesses are the awkward embedded rule title in the trigger clause, check-only action coverage, and a few missing natural synonyms like "optimize" or "SVGO".

Suggestions

Rewrite the when-clause into natural user phrasing, e.g., "Use when reviewing inline SVGs, icon markup, or image delivery in HTML/components" instead of embedding the rule title mid-sentence.

Add a few common trigger synonyms ("SVG optimization", "SVGO", "SVG sprites") and a fix-side action verb (e.g., "Extract oversized inline SVGs to external files or components") to round out coverage.

Trim the generic "CDN or build transforms" wording, which overlaps with unrelated delivery/asset skills, in favor of SVG-specific terms.

DimensionReasoningScore

Specificity

The description lists several concrete actions — "Check encoded size, rendered size, loading strategy, and above-the-fold impact together" plus "reviewing image assets, markup, and CDN or build transforms" — but coverage is check-only; the skill's fix-side actions (extract to file, sprites, SVGO) are absent, leaving minor gaps. This fits the 4 anchor ("lists several specific actions; minor gaps") better than 5, whose comprehensive multi-action coverage is not met, and better than 3, since more than 1-2 concrete actions are named.

4 / 5

Completeness

Both parts are explicit: the what is "Check encoded size, rendered size, loading strategy, and above-the-fold impact together" and the when is the "Use when reviewing image assets, markup, and CDN or build transforms related to..." clause. It does not reach 5 because the when-clause embeds the rule title awkwardly ("related to Manage inline SVG size and complexity") rather than giving crisp user-facing trigger phrases, and the what covers only checking, not remediation — matching the 4 anchor ("both present; when could be more explicit or specific"). The "Use when..." clause is present, so no cap at 3 applies.

4 / 5

Trigger Term Quality

Natural terms a reviewer would say are present — "inline SVG size and complexity", "image assets", "markup", "CDN or build transforms", "loading strategy", "above-the-fold" — giving good keyword coverage. A few common variations are missing (e.g., "SVG optimization", "SVGO", "sprites", "icons"), so it falls just short of the 5 anchor's "comprehensive coverage... including synonyms and file extensions" but is clearly above 3's "missing common variations".

4 / 5

Distinctiveness Conflict Risk

The niche is clear — inline SVG size and complexity with checks like "encoded size, rendered size, loading strategy" — and unlikely to trigger for unrelated skills. However, the broad opening terms "image assets... and CDN or build transforms" create minor overlap risk with sibling image-optimization and delivery skills in the same category, matching the 4 anchor ("mostly distinct; minor overlap risk with closely related skills") rather than 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/svg-inline/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.