CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

interstitials

Use when applies to CSS and JavaScript implementations of modals, overlays, pop-ups, cookie banners, newsletter sign-up dialogs, and promotional overlays. Check for `position: fixed`, `position: absolute` with large z-index, backdrop overlays, and JavaScript that shows modals on page load or shortly after. Consider both SEO impact (Google) and accessibility (WCAG focus management).

Quality

84%

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

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 with a clean Check/Fix/Explain workflow, specific thresholds and ARIA attributes, and correct one-level-deep reference usage. Its main weakness is redundancy — the Google penalty and exemption lists are stated twice and the Explain section re-teaches concepts Claude already knows.

Suggestions

Remove the duplicated statements in Explain (Google penalty exemptions already appear verbatim in Quick Reference) and cut the re-explanation of WCAG/ARIA dialog basics that Claude already knows, keeping only the rule-specific citations.

Make the deferred verification explicit: mention that references/rule.md contains a Verification checklist for confirming fixes in the rendered UI, so the workflow has an explicit post-fix checkpoint.

Tighten the qualitative checks by giving thresholds: replace "high z-index values" with a concrete cutoff and point to the focus-trap implementation in references/rule.md instead of "using a focus trap".

DimensionReasoningScore

Conciseness

The Google-penalty fact and the acceptable-interstitials exemption list ("age verification, legally required notices, login walls") each appear twice in the body (Quick Reference and Explain), and the Explain section re-states WCAG/ARIA dialog requirements Claude already knows. Mostly efficient, but more than minor trimming is needed — not 4; not 2 because the bulk is actionable specifics rather than padded explanation.

3 / 5

Actionability

Concrete, near-executable guidance throughout: "max-height 10-15% of viewport", "< 600px width", "role='dialog', aria-modal='true', aria-labelledby", Escape-key and focus-return steps. Not 5 because some checks stay qualitative ("high z-index values" with no threshold, "trap focus using a focus trap" with no implementation detail) and code lives only in the reference file.

4 / 5

Workflow Clarity

Clear Check → Fix → Explain → Code Review sequence with five explicit per-element checks and an explicit decision rule ("Flag dialogs that fail any of these checks"). Not 5 because verification of applied fixes is not in the body — it exists only in the reference file the body does not specifically point to for verification. Not 3 because the sequence and decision checkpoints are explicit, and this review workflow is not destructive/batch so the validation cap does not apply.

4 / 5

Progressive Disclosure

The ~45-line body is a well-organized overview (Quick Reference, Check, Fix, Explain, Code Review) that defers code examples and full implementation detail to a clearly signaled, one-level-deep reference ("see `references/rule.md`"). The referenced file exists and contains exactly the deferred material (CSS/HTML/JS examples, verification steps), so navigation is easy and the split is appropriate.

5 / 5

Total

16

/

20

Passed

Description

91%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 strong description with comprehensive natural trigger terms and explicit what/when guidance. Its only weaknesses are detection-only capability coverage and slightly awkward "Use when applies to" phrasing.

DimensionReasoningScore

Specificity

"Check for `position: fixed`, `position: absolute` with large z-index, backdrop overlays, and JavaScript that shows modals on page load" lists several specific, technical actions. Not 5 because coverage is detection-only — no remediation capability (alternatives, focus-management fixes) is mentioned, a minor gap.

4 / 5

Completeness

Explicitly answers both: "Use when applies to CSS and JavaScript implementations of modals, overlays, pop-ups..." (when, with concrete trigger phrases) and "Check for... Consider both SEO impact (Google) and accessibility (WCAG focus management)" (what). The awkward "Use when applies to" phrasing is grammatically odd but the trigger guidance remains explicit.

5 / 5

Trigger Term Quality

"modals, overlays, pop-ups, cookie banners, newsletter sign-up dialogs, and promotional overlays" is comprehensive natural-synonym coverage of exactly what users would say when they need this skill; no common variant is missing.

5 / 5

Distinctiveness Conflict Risk

A clear niche (interstitial CSS/JS patterns) with distinct triggers like "cookie banners" and "promotional overlays". Not 5 because "accessibility (WCAG focus management)" and general modal work could overlap with a dedicated accessibility or dialog-implementation skill.

4 / 5

Total

18

/

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/interstitials/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.