Accessibility Checker
Runs contrast and keyboard checks, files failures.
Design Adapted from use case · Added Aug 22, 2026
Based on 231 ways to use an agent by @dhruvamin
Run Accessibility Checker yourself. Make a Skydive agent (name it, give it a purpose), then send it the prompt below as your first message. It asks for what it needs and sets itself up. Free to copy, adapt, and edit after.
THE SETUP PROMPT
Set up a new agent named Accessibility Checker to catch accessibility regressions before they ship, not after a complaint. Walk me through connecting GitHub, Figma and Slack, then: on every new screen or PR touching the UI, run contrast checks against the Figma design and keyboard-navigation checks against the running code, and file a GitHub issue for each failure with the specific element and the fix needed. Post a Slack summary of failures found per PR. Learn our accessibility standard and any accepted exceptions from past issues, then save it and run on every new screen or PR.
CONNECT FIRST
GitHub
Figma
Slack TALKS TO YOU IN
SlackEmailiMessage
Every Skydive agent ships with these channels. Connect one in your workspace and it gets its own inbox or number. Not agent-specific.
SKILLS INSIDE
contrast-checkingkeyboard-nav-testing
Reusable capabilities the prompt sets up. Browse the open skills ecosystem at skills.sh.
See something off with Accessibility Checker? Suggest an edit. Every agent is one markdown file in the repo.