CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

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

76%

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

The body is a well-structured, actionable accessibility review skill: concrete check criteria, specific fixes, a clear Check/Fix/Explain flow, and clean one-level progressive disclosure to a real, relevant references/rule.md. Its main weakness is redundancy — the rationale appears twice and the Check section restates the Quick Reference — which could be tightened without losing anything.

Suggestions

Merge the Quick Reference bullets into the Check section (or vice versa) — they state the same criteria (no autoplay, muted by default, accessible pause controls, 5-second rule) almost word-for-word.

Cut either the opening paragraph or trim the Explain section, since both make the identical point about screen readers, startled users, and bandwidth.

In the Code Review section, name concrete verification tools (e.g., axe DevTools, Lighthouse, or a specific screen reader) instead of the generic "browser accessibility tooling or assistive tech".

DimensionReasoningScore

Conciseness

Mostly efficient but with real duplication: the intro ("Autoplaying audio drowns out screen reader speech, startles users, and wastes bandwidth") restates the "Explain" section nearly verbatim, and "Check" ("Verify no audio or video autoplays on page load... muted by default and pause controls are immediately accessible") repeats the Quick Reference bullets. Not 4 because the redundancy exceeds minor over-explanation; not 2 because the document is short and contains no basic-concept tutorials.

3 / 5

Actionability

Concrete, executable guidance throughout: "Remove autoplay attributes from media elements", "add muted attribute", "Autoplay should stop after 5 seconds or provide stop mechanism", "pause controls are immediately accessible via keyboard within the first few tab stops". Not 5 because the body has no code examples (delegated to references/rule.md) and verification guidance ("browser accessibility tooling or assistive tech") leaves tools unspecified.

4 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence with concrete acceptance criteria (muted by default, first few tab stops, 5-second limit). Not 5 because the fix-verification step ("note how to verify the fix with browser accessibility tooling or assistive tech") is vague and there is no explicit re-check loop; not 3 because checkpoints are largely present and this is not a destructive or batch operation requiring a cap.

4 / 5

Progressive Disclosure

SKILL.md serves as a lean overview with a single, well-signaled, one-level-deep reference — "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — and the referenced file exists in the bundle with exactly that content (code examples, rationale, accessible player guidance). Content is appropriately split with easy navigation; no nesting or buried references.

5 / 5

Total

16

/

20

Passed

Description

71%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 follows the "Use when..." convention with explicit what/when structure and several concrete review actions, but it reads as template boilerplate grafted onto the rule name. Its generic accessibility phrasing weakens distinctiveness against sibling skills and omits the natural topic keywords (audio, video, muted, pause) users would actually say.

Suggestions

Add rule-specific natural keywords to the description — e.g., "audio", "video", "muted", "autoplay attribute", "pause/stop controls" — so trigger coverage matches what users actually say when facing this issue.

Replace the generic action list with actions specific to this rule (e.g., "verify no audio/video autoplays on load, confirm autoplaying video is muted by default, and check pause controls are keyboard-accessible") to sharpen the "what" and reduce overlap with sibling accessibility skills.

State the trigger in terms of the user's situation rather than circularly referencing the rule name — e.g., "Use when a page autoplays audio or video or when reviewing media elements for accessibility".

DimensionReasoningScore

Specificity

Lists several concrete actions — "reviewing rendered HTML, interactive components, or design-system patterns", "Check native semantics first", "inspect keyboard behavior, focus flow, accessible names, and screen-reader output" — with minor gaps in coverage. Not 5 because the actions are generic accessibility-review steps and omit autoplay-specific actions (e.g., verifying muted autoplay or pause controls); not 3 because well over 1-2 concrete actions are explicitly stated.

4 / 5

Completeness

Both parts are present: the "what" ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") and an explicit "Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid autoplaying media" trigger. Not 5 because the "what" is boilerplate not specific to this rule (no media-specific actions) and the "when" is circular ("related to Avoid autoplaying media").

4 / 5

Trigger Term Quality

Good natural-keyword coverage: "Avoid autoplaying media", "rendered HTML", "interactive components", "keyboard behavior", "screen-reader output" are phrases a user would plausibly say. Not 5 because the most common topic terms — "audio", "video", "muted", "pause controls" — are absent; not 3 because coverage goes well beyond "some relevant keywords".

4 / 5

Distinctiveness Conflict Risk

Only the rule name "Avoid autoplaying media" distinguishes this skill; the remainder ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output") is template text shared with sibling accessibility skills, creating real overlap risk. Not 4 because the boilerplate actions would match many similar a11y skills; not 2 because the explicit rule name does anchor a niche.

3 / 5

Total

15

/

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