CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

autofocus-avoidance

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Avoid autofocus on form fields. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

77%

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/autofocus-avoidance/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.

A well-organized, appropriately-sized body with excellent progressive disclosure and a clear check-fix-review flow. The main weaknesses are redundancy across the Quick Reference, opening line, Explain, and Code Review sections, and verification guidance that names 'browser accessibility tooling' without any concrete tool or procedure.

Suggestions

Remove the duplication between the opening sentence and the Explain section, and trim the Quick Reference bullets that restate the Check and Fix sections verbatim — one authoritative statement of each point is enough.

Make the verification step concrete: name a specific check such as a keyboard-only Tab test on page load, or a specific tool (e.g. axe DevTools, VoiceOver/NVDA) instead of the generic 'browser accessibility tooling or assistive tech'.

Either include a minimal inline example of the recommended JavaScript focus pattern (e.g. focus set in a click handler) or explicitly note that the code example for it is in references/rule.md.

DimensionReasoningScore

Conciseness

The body is compact overall but contains real redundancy: the opening line ('Autofocus teleports screen reader users to mid-page without context...') is nearly duplicated by the Explain section ('Explain how autofocus moves screen reader users to mid-page without context...'), the Quick Reference bullets restate the Check/Fix content, and the Code Review paragraph restates the frontmatter description. This fits 'mostly efficient but includes some unnecessary explanation or could be tightened' rather than 4, where over-explanation would be only minor.

3 / 5

Actionability

As an instruction-only skill the guidance is concrete and specific: 'Search for autofocus attributes on form elements', 'Remove autofocus attributes from form elements. If focus management is needed, use JavaScript to set focus after user interaction rather than automatically on page load.' It stops short of 5 because the JavaScript focus alternative is named but never shown or pointed to inline (the code example lives only in references/rule.md).

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form a coherent review workflow with a named verification checkpoint ('note how to verify the fix with browser accessibility tooling or assistive tech'), matching 'clear sequence with most checkpoints present; minor validation gaps'. Not 5 because the verification step names no concrete tool or procedure (e.g. keyboard-only tab test, a specific screen reader, or axe DevTools).

4 / 5

Progressive Disclosure

The body is under 50 lines, cleanly sectioned (Quick Reference, Check, Fix, Explain, Code Review), and points to a single one-level-deep reference that exists (references/rule.md) with its contents clearly labeled ('For full implementation details, code examples, and framework-specific guidance'). This matches 'clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation'.

5 / 5

Total

16

/

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 solid description with an explicit trigger clause and several concrete inspection actions. Its main weaknesses are the awkwardly injected rule-name phrase ('related to Avoid autofocus on form fields'), the missing mention of the fix/explain capabilities, and the absence of common accessibility vocabulary like 'accessibility' or 'a11y'.

Suggestions

State the full capability set in the what-portion, e.g. 'Flag autofocus violations on form fields, remove them, and explain the impact' so the description covers check, fix, and explain rather than only inspection.

Smooth the boilerplate phrase 'related to Avoid autofocus on form fields' into natural language (e.g. 'Use when reviewing HTML or interactive components for autofocus on form fields') so it reads as a capability statement rather than an injected rule name.

Add natural accessibility vocabulary users would actually say — 'accessibility', 'a11y', 'focus management', or 'WCAG' — to improve trigger term coverage.

DimensionReasoningScore

Specificity

The description lists several concrete actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"), matching the 'several specific actions; minor gaps' anchor. It falls short of 5 because the skill's fix and explain capabilities are not mentioned, and above 3 because it goes beyond 1-2 generic actions.

4 / 5

Completeness

Both parts are present: an explicit "Use when reviewing rendered HTML, interactive components, or design-system patterns..." trigger clause plus concrete what-actions ("Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output"). It is not 5 because the when-clause is broad and the awkward 'related to Avoid autofocus on form fields' phrasing blurs what the skill actually does (flag and fix autofocus violations).

4 / 5

Trigger Term Quality

It includes good natural keywords users would say — "autofocus", "form fields", "keyboard", "focus", "screen-reader", "rendered HTML" — matching the 'good keyword coverage; a few natural terms missing' anchor. Not 5 because common variations like "accessibility", "a11y", "focus management", or "WCAG" are absent.

4 / 5

Distinctiveness Conflict Risk

"autofocus" and "form fields" are distinct niche triggers with minimal conflict risk, fitting the 'mostly distinct; minor overlap risk' anchor. The broad opening 'reviewing rendered HTML, interactive components, or design-system patterns' could overlap with generic frontend or design-system review skills, keeping it below 5.

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/autofocus-avoidance/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.