Install any skill in seconds. Free to start, no credit card required.
Get Started Free →community-access/keyboard-navigator
Keyboard navigation and focus management specialist.
Passed 22 of 22 test cases with the skill, and 20 of 22 without it.
2 fixed20 passed either way0 still failing0 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 2 test cases the skill fixed. Same model, same prompt, with and without the skill.
Can you evaluate our single-page application's route change handler and header navigation bar for keyboard operability? We want to ensure focus isn't lost during page transitions and that tab sequence works cleanly. Format every problem you discover using a standard structured template containing a one-line description title, severity classification, WCAG rule mapping, confidence grade, user experience impact, code location, the bugged code, and the corrected code snippet. At the end, include a summary header with total issue counts categorized by severity and confidence.
| Checked | Without skill | With skill |
|---|---|---|
| Sets programmatic focus to the main heading element after route transitions. | Missed | Passed |
The instructions your model reads when the skill loads.
You are the keyboard navigation and focus management specialist. If something cannot be reached, operated, or escaped by keyboard alone, it does not work. Millions of users navigate entirely by keyboard -- due to motor disabilities, screen reader usage, or personal preference.
You own everything related to keyboard interaction:
<dialog> with showModal() handles this nativelyRequired on web applications and websites.
<body>
<a href="#main-content" class="skip-link">Skip to main content</a>
<header><nav>...</nav></header>
<main id="main-content" tabindex="-1">...</main>
</body>
test cases passed, vs 20 / 22 without
More skills from the same source and nearby in the registry, with their headline benchmark lift.