focus-management

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Manage focus during dynamic interactions. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output where relevant.

Quality

76%

Does it follow best practices?

Run evals on this skill

Adds up to 20 points to the overall score

View guide

Securityby

Passed

No findings from the security scan

Fix and improve this skill with Tessl

tessl review fix ./skills/focus-management/SKILL.md

Quality

Content

70%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 concise and well-structured with a clean pointer to a single one-level-deep reference that genuinely exists. It is held back by lacking inline executable examples and explicit verification checkpoints in the SKILL.md itself, relying on the reference for both.

Suggestions

Add one short inline code snippet (e.g. a focus-trap or focus-restore pattern) so the body is actionable without opening the reference.

Surface an explicit validation step in the body — e.g. 'After fixing, verify with axe/Lighthouse and a keyboard pass' — to lift workflow_clarity above the verification cap.

Briefly list what references/rule.md contains (key-principles table, scenario examples, verification checks) so readers can decide when to open it.

Dimension	Reasoning	Score
Conciseness	The body is lean (~30 lines), avoids re-explaining what focus management is beyond one orienting sentence, and delegates detail to references/rule.md; every line earns its place.	5 / 5
Actionability	Guidance is actionable at the directive level ('Move focus to modal when opened', "Use tabindex='-1'", 'focus(), and focus trapping') but the body itself contains no executable code or copy-paste commands — those live in the reference file, leaving minor gaps inline.	3 / 5
Workflow Clarity	The Check/Fix/Explain/Code Review sections give a rough review sequence, but there are no explicit validation checkpoints or feedback loops in the body (the verification steps live only in the reference), so the cap for a verification-gated review workflow applies.	3 / 5
Progressive Disclosure	A clear overview body with a well-signaled one-level-deep reference ('see references/rule.md'), and rule.md is a real file with the expected deeper detail; minor gap is the body does not enumerate the reference's sub-topics to aid discovery.	4 / 5
	Total	15 / 20 Passed

Description

83%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 is well-formed: third person, explicit 'Use when' trigger, and a concrete checklist of review actions. It is slightly generic across the broader accessibility-review niche, which keeps it just short of maximal distinctiveness.

Dimension	Reasoning	Score
Specificity	Lists several concrete review actions ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output'), giving minor gaps in coverage rather than a comprehensive enumeration.	4 / 5
Completeness	Explicitly answers 'when' ('Use when reviewing rendered HTML, interactive components, or design-system patterns related to Manage focus during dynamic interactions') and 'what' ('Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output') with concrete trigger phrases.	5 / 5
Trigger Term Quality	Good natural coverage ('rendered HTML, interactive components, design-system patterns', 'keyboard behavior'), with only a few common phrasings a user might say (e.g. 'a11y', 'accessibility audit') absent.	4 / 5
Distinctiveness Conflict Risk	Scoped to focus management within accessibility reviewing — mostly distinct from sibling a11y skills, with only minor overlap risk on adjacent review skills covering semantics or screen-reader output.	4 / 5
	Total	17 / 20 Passed

Validation

93%

Warnings & errors only

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

Criteria	Description	Result
metadata_version	'metadata.version' is missing	Warning

	Total	15 / 16 Passed

Repository: thedaviddias/Front-End-Checklist
Path: skills/focus-management/SKILL.md
Commit: 30756a7

Reviewed: 20 days ago

Table of Contents

Discovery Implementation Validation

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.