CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

touch-targets

Use when applies to all interactive elements on touchscreen interfaces: buttons, links, checkboxes, radio buttons, form inputs, icon buttons, and menu items. Check CSS for min-width, min-height, width, height, and padding on interactive elements. Particularly important for icon-only buttons (close, delete, share) which are often made too small.

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/touch-targets/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

67%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 audit skill: precise check criteria, copy-paste CSS fixes, and a clean one-level reference split. The main weaknesses are redundancy — the Explain section repeats Quick Reference thresholds, and the Code Review section is boilerplate — and verification guidance that stays generic in the body.

Suggestions

Cut the "Explain" section or reduce it to one line of fingertip-size rationale; the WCAG SC numbers and 24/44px thresholds are already in Quick Reference and in references/rule.md, so repeating them triples the same facts.

Replace the generic "Code Review" boilerplate with a concrete verification step, e.g. "Verify: re-measure the rendered bounding box in DevTools (or run axe's target-size rule) and confirm every target is ≥24×24px or has 24px spacing".

Make the reference pointer accurate to rule.md's contents (code examples, size table, exceptions, verification) rather than promising "framework-specific guidance" that the file does not contain.

DimensionReasoningScore

Conciseness

The Check and Fix sections are tight, but there is real redundancy: the "Explain" section restates the WCAG SC numbers and 24/44px thresholds already given in "Quick Reference", and the "Code Review" section is generic boilerplate ("Flag exact elements, roles, labels, focus behavior, or keyboard interactions") that adds little beyond what any audit skill would say. Not 2 because the core instructional sections are efficient; not 4 because the duplicated thresholds and filler section are noticeable padding.

3 / 5

Actionability

"Check" specifies exact element selectors, the measurement to take (rendered bounding box including padding), and concrete thresholds (24px AA, 44px AAA, 24px spacing rule); "Fix" provides copy-paste CSS including `min-width: 44px; min-height: 44px` and the `::before { inset: -12px }` hit-area pattern. It falls short of 5 because the body contains no complete executable example (those live in the reference) and verification guidance ("browser accessibility tooling") stays generic.

4 / 5

Workflow Clarity

A clear Check-then-Fix sequence with explicit flagging criteria and four enumerated remediation techniques in priority order. The verify-the-fix step exists ("Code Review" section, plus a Verification section in the reference) but is vague in the body, which is the minor checkpoint gap that keeps it at 4 rather than 5.

4 / 5

Progressive Disclosure

The ~47-line body is a well-organized overview (Quick Reference, Check, Fix, Explain) that points to a real, one-level-deep `references/rule.md` for code examples and detail — verified the file exists. It falls short of 5 because the pointer slightly overstates the reference ("framework-specific guidance" is not actually in rule.md) and the Explain section duplicates reference material (the size-requirements table and rationale), a minor organization gap.

4 / 5

Total

15

/

20

Passed

Description

75%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 specific, well-scoped description with good trigger vocabulary and explicit what/when structure, held back by a malformed opening clause ("Use when applies to") and the absence of the field's canonical terms (touch targets, tap targets, WCAG). Solid but with clear room for polish.

Suggestions

Fix the garbled trigger clause: replace "Use when applies to all interactive elements on touchscreen interfaces" with a grammatical, situation-specific trigger such as "Use when reviewing or auditing UI for touch target size, mobile accessibility, or when interactive elements (buttons, links, form controls) appear too small to tap".

Add the canonical trigger terms users naturally say — "touch targets", "tap targets", "hit area", and "WCAG 2.2 target size" — so the skill matches how the requirement is actually named.

State the outcome as a concrete action, e.g. "Flags interactive elements smaller than 24×24px (AA) or 44×44px (AAA) and prescribes CSS fixes", to strengthen the 'what' beyond a single 'Check' verb.

DimensionReasoningScore

Specificity

The description enumerates concrete element types ("buttons, links, checkboxes, radio buttons, form inputs, icon buttons, and menu items") and the exact CSS properties to check ("min-width, min-height, width, height, and padding"), giving several specifics with only minor gaps. It falls short of 5 because it has effectively one action verb ("Check") rather than multiple distinct concrete actions.

4 / 5

Completeness

Both parts are present: what ("Check CSS for min-width, min-height, width, height, and padding on interactive elements") and when ("Use when applies to all interactive elements on touchscreen interfaces"). The when-clause is grammatically garbled ("Use when applies to") and not situation-specific, so it does not clearly match the 5 anchor's explicit concrete trigger phrases, but an explicit trigger clause does exist, keeping it above 3.

4 / 5

Trigger Term Quality

Good natural keyword coverage including "icon-only buttons (close, delete, share)", "padding", "min-width", and touchscreen UI vocabulary. It misses the canonical synonyms users actually say — "touch targets" / "tap targets" / "hit area" — and "WCAG", so it does not reach 5.

4 / 5

Distinctiveness Conflict Risk

It carves out a clear niche (touch-target sizing on interactive elements for touchscreens) with specific triggers. Minor overlap risk remains with general responsive-layout or other accessibility skills since "Check CSS for min-width, min-height, width, height, and padding" could broadly match layout work.

4 / 5

Total

16

/

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/touch-targets/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.