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
Quality
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 placeholder that provides almost no useful information for skill selection. It only states the skill name and category without explaining what the skill does, what actions it performs, or when it should be triggered. The redundant trigger terms and lack of natural user language make it nearly impossible for Claude to appropriately select this skill.
Suggestions
Add specific actions the skill performs, e.g., 'Tests keyboard accessibility by validating tab order, focus indicators, and keyboard-only navigation paths in web interfaces.'
Include a 'Use when...' clause with natural trigger terms like 'tab order', 'focus states', 'keyboard accessibility', 'a11y testing', 'skip links', or 'focus trap'.
Remove the duplicate trigger term and expand to include variations users would naturally say when needing keyboard navigation testing.
| Dimension | Reasoning | Score |
|---|---|---|
Specificity | The description only names the skill ('Keyboard Navigation Tester') without describing any concrete actions. There are no verbs indicating what the skill actually does - no mention of testing, validating, checking focus states, or any specific capabilities. | 1 / 3 |
Completeness | The description fails to answer 'what does this do' beyond the name, and provides no 'when should Claude use it' guidance. The 'Triggers on' field just repeats the skill name rather than providing meaningful trigger scenarios. | 1 / 3 |
Trigger Term Quality | The trigger terms are redundant ('keyboard navigation tester' listed twice) and overly specific. Missing natural variations users would say like 'tab order', 'focus', 'a11y', 'accessibility testing', 'keyboard shortcuts', or 'focus management'. | 1 / 3 |
Distinctiveness Conflict Risk | The term 'keyboard navigation' is somewhat specific to accessibility/frontend testing, which provides some distinctiveness. However, without concrete actions described, it could overlap with general accessibility skills 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 entirely meta-content describing what it claims to do rather than providing any actual guidance on keyboard navigation testing. It contains no executable code, no testing procedures, no accessibility standards (WCAG), no keyboard interaction patterns, and no concrete examples. The content is essentially a placeholder template with no substantive value.
Suggestions
Add concrete keyboard navigation testing steps: Tab order verification, focus indicator visibility, Enter/Space activation, Escape key handling, arrow key navigation patterns
Include executable code examples for testing keyboard accessibility, such as JavaScript snippets for focus trapping, skip links, or automated testing with tools like axe-core
Reference specific WCAG success criteria (2.1.1 Keyboard, 2.4.7 Focus Visible) and provide checklists for common UI components (modals, dropdowns, menus)
Add validation workflow: manual testing steps, automated testing commands, and common failure patterns with fixes
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The content is padded with generic boilerplate that provides no actual value. Phrases like 'provides automated assistance' and 'follows industry best practices' are vague filler that Claude doesn't need. | 1 / 3 |
Actionability | There is zero concrete guidance on how to actually test keyboard navigation. No code examples, no specific testing steps, no commands, no accessibility standards referenced - just abstract descriptions of what the skill supposedly does. | 1 / 3 |
Workflow Clarity | No workflow is provided whatsoever. The skill claims to provide 'step-by-step guidance' but contains no actual steps for testing keyboard navigation, no validation checkpoints, and no process to follow. | 1 / 3 |
Progressive Disclosure | The content is a monolithic block of meta-description with no useful structure. There are no references to detailed materials, no examples section, and no actual content to organize - just self-referential trigger descriptions. | 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
994edc4
- 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.