CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

horizontal-scroll

Use when applies to all CSS layout rules. Check `width`, `min-width`, fixed pixel values on containers, `overflow`, `white-space`, and `word-break` properties. Use when auditing responsive design or WCAG 2.1 Level AA compliance. Test at 320px viewport width and at 400% browser zoom.

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/horizontal-scroll/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 overview with highly actionable Check/Fix guidance and excellent progressive disclosure into a genuine one-level reference. Its main weakness is redundancy — the WCAG 1.4.10 reflow requirement is restated four times — plus a missing post-fix verification step.

Suggestions

State the 320px / 400% zoom / SC 1.4.10 reflow requirement once (e.g., in Quick Reference) and remove its restatements in the intro and Explain sections — Quick Reference bullets 1 and 2 are near-duplicates.

Add a post-fix re-verification step (re-test at 320px and confirm no horizontal scrollbar) to close the workflow feedback loop, or point to the Verification section in references/rule.md.

Include one minimal inline code example (e.g., the `max-width` + `width: 100%` pattern) so the most common fix is copy-paste ready without opening the reference.

DimensionReasoningScore

Conciseness

The 320px / 400% zoom / SC 1.4.10 reflow fact is stated four times: in the intro ("WCAG 2.1 SC 1.4.10 (Reflow) specifically addresses this..."), in both Quick Reference bullets (which are near-duplicates of each other), and again in full in the Explain section. This fits "mostly efficient but could be tightened"; not 4 because the repetition exceeds minor trimming, not 2 since the Check and Fix sections are lean.

3 / 5

Actionability

Concrete, specific guidance throughout: "Replace fixed `width: Npx` on layout containers with `max-width: Npx` plus `width: 100%`", "Apply `overflow-wrap: break-word` (with fallback `word-wrap: break-word`)", "`overflow-x: auto` on the table wrapper, not the page body". Not 5 because the body has no copy-paste code (it lives in references/rule.md) and never says how to test at 320px; not 3 since the guidance is specific and complete for the common cases, not pseudocode.

4 / 5

Workflow Clarity

A clear Check → Fix sequence with the 320px test as an explicit inspection checkpoint ("Test the page at a 320px CSS viewport width... Look for horizontal scrollbars"). Not 5 because there is no post-fix re-verification step in the body — the Verification procedure exists only in references/rule.md and is not pointed to; not 3 since the sequence and checkpoints are explicit.

4 / 5

Progressive Disclosure

A ~45-line overview with well-organized sections (Quick Reference, Check, Fix, Explain, Code Review) and bulk code examples correctly split into a real, one-level-deep, clearly signaled reference: "For full implementation details, code examples, and framework-specific guidance, see `references/rule.md`" — the file exists and matches. Matches the clear-overview anchor; the only quibble ("framework-specific guidance" slightly over-describes the reference's contents) does not fit the anchor-4 organization gaps.

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 lists concrete, specific capabilities and has an explicit "Use when" trigger, but never names the skill's core subject — horizontal scrolling — and opens with a garbled, over-broad clause. Keyword coverage is good for the auditing context yet misses the most natural defect terms a user would say.

Suggestions

State the skill's purpose explicitly (e.g., "Prevent horizontal scrolling / horizontal overflow at small viewport widths") so the what is complete and the core trigger term appears.

Fix or remove the garbled clause "Use when applies to all CSS layout rules" — the all-CSS claim widens conflict with every other CSS skill.

Add natural trigger terms users would actually say: "horizontal scroll", "horizontal overflow", "reflow", "sideways scrolling".

DimensionReasoningScore

Specificity

Lists several concrete actions — "Check `width`, `min-width`, fixed pixel values on containers, `overflow`, `white-space`, and `word-break` properties" and "Test at 320px viewport width and at 400% browser zoom" — matching the anchor for several specific actions with minor gaps. Not 5 because it never states the skill's actual outcome (preventing horizontal scrolling); not 3 because coverage well exceeds 1-2 actions.

4 / 5

Completeness

Both what ("Check ... properties", "Test at 320px viewport width and at 400% browser zoom") and an explicit when ("Use when auditing responsive design or WCAG 2.1 Level AA compliance") are present. Not 5 because the opening clause "Use when applies to all CSS layout rules" is garbled and the what omits the skill's purpose (preventing horizontal overflow); not 3 since the when is explicit rather than merely implied.

4 / 5

Trigger Term Quality

Good natural keyword coverage: "auditing responsive design", "WCAG 2.1 Level AA compliance", "browser zoom", "320px viewport width". Not 5 because the most natural user phrasings for this skill — "horizontal scroll", "horizontal overflow", "reflow", "sideways scrolling" — are entirely absent; not 3 because coverage is far richer than the anchor-3 example.

4 / 5

Distinctiveness Conflict Risk

"applies to all CSS layout rules" is maximally broad, and "auditing responsive design or WCAG 2.1 Level AA compliance" overlaps other responsive/WCAG audit skills — fitting the "somewhat specific but could still overlap" anchor. Not 4 because the all-CSS claim plus the garbled opening clause raise overlap beyond minor; not 2 since the specific properties and 320px/400% zoom details anchor it to 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/horizontal-scroll/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.