testing-accessibility
Use when testing accessibility is required during quality work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
Profile →npx skills add casioreview20-glitch/forge-os --skill testing-accessibility --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Testing Accessibility ## Overview This skill owns one bounded responsibility: **testing accessibility**. Its focus is testing accessibility within quality lifecycle boundaries. It converts declared inputs into typed artifacts and reproducible evidence without silently changing product scope. ## Trigger Activate only when the project is in one of these stages: `verification`, all contract preconditions pass, and the router identifies a missing output this skill can produce. Do not activate merely because the skill name resembles the user request. ## Required Inputs - `test-plan` - `verified-build` - Optional: `domain-evidence` - Current gate result, open findings, artifact hashes, and invalidation state - Required tools: `test-runner` - Optional tools: none - Confirmed human decisions relevant to this scope ## Method-Specific Protocol 1. Define the exact decision, actors, objects, states, invariants, side effects, and non-goals owned by testing accessibility. 2. Build a decision table for normal, boundary, invalid, permission, failure, retry, recovery, concurrency, migration, and abuse conditions relevant to testing accessibility. 3. Apply testing accessibility only to direct inpu
- Overview
- Trigger
- Required Inputs
- Method-Specific Protocol
- Procedure
- Verification Questions
- Evidence Packet
- Output Contract
- Quality Gate
- Forbidden Shortcuts
- Failure Modes
- Escalation and Invalidation
- Handoff
- Token and Context Policy
What does the testing-accessibility skill do?
Use when testing accessibility is required during quality work, especially when the result must be traceable, independently reviewable, and safe to hand to another agent.
How do I install it?
Run `npx skills add casioreview20-glitch/forge-os --skill testing-accessibility --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From casioreview20-glitch/forge-os, a repository with 11 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.