CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

flashing-content

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

Quality

71%

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/flashing-content/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, concise overview with a clear check/fix/explain workflow and exemplary progressive disclosure to a single verified reference file. Its main weakness is actionability: the concrete thresholds are present, but no specific measurement tool or command is named in the body itself, and there is minor duplication between the Quick Reference and Check sections.

Suggestions

Name a concrete measurement method instead of "animation tools" — e.g. a specific tool or a quick way to compute flash frequency from an animation-duration value (0.2s duration = 5 flashes/second).

Remove the duplication between Quick Reference and Check (the GIF/video/CSS-animation testing line and the 3-60 Hz fact each appear twice in ~35 lines).

Inline one small executable example (e.g. the dangerous vs. safe CSS animation snippet) so the body is actionable without opening the reference file.

DimensionReasoningScore

Conciseness

The body is lean and well-organized, but the Quick Reference bullets are repeated nearly verbatim in the Check section ("Test animated GIFs, videos, and CSS animations for rapid flashing" appears twice), and the 3-60 Hz / photosensitive-epilepsy fact is stated in both the intro and the Explain section.

4 / 5

Actionability

Concrete numeric criteria are given ("no content flashes more than 3 times per second", "less than 25% of the viewport"), but the body contains no executable code or commands, and "Use animation tools to measure flash frequency" names no specific tool, leaving key details to the reference file.

3 / 5

Workflow Clarity

A clear Check → Fix → Explain → Code Review sequence is present with verification mentioned ("note how to verify the fix with browser accessibility tooling or assistive tech"), but the verification checkpoint is not concrete — no specific tool or command is named, a minor validation gap.

4 / 5

Progressive Disclosure

The skill is under 50 lines with well-organized sections and a single clearly signaled, one-level-deep reference: "For full implementation details, code examples, and framework-specific guidance, see references/rule.md" — and that file exists with exactly that content (203 lines including CSS examples and framework guidance).

5 / 5

Total

16

/

20

Passed

Description

58%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 has an explicit "Use when..." trigger and names several concrete inspection actions, but the actions are generic accessibility boilerplate misaligned with the skill's actual purpose (flash frequency and viewport-area thresholds), and it lacks natural trigger synonyms like animation, strobe, or blinking. It is serviceable but below the quality of the rubric's top examples.

Suggestions

Rewrite the action clause around what this skill actually does, e.g. "Check that content flashes no more than 3 times per second, that flashing areas stay under 25% of the viewport, and that no red flashing is present, per WCAG 2.3.1."

Add natural trigger synonyms users would say: "flashing", "strobe", "blinking", "rapid animation", "GIFs/videos", "photosensitive epilepsy", "WCAG 2.3.1".

Drop the boilerplate keyboard/focus/screen-reader inspection language (or trim it to what is genuinely relevant) so the description is distinguishable from sibling accessibility-rule skills that share this template.

DimensionReasoningScore

Specificity

The description lists several concrete inspection actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"), but these are generic accessibility-review verbs; the domain-specific actions for flashing content (measuring flash frequency, checking the 25%-viewport area threshold) are absent, so coverage is not comprehensive.

3 / 5

Completeness

Both "what" (check native semantics, inspect keyboard behavior, focus flow, accessible names, screen-reader output) and "when" ("Use when reviewing rendered HTML, interactive components, or design-system patterns related to...") are present, but the when-clause embeds the capitalized rule title rather than natural concrete trigger phrases, so it could be more explicit.

4 / 5

Trigger Term Quality

It contains some relevant keywords ("flashing", "seizure", "rendered HTML") but misses common natural variations and synonyms users would actually say, such as "animation", "strobe", "blinking", "GIF", "video", or "WCAG".

3 / 5

Distinctiveness Conflict Risk

The flashing/seizure domain itself is distinct, but the boilerplate trigger contexts (keyboard behavior, focus flow, screen-reader output) would overlap heavily with sibling accessibility skills that share this template, so it could still trigger for the wrong accessibility skill.

3 / 5

Total

13

/

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/flashing-content/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.