Developer tools accessibility router for Python, wxPython, desktop accessibility APIs, NVDA add-ons, scanner tooling, CI tooling, and accessibility developer experience.
NewMaintained
Automatic
◆Coding pack
Last verified 8/22/2026
What it changes
Passed 7 of 22 test cases with the skill, and 15 of 22 without it.
Without skill67%
With skill33%
Checks it passed that the model alone missed
The response recommends specifying explicit keyboard interaction models for exposed tools.
1 fixed18 passed either way1 still failing2 broke
Pass-rate lift
-33 pp
Tokens
-6%
Agent turns
0%
Response time
-9%
Model gemini-3.6-flashMeasured 8/22/2026v119 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
A test case the skill fixed. Same model, same prompt, with and without the skill.
Prompt
Our team is designing a Model Context Protocol (MCP) server that exposes desktop accessibility inspection tools to local agents. We plan to emit unstructured text logs without keyboard shortcut annotations or structured node naming. Review our MCP tool response design.
What was checked, without and with the skill
Checked
Without skill
With skill
The response recommends returning structured screen reader naming attributes in the tool payloads.
Passed
Passed
The response recommends specifying explicit keyboard interaction models for exposed tools.
Missed
Passed
case-04 · gemini-3.6-flash · 8/22/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md12 linessingle file
Developer Tools Router
Use this skill for desktop, Python, scanner, and developer-tool accessibility work.
Workflow
Identify the platform: Python CLI, wxPython, desktop GUI, NVDA add-on, scanner tooling, CI integration, or MCP/server tooling.
Check installed Accessibility Agents extensions for company tooling standards, internal scanner rules, or platform-specific requirements.
Use the matching Codex subagent for focused review when subagents are requested.
Keep recommendations practical: APIs, keyboard behavior, screen reader naming, focus handling, test coverage, and packaging impact.
Extension rules should supplement core accessibility standards, not hide them.