GitHub workflow accessibility router for PR review, issues, Actions, releases, projects, security alerts, notifications, repository management, and accessible contributor workflows.
SkillScore56Maintained
Automatic
◆DevOps & SRE pack
Last verified 8/22/2026
What it changes
Passed 14 of 25 test cases with the skill, and 4 of 25 without it.
Without skill16%
With skill56%
Checks it passed that the model alone missed
Orders regression findings by risk level.
Orders notification findings by risk level.
Orders documentation findings by risk level.
and 11 more in the full report
10 fixed4 passed either way11 still failing0 broke
Pass-rate lift
+40 pp
Tokens
-22%
Agent turns
0%
Response time
-29%
Model gemini-3.6-flashMeasured 8/22/2026v114 of 25 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 10 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 10
Prompt
We are configuring automated release pipelines and issue management for our organization's repository. Can you assess our repository setup workflow and give me a clear report detailing any potential compliance gaps, recommended automated checks, and suggested next steps tied to our repository configuration?
What was checked, without and with the skill
Checked
Without skill
With skill
Checks installed Accessibility Agents extensions for release standards or compliance reporting.
Missed
Passed
Ties recommendations directly to specific repository configuration objects.
Missed
Passed
case-02 · 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
GitHub Workflows Router
Use this skill for GitHub workflow tasks that should preserve accessible repository operations.
Workflow
Identify the GitHub workflow: PR review, issue triage, Actions, releases, projects, wiki, security alerts, notifications, or repository setup.
Check installed Accessibility Agents extensions for organization-specific labels, required checks, release standards, or compliance reporting.
Use pr-review for code review and add domain specialists when the diff touches accessibility-sensitive surfaces.
Keep findings concrete, ordered by risk, and tied to files, checks, or GitHub objects.
Do not replace GitHub product policy or repository ownership decisions. Surface risks and suggested actions.