animated-content

Use when auditing slow page loads, heavy assets, or rendering delays related to Convert animated GIFs to video. Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes.

Quality

73%

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/animated-content/SKILL.md

Quality

Content

72%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 skill body is a tight, well-structured overview that defers detail to a real one-level reference file and gives concrete video-tag guidance. Its main weakness is the absence of explicit validation checkpoints in the GIF-to-video replacement workflow.

Suggestions

Add a verification checkpoint after the Fix step (e.g., compare file sizes before/after and confirm the <video> autoplays in the target browsers).

Include a minimal executable example — a concrete ffmpeg conversion command and a sample <video> tag — to push actionability from mostly-executable to copy-paste ready.

Trim the opening restatement of why GIFs are heavy, since the reference file already covers it, to remove the mild redundancy.

Dimension	Reasoning	Score
Conciseness	The body is lean with sectioned Quick Reference, Check, Fix, Explain, and Code Review blocks and no padding about what GIFs are; only the opening restatement of the problem is mildly redundant, keeping it just below the fully lean 5 anchor.	4 / 5
Actionability	The Fix step gives concrete, specific guidance — '<video> tag with autoplay, loop, muted, and playsinline attributes' and MP4/WebM formats — which is actionable without code; it stops short of an executable conversion command or example tag, so it is mostly executable rather than copy-paste ready.	4 / 5
Workflow Clarity	The Check → Fix → Explain → Code Review sections provide a recognizable sequence, but there are no explicit validation checkpoints (e.g., confirm the new file is smaller, verify the video autoplays) for an asset-replacement workflow.	3 / 5
Progressive Disclosure	The body is a concise overview with well-organized sections and a single clearly signaled one-level-deep reference to references/rule.md, which exists as a real file, matching the clear-overview-with-easy-navigation anchor.	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.

The description explicitly pairs a 'Use when' trigger with concrete auditing actions and named measurement tools, clearly answering both what and when. It is slightly generic in its opening framing and could add more natural synonyms (GIF, animated) to fully reach the top anchors.

Suggestions

Lead with the concrete capability ('Convert large animated GIFs to MP4/WebM video to cut page weight') before the auditing framing so the 'what' is unmistakable.

Add natural trigger synonyms users would say — 'animated GIF', 'GIF', 'page weight', 'Largest Contentful Paint' — alongside 'slow page loads'.

Tighten the trigger so it is clearly scoped to GIF/video issues rather than general performance auditing, reducing overlap with broader performance skills.

Dimension	Reasoning	Score
Specificity	Names the performance domain and several concrete actions ('auditing slow page loads, heavy assets, or rendering delays', 'Verify the actual bottleneck in DevTools, Lighthouse, or field data before recommending changes'), with only minor coverage gaps relative to the comprehensive 5 anchor.	4 / 5
Completeness	It states both what (audit performance issues tied to GIF-to-video conversion) and when via an explicit 'Use when...' clause; the trigger phrasing could be more specific, so it sits above the midpoint rather than at 5.	4 / 5
Trigger Term Quality	Natural user phrases like 'slow page loads', 'heavy assets', and 'rendering delays' are present, but common synonyms/extensions such as 'GIF', 'animated GIF', or 'page weight' are underrepresented, leaving it just below comprehensive.	4 / 5
Distinctiveness Conflict Risk	The GIF-to-video niche is fairly distinct, but the lead-in framing around generic performance auditing creates minor overlap risk with broader web-performance skills.	4 / 5
	Total	16 / 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/animated-content/SKILL.md
Commit: 30756a7

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