CtrlK
BlogDocsLog inGet started
Tessl Logo

accordion-accessibility

Use when reviewing templates, rendered HTML, or shared components related to Make accordions keyboard navigable. Validate the final browser-facing markup, not just the source framework abstraction.

61

Quality

72%

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/accordion-accessibility/SKILL.md
SKILL.md
Quality
Evals
Security

Quality

Content

70%

Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.

The content is a clean, well-organized overview that appropriately offloads detail to a real one-level reference. Its weaknesses are redundancy across the Quick Reference/Check/Fix sections and the lack of an in-body executable example, leaving Fix somewhat generic.

Suggestions

Collapse the overlapping Quick Reference, Check, and Fix sections into a single checklist to remove the repeated aria-expanded/aria-controls/keyboard statements.

Include a minimal in-body HTML snippet showing the correct button+aria-expanded+aria-controls pattern so the guidance is copy-paste ready before reaching the reference.

Make the Fix step concrete by naming the exact keyboard handlers (Enter, Space, Arrow Up/Down) instead of the generic 'and keyboard support'.

DimensionReasoningScore

Conciseness

The body is lean and well-sectioned, but Quick Reference, Check, and Fix all restate the same aria-expanded/aria-controls/keyboard points, so it could be tightened by consolidating the redundant sections.

2 / 3

Actionability

Concrete attributes are named (aria-expanded, aria-controls, Arrow/Enter/Space keys), but there is no in-body executable example (deferred to the reference) and the Fix step stays generic with 'and keyboard support'.

2 / 3

Workflow Clarity

This is a simple single-purpose skill under 50 lines with clear Check/Fix/Explain/Code Review sections; per the simple-skills note, clear organization lets workflow clarity reach 3 even without an explicit multi-step process.

3 / 3

Progressive Disclosure

The body is a concise overview that clearly signals a single one-level-deep reference ('see references/rule.md'), and that file exists with code examples, ARIA patterns, and verification guidance, matching the score-3 anchor.

3 / 3

Total

10

/

12

Passed

Description

75%

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 clearly answers both what it does and when to use it, with a distinct accessibility niche. It is held back from a top score by action verbs that are variations on review/validate and by missing common accessibility trigger terms like 'a11y' or 'screen reader'.

Suggestions

Lead with a third-person action statement (e.g., 'Reviews and validates...') before the 'Use when' clause to broaden the action vocabulary beyond review/validate.

Add common accessibility trigger terms ('accessibility', 'a11y', 'screen reader', 'ARIA') so users searching those words match this skill.

DimensionReasoningScore

Specificity

It names the domain and concrete targets ('reviewing templates, rendered HTML, or shared components', 'Validate the final browser-facing markup'), but the actions are variations on review/validate rather than the multiple distinct actions of the score-3 anchor.

2 / 3

Completeness

An explicit 'Use when reviewing templates, rendered HTML, or shared components...' clause gives the trigger, and 'Validate the final browser-facing markup...' states what it does, satisfying both what and when.

3 / 3

Trigger Term Quality

Natural terms like 'accordion', 'keyboard', 'HTML', 'templates', and 'components' appear, but common accessibility variations a user would say ('accessibility', 'a11y', 'screen reader', 'ARIA') are missing.

2 / 3

Distinctiveness Conflict Risk

The niche is specific (accordion keyboard navigation, browser-facing markup vs source framework abstraction) with distinct triggers, making conflict with unrelated skills unlikely.

3 / 3

Total

10

/

12

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.

Validation15 / 16 Passed

Validation for skill structure

CriteriaDescriptionResult

metadata_version

'metadata.version' is missing

Warning

Total

15

/

16

Passed

Repository
thedaviddias/Front-End-Checklist
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.