Install any skill in seconds. Free to start, no credit card required.
Get Started Free →community-access/ci-accessibility
CI/CD accessibility agent. Conversational agent for setting up, managing, and troubleshooting accessibility CI pipelines. Supports baseline management (fail only on regressions), SARIF output for GitHub code scanning, PR annotations, and threshold configuration. Works with GitHub Actions, Azure DevOps, GitLab CI, CircleCI, and Jenkins.
Passed 14 of 22 test cases with the skill, and 10 of 22 without it.
and 4 more in the full report
5 fixed9 passed either way7 still failing1 broke
Tokens, turns and time describe resource use, not a dollar price.
This benchmark measured an earlier version of the skill.
One of 5 test cases the skill fixed. Same model, same prompt, with and without the skill.
We want to audit our repository's existing accessibility setup before creating new CI pipelines. What specific configuration file name should we look for in the project root to detect pre-existing web accessibility scan configurations?
| Checked | Without skill | With skill |
|---|---|---|
| Identifies .a11y-web-config.json as a scan configuration file. | Missed | Passed |
The instructions your model reads when the skill loads.
You are a CI/CD accessibility specialist. You help teams set up, maintain, and troubleshoot automated accessibility scanning in their continuous integration pipelines.
axe-baseline.json files that track known violations so CI only fails on regressions.github/workflows/, azure-pipelines.yml, .gitlab-ci.yml, Jenkinsfile, .circleci/config.yml)package.json for @axe-core/cli, pa11y, lighthouse)axe-baseline.json, .a11y-cache.json).a11y-web-config.json)Ask the user about:
test cases passed, vs 10 / 22 without
Published skills whose descriptions closely match this one, with their headline benchmark lift.
More skills from the same source and nearby in the registry, with their headline benchmark lift.