CtrlK
BlogDocsLog inGet started
Tessl Logo

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).

74

Quality

92%

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

85%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The body is well-structured, highly actionable, and properly splits detail into a one-level-deep reference. Its main weakness is conciseness: it re-explains well-known SEO/accessibility concepts and repeats the Google update across sections.

Suggestions

Collapse the redundant Google 2017 update mentions (Quick Reference, Check, Explain) into a single statement to remove repetition of a concept Claude already knows.

Trim the Explain section to only what is non-obvious — keep the WCAG SC numbers (2.1.2, 4.1.3) but drop the general re-explanation of why modal focus management matters.

Merge the intro paragraph into Quick Reference since both cover mobile/accessibility/SEO impact, eliminating overlapping prose.

DimensionReasoningScore

Conciseness

Mostly efficient but re-explains concepts Claude already knows (the 2017 Intrusive Interstitials Update, WCAG/ARIA dialog pattern) and repeats the Google update across Quick Reference, Check, and Explain, so it could be tightened.

2 / 3

Actionability

Provides concrete actionable guidance — specific selectors (position: fixed/absolute with high z-index), a concrete breakpoint (< 600px width), numeric fix constraints (max-height 10-15% of viewport), and exact ARIA attributes (role='dialog', aria-modal='true', aria-labelledby, Escape, focus return).

3 / 3

Workflow Clarity

The Check section is a numbered 5-point checklist culminating in the explicit validation step "Flag dialogs that fail any of these checks," and Fix is sequenced 1–4 with sub-steps, giving a clear review workflow.

3 / 3

Progressive Disclosure

SKILL.md is a well-sectioned overview that defers full implementation, code examples, and framework guidance to a single, clearly signaled one-level-deep reference at references/rule.md (verified to exist).

3 / 3

Total

11

/

12

Passed

Description

100%

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 specific, trigger-rich, and complete, clearly stating both what the skill does and when to use it with natural user-facing terms. It is distinguishable from other frontend skills.

DimensionReasoningScore

Specificity

Lists multiple concrete actions: "Check for `position: fixed`, `position: absolute` with large z-index, backdrop overlays, and JavaScript that shows modals on page load" plus "Consider both SEO impact (Google) and accessibility (WCAG focus management)."

3 / 3

Completeness

Explicitly answers both: what ("Check for...", "Consider both SEO impact... and accessibility") and when via the leading "Use when applies to CSS and JavaScript implementations of modals..." trigger.

3 / 3

Trigger Term Quality

Covers natural terms users would say — "modals, overlays, pop-ups, cookie banners, newsletter sign-up dialogs, and promotional overlays" — giving good breadth of likely trigger phrases.

3 / 3

Distinctiveness Conflict Risk

Clear niche (intrusive interstitials) with distinctive triggers — modals, cookie banners, position:fixed, large z-index — unlikely to fire for unrelated skills.

3 / 3

Total

12

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.