autoplay-media

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid autoplaying media. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

67%

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/autoplay-media/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.

The body is a clean, well-organized overview with good progressive disclosure to a real reference file, but it leans on prose-only guidance and restates rationale Claude already knows, leaving actionability and workflow validation somewhat implicit.

Suggestions

Add one small inline code example (e.g. the muted/controls video snippet) so the body is actionable without requiring the reference for the common case.

Make the validation loop explicit in the Check/Fix flow — verify, then re-check after fixing — rather than leaving checkpoints implicit.

Trim the duplicated why-it-matters text between the intro and the 'Explain' section to improve token efficiency.

Dimension	Reasoning	Score
Conciseness	Mostly lean and sectioned, but the intro and 'Explain' sections restate the same why-it-matters rationale ('drowns out screen reader speech, startles users, wastes bandwidth') that Claude already knows; not a 3 because redundant explanation of known concepts occupies tokens that do not earn their place.	2 / 3
Actionability	Gives concrete prose direction ('Remove autoplay attributes', 'add muted attribute') but delegates all executable code and framework guidance to references/rule.md; not a 3 because the body itself offers no copy-paste-ready example, and not a 1 because the guidance is specific enough to act on.	2 / 3
Workflow Clarity	The Check/Fix/Explain/Code Review sections imply a review sequence and the Check step functions as a manual verification, but there is no explicit fix-then-revalidate feedback loop; not a 3 because validation checkpoints are implicit rather than explicit.	2 / 3
Progressive Disclosure	The body is a concise overview that clearly signals a single one-level-deep reference ('see references/rule.md') which exists as a real file; not a 2 because navigation is clearly signaled and content is appropriately split rather than inlined.	3 / 3
	Total	9 / 12 Passed

Description

77%

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 well-structured with an explicit Use-when trigger and concrete review actions, but its trigger terms describe a generic accessibility-review pattern shared across many rules rather than topic-specific natural language, raising conflict risk.

Suggestions

Add topic-specific natural trigger terms such as 'autoplay', 'audio', 'video', or 'media playback' so the skill surfaces when users describe the actual problem.

Differentiate the trigger from sibling accessibility skills by foregrounding the autoplay-media behavior rather than the generic review activity.

Keep the concrete action list but tighten the awkward embedded rule name 'related to Avoid autoplaying media' into a smoother clause.

Dimension	Reasoning	Score
Specificity	Names multiple concrete actions — 'inspect keyboard behavior, focus flow, accessible names, and screen-reader output' — rather than vague language; not the level below because it lists several specific review activities, not just a domain.	3 / 3
Completeness	Explicitly answers both — an explicit 'Use when reviewing ...' trigger clause and concrete what-to-do actions; not a 2 because the 'when' guidance is present and explicit, not merely implied.	3 / 3
Trigger Term Quality	Includes relevant terms ('rendered HTML, interactive components, or design-system patterns') but the triggers describe a generic accessibility-review activity rather than the topic's own natural terms (autoplay, audio, video, media); not a 3 because users needing this rule would not naturally say these phrases.	2 / 3
Distinctiveness Conflict Risk	Names the specific rule ('related to Avoid autoplaying media') but the shared trigger pattern ('reviewing rendered HTML ... interactive components ... design-system patterns') would overlap with sibling accessibility skills; not a 3 because the triggers are templated and not unique to this rule.	2 / 3
	Total	10 / 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/autoplay-media/SKILL.md
Commit: 48405aa

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