CtrlK
BlogDocsLog inGet started
Tessl Logo
SkillPublic

focus-styles

Use when reviewing stylesheets, component styles, and responsive behavior related to Provide visible custom focus indicators. Check the rendered layout across breakpoints and interaction states before proposing a fix.

Quality

78%

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/focus-styles/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

78%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, right-sized body for a single CSS accessibility rule: concrete search patterns and values, a clear Check→Fix sequence with embedded verification checkpoints, and correct deferral of code examples to a single one-level-deep reference file. The only improvements are trimming the intro rationale paragraph (duplicated in the reference) and surfacing one inline fix snippet plus the post-fix verification step in the body itself.

Suggestions

Cut or compress the opening rationale paragraph — the same text appears in references/rule.md's 'Why It Matters', and Claude already knows why keyboard focus indicators matter.

Add one minimal inline fix snippet in the Fix section (e.g., the :focus-visible rule with outline: 2px solid and outline-offset) so the guidance is copy-paste ready without opening the reference.

Surface the post-fix verification step from references/rule.md's Verification section in the body's Fix or Code Review section to close the validation gap.

DimensionReasoningScore

Conciseness

The body is mostly lean — dense prescriptive bullets ('3:1 contrast ratio against adjacent colors (WCAG 2.2)', 'at least 2px solid outline with an offset') and short Check/Fix/Explain/Code Review sections — but the opening paragraph ('Users who navigate by keyboard... rely entirely on focus indicators to know where they are on the page') explains rationale Claude already knows and duplicates references/rule.md's 'Why It Matters' nearly verbatim. This is a minor instance of over-explanation that could be trimmed (anchor 4), not the broader padding of anchor 3, and not the fully lean anchor 5.

4 / 5

Actionability

Concrete executable guidance is present: exact search targets ('Find all instances of outline: none, outline: 0, or :focus { outline: none }'), specific values ('3:1 contrast ratio', 'at least 2px solid outline with an offset'), and a definite fix direction ('Replace outline: none on :focus with :focus-visible styles'). It falls short of anchor 5 because no copy-paste CSS snippet appears in the body — all code examples live in references/rule.md — and sits above anchor 3 because it names exact selectors, declarations, and values rather than pseudocode or vague hints.

4 / 5

Workflow Clarity

The Check → Fix → Explain → Code Review sections form an unambiguous sequence for this simple single-purpose rule, and the Check section embeds verification checkpoints ('Check if they provide an alternative visible focus indicator', 'verify the ring cannot be clipped or misplaced by overflow or missing positioning context'). It matches anchor 4 rather than 5 because a post-fix rendered-verification step exists only in references/rule.md's Verification section, not in the body; the destructive/batch cap does not apply since this is a review/propose skill.

4 / 5

Progressive Disclosure

The ~35-line body is a clear overview that defers 'full implementation details, code examples, and framework-specific guidance' to references/rule.md — a real file (verified present), one level deep, clearly signaled at the end. Code examples, skip-link patterns, the WCAG breakdown, and verification steps are appropriately split into the reference rather than inlined, matching the top anchor ('Clear overview with well-signaled one-level-deep references; content appropriately split; easy navigation').

5 / 5

Total

17

/

20

Passed

Description

70%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 'Use when...' trigger, good natural keyword coverage, and a clearly distinguishable accessibility niche. Its main weaknesses are the imperative instruction voice in the second sentence (penalized under specificity) and a 'what' that is implied through the when-clause rather than stated as a capability.

Suggestions

Rewrite the second sentence in third person as a capability statement (e.g., 'Reviews focus indicator styles across breakpoints and interaction states and proposes concrete fixes') to avoid the imperative-instruction voice penalty.

Add natural trigger synonyms such as 'outline: none', 'focus ring', 'keyboard navigation', or ':focus-visible' to strengthen trigger term coverage and distinctiveness.

State the 'what' as an explicit capability clause before the 'Use when...' trigger (e.g., 'Flags and fixes invisible or missing keyboard focus indicators in CSS') so completeness reaches the top anchor.

DimensionReasoningScore

Specificity

The description lists several concrete actions — 'reviewing stylesheets, component styles, and responsive behavior', 'Check the rendered layout across breakpoints and interaction states', 'proposing a fix' — which on content alone anchors at 4 ('Lists several specific actions; minor gaps in coverage'). However, the second sentence is a second-person imperative instruction ('Check the rendered layout across breakpoints and interaction states before proposing a fix') rather than a third-person capability statement, and the rubric's voice guideline reduces the specificity score by 1, landing at 3. It stays above anchor 2 because the domain and multiple actions are named concretely, not minimally or generically.

3 / 5

Completeness

Both parts are answered: the explicit trigger 'Use when reviewing stylesheets, component styles, and responsive behavior related to Provide visible custom focus indicators' plus the actions in 'Check the rendered layout across breakpoints and interaction states before proposing a fix'. It matches anchor 4 rather than 5 because the 'what' is embedded inside the when-clause and an instruction rather than stated as a clean, explicit capability; it is above anchor 3 because the 'when' is explicit and specific, not missing or weakly implied.

4 / 5

Trigger Term Quality

Natural terms users would say are present — 'stylesheets', 'component styles', 'responsive behavior', 'breakpoints', 'interaction states', 'focus indicators' — matching anchor 4 ('Good keyword coverage; a few natural terms missing'). It falls short of anchor 5 because common synonyms and variations are absent ('outline', 'focus ring', 'keyboard navigation', ':focus-visible', 'accessibility/a11y', '.css'), and it exceeds anchor 3 because coverage goes well beyond one or two generic keywords.

4 / 5

Distinctiveness Conflict Risk

'Provide visible custom focus indicators' carves a clear niche with distinct triggers like 'focus indicators', matching anchor 4 ('Mostly distinct; minor overlap risk with closely related skills'). The generic lead 'reviewing stylesheets, component styles, and responsive behavior' would overlap with sibling CSS-review skills sharing the same template, and missing distinguishing terms like 'outline' or ':focus-visible' keep it below anchor 5's 'clear niche with distinct triggers; minimal conflict risk'.

4 / 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/focus-styles/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.