keyboard-navigation-tester
Keyboard Navigation Tester - Auto-activating skill for Frontend Development. Triggers on: keyboard navigation tester, keyboard navigation tester Part of the Frontend Development skill category.
34
3%
Does it follow best practices?
Impact
87%
1.00xAverage score across 3 eval scenarios
Passed
No known issues
Optimize this skill with Tessl
npx tessl skill review --optimize ./planned-skills/generated/05-frontend-dev/keyboard-navigation-tester/SKILL.mdQuality
Discovery
7%Based on the skill's description, can an agent find and select it at the right time? Clear, specific descriptions lead to better discovery.
This description is essentially a title repeated as a trigger term with no substantive content. It fails to describe any concrete actions the skill performs, provides no meaningful trigger terms beyond its own name, and lacks any 'Use when...' guidance. It reads as auto-generated boilerplate rather than a useful skill description.
Suggestions
Add concrete actions describing what the skill does, e.g., 'Tests keyboard navigation flows, validates tab order, checks focus management, and identifies focus traps in web interfaces.'
Add a 'Use when...' clause with natural trigger terms like 'Use when the user asks about tab order, keyboard accessibility, focus management, a11y keyboard testing, or navigating UI with keyboard only.'
Expand trigger terms to include common variations users would naturally say: 'tab navigation', 'focus order', 'keyboard accessibility', 'a11y', 'focus trap', 'skip links'.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description names the domain ('Frontend Development') but describes no concrete actions. 'Keyboard Navigation Tester' is a label, not a description of what it does—there are no verbs like 'tests', 'validates', 'checks tab order', etc. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name itself, and the 'when' clause is just a redundant repetition of the skill name rather than meaningful trigger guidance. | 1 / 3 |
Trigger Term Quality | The only trigger terms listed are 'keyboard navigation tester' repeated twice. It misses natural user phrases like 'tab order', 'focus management', 'accessibility', 'keyboard accessibility', 'focus trap', 'a11y', or 'screen reader navigation'. | 1 / 3 |
Distinctiveness Conflict Risk | The phrase 'keyboard navigation' is fairly niche and unlikely to conflict with most other skills, but the lack of specificity about what it actually tests or validates means it could overlap with broader accessibility or frontend testing skills. | 2 / 3 |
Total | 5 / 12 Passed |
Implementation
0%Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
This skill is an empty shell with no actual content. It consists entirely of auto-generated boilerplate that describes what a skill would do without providing any real instructions, code, examples, or techniques for keyboard navigation testing. It adds no value beyond what Claude already knows and wastes tokens on meta-descriptions.
Suggestions
Add concrete, executable code examples for keyboard navigation testing (e.g., using Testing Library's userEvent.tab(), Cypress keyboard commands, or Playwright keyboard interaction APIs)
Include a specific workflow for auditing keyboard navigation: identify focusable elements, test tab order, verify focus indicators, check keyboard traps, validate ARIA roles
Provide a checklist of common keyboard navigation issues to test for (focus traps, missing skip links, non-focusable interactive elements, incorrect tab order) with code snippets showing how to detect each
Remove all boilerplate meta-sections ('When to Use', 'Example Triggers', 'Capabilities') and replace with actionable technical content
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is entirely filler and meta-description. It explains what the skill does in abstract terms without providing any actual knowledge or instructions. Every section restates the same vague concept without adding value. | 1 / 3 |
Actionability | There is zero concrete guidance—no code, no commands, no specific techniques for testing keyboard navigation. The content describes rather than instructs, offering no executable or actionable information whatsoever. | 1 / 3 |
Workflow Clarity | No workflow, steps, or process is defined. The skill claims to provide 'step-by-step guidance' but contains none. There are no validation checkpoints or sequences of any kind. | 1 / 3 |
Progressive Disclosure | There is no meaningful content to organize, no references to external files, and no structured navigation. The sections are purely boilerplate headers with no substantive content beneath them. | 1 / 3 |
Total | 4 / 12 Passed |
Validation
81%Checks the skill against the spec for correct structure and formatting. All validation checks must pass before discovery and implementation can be scored.
Validation — 9 / 11 Passed
Validation for skill structure
| Criteria | Description | Result |
|---|---|---|
allowed_tools_field | 'allowed-tools' contains unusual tool name(s) | Warning |
frontmatter_unknown_keys | Unknown frontmatter key(s) found; consider removing or moving to metadata | Warning |
Total | 9 / 11 Passed | |
- Commit
3076d78
- 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.