New: 98,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Insiders A11y Tracker

by Community-Access in Community-Access/accessibility-agents

Track accessibility changes in VS Code and other repos you follow.

MITAuto-check passedFrontend & Design

Install Insiders A11y Tracker

skills CLI
$ npx skills add Community-Access/accessibility-agents --skill insiders-a11y-tracker -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install Community-Access/accessibility-agents insiders-a11y-tracker --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/insiders-a11y-tracker .claude/skills/insiders-a11y-tracker && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
insiders-a11y-tracker
GitHub stars
423
Token cost
~1.6k tokens
SKILL.md length
730 words
Files
5 (incl. references)
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Track accessibility changes in VS Code and other repos you follow.

  • Works in 4 steps: Add that repo to the session's tracked… → Search that repo using its own label… → Include results from all tracked repos… → …
  • Tasks that involve Accessibility
  • SKILL.md covers Configuration, Response Guidelines, Context Awareness and Multi-Repo Support, plus 6 more sections
  • Calls node

What it does

Insiders A11y Tracker is an agent skill from Community-Access/accessibility-agents. Track accessibility changes in VS Code and other repos you follow.

Its SKILL.md is about 1.6k tokens, which your agent loads only when the skill is triggered. The skill folder holds 6 other files, including reference files (for example `agents/openai.yaml`, `references/accessibility-tracker.md` and `references/tracked-repositories.md`).

It sits in Frontend & Design, covering Accessibility. It works with Visual Studio Code. The repository describes itself as: Accessibility review agents for Claude Code, GitHub Copilot, and Claude Desktop. Eleven specialists that enforce WCAG 2.2 AA compliance so AI coding tools stop generating… The licence is MIT.

When your agent uses it

  • Tasks that involve Accessibility

Example prompts

  • “/insiders-a11y-tracker”

Workflow steps

4 steps, taken from the first numbered list in SKILL.md.

  1. Add that repo to the session's tracked repos list.
  2. Search that repo using its own label conventions (discover labels by listing repo labels first if needed).
  3. Include results from all tracked repos in reports, clearly separated by repo.
  4. Suggest the user add the repo to preferences.md for persistent tracking.

What it can do on your machine

Read from SKILL.md and the folder at commit decf6ba. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • node

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Insiders A11y Tracker loads about 1.6k tokens when it runs, and up to ~4.6k if it reads all its reference files. Until then it costs about 22 tokens; SKILL.md has 730 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~22
When it runs · the whole SKILL.md, loaded when a task matches
~1.6k
With references · SKILL.md plus every file in references/, read only if the agent opens them
~4.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from Community-Access/accessibility-agents at commit decf6ba, republished under its MIT licence (© Community-Access). 730 words, ~1,562 tokens.

Download SKILL.mdSave it as .claude/skills/insiders-a11y-tracker/SKILL.md (or your agent's skills folder). This skill also uses 4 other files; get the full folder from GitHub.
name
insiders-a11y-tracker
description
Track accessibility changes in VS Code and other repos you follow.
license
MIT
disable-model-invocation
true
metadata.tier
specialist
metadata.domain
github
metadata.output
report
metadata.effort
medium
metadata.title
Insiders Accessibility Tracker

Configuration

Load accessibility tracking configuration from .github/agents/preferences.md under the accessibility_tracking section. If no configuration is found, use the defaults below.

Defaults
  • Primary tracked repo: microsoft/vscode
  • Labels: accessibility, insiders-released
  • Channels: Insiders and Stable
  • WCAG cross-referencing: enabled
  • ARIA pattern mapping: enabled
  • Briefing limit: 10 items

Users can override these defaults in preferences.md to track accessibility in any repository. Each tracked repo can specify its own label names and channel configuration. See preferences.example.md for the full configuration reference.

Response Guidelines

  • Lead with the title/description, then issue number and details - never lead with a number.
  • Always include clickable GitHub URLs.
  • Group by category, not chronologically.
  • Use bullet lists for quick updates, not tables (tables are for reports).
  • When no results are found, clearly state this, check the milestone name, and suggest alternative timeframes.
  • Format dates consistently: "February 11, 2026".
  • Explain user impact in plain language - don't just repeat the issue title.

Context Awareness

  • Current date awareness: Use to determine the correct milestone format (e.g., "February 2026").
  • If the user says "this month" -> use current month's milestone.
  • If the user says "last month" -> use previous month's milestone.
  • If the user says "today" -> add closed:YYYY-MM-DD for today's date.
  • If the user says "this week" -> add closed:>YYYY-MM-DD for 7 days ago.

Multi-Repo Support

When the user says "track owner/repo" or asks about accessibility in a specific repo:

  1. Add that repo to the session's tracked repos list.
  2. Search that repo using its own label conventions (discover labels by listing repo labels first if needed).
  3. Include results from all tracked repos in reports, clearly separated by repo.
  4. Suggest the user add the repo to preferences.md for persistent tracking.

When generating reports, always include a section for each tracked repo. The default microsoft/vscode tracking should always run unless the user explicitly excludes it.

Progress Announcements

Narrate every collection step. Never mention tool names:

text
 Scanning accessibility issues in microsoft/vscode (Insiders milestone)...
 Scanning accessibility issues in microsoft/vscode (Stable milestone)...
 Checking custom tracked repos...
 Accessibility report ready - {N} issues tracked, {M} updates since last report.

Confidence Levels

Apply to every categorized finding:

LevelWhen to Use
HighIssue confirmed in target milestone, title and labels match accessibility category
MediumIssue likely accessibility-related; category inferred from description
LowPossible edge case; include but flag for human review

Delta Tracking

Compare every report against the previous one:

StatusDefinition
FixedWas tracked; issue closed
NewNot in previous report
PersistentStill open, unchanged
RegressedWas fixed; reopened or re-filed

Escalation: if a finding is Persistent for 3+ consecutive reports, add:

Escalation: This accessibility issue has been open for {N} consecutive reports. It may warrant a community nudge or workaround documentation.

Show full SKILL.md (320 more words)Show less

Behavioral Rules

  1. Check workspace context first. Look for scan config files (.a11y-*-config.json) and previous audit reports in the workspace root.
  2. Narrate collection with / announcements for each repo scan stream - run streams in parallel.
  3. Delta-check every report. Compare against the previous report before presenting results.
  4. Confidence on every issue. Every categorized finding includes a High/Medium/Low confidence tag.
  5. Escalate persistent issues. Issues Persistent for 3+ reports get a visible escalation callout.
  6. Multi-repo parallel scanning. Run all tracked repos simultaneously - announce each as it completes.
  7. WCAG mapping required. Every finding maps to at least one WCAG 2.2 success criterion.
  8. User impact in plain language. Never just repeat the issue title; explain what the accessibility barrier is.
  9. Group by category, not repo. In cross-repo reports, group by accessibility type (focus, contrast, screen reader, etc.).
  10. Never post to GitHub without confirmation. Commenting on VS Code issues requires explicit approval.
  11. Preserve date-stamped reports. Never overwrite a previous report - always create a new dated file and offer delta comparison.
  12. Dual output always. Every report saved as both .md and .html.
  13. Include CI scanner data. When a tracked repo has the GitHub Accessibility Scanner or Lighthouse CI configured, include scanner-originated findings in reports alongside human-filed issues. Tag them with [CI Scanner] or [Lighthouse] to distinguish their source.
  14. Track Copilot fix lifecycle. For scanner issues assigned to Copilot, report fix PR status (pending, open, merged, rejected) in every report cycle.

Reference files

Read one only when the task reaches it. Do not read them all up front.

  • references/accessibility-tracker.md - Accessibility Tracker
  • references/tracked-repositories.md - Tracked Repositories, Search Patterns, Capabilities
  • references/vs-code-1-113-features-for-accessibility.md - VS Code 1.113 Features for Accessibility

Output contract

Collect findings as JSON from each specialist you dispatch, write them to .a11y-history/<timestamp>/, then render the report with node skills/a11y-core/scripts/render-report.mjs. Do not type the report by hand.

Shared rules, dispatch contract and schemas: skills/a11y-core/SKILL.md. Authoritative specifications for this skill: skills/a11y-core/references/sources.md.

© Community-Access, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 4 other files (references) in skills/insiders-a11y-tracker of Community-Access/accessibility-agents.

  • SKILL.md
  • agents/openai.yaml
  • references/accessibility-tracker.md
  • references/tracked-repositories.md
  • references/vs-code-1-113-features-for-accessibility.md

Open the folder on GitHubat commit decf6ba

Compare with similar skills

Insiders A11y Tracker next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Insiders A11y Tracker compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Insiders A11y Tracker this skillCommunity-Access/accessibility-agents423—~1.6kAutomated safety check: PassMIT
Accessibility Aria Expertmicrosoft/vscode-cosmosdb200—~3.2kAutomated safety check: PassMIT
Vscode Elements Webviewsforcedotcom/salesforcedx-vscode1k—~593Automated safety check: PassBSD-3-Clause
Web Interface Guidelines Reviewervercel-labs/openreview1.7k97 repos~308Automated safety check: PassNone
Accessibility Reviewmarkmead/hyperui12k1 repos~1.1kAutomated safety check: PassMIT
Web Animation DesignbaptisteArno/typebot.io11k2 repos~2.7kAutomated safety check: PassCustom licence

Similar skills

  • Accessibility Aria Expert

    microsoft/vscode-cosmosdb

    Official

    Detects and fixes accessibility issues in React/Fluent UI webviews.

    200 GitHub stars~3.2k tokensUpdated today
    Frontend & DesignAuto-check passed

  • Vscode Elements Webviews

    forcedotcom/salesforcedx-vscode

    Integrate @vscode-elements/elements controls into Lit webviews.

    1k GitHub stars~593 tokensUpdated today
    Frontend & DesignAuto-check passed

  • Web Interface Guidelines Reviewer

    vercel-labs/openreview

    Official

    Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my…

    1.7k GitHub starsUsed in 97 repos~308 tokens
    Frontend & DesignAuto-check passed

  • Accessibility Review

    markmead/hyperui

    Run a WCAG 2.1 AA accessibility audit on a design or page. An agent skill from markmead/hyperui.

    12k GitHub starsUsed in 1 repo~1.1k tokens
    Frontend & DesignAuto-check passed

  • Web Animation Design

    baptisteArno/typebot.io

    Guides easing, timing and animation choices for UI motion, based on a web animation course, and reviews existing animations in a before-and-after table.

    11k GitHub starsUsed in 2 repos~2.7k tokens
    Frontend & DesignAuto-check passed

  • Accessibility Fixer

    ibelick/ui-skills

    Audits and fixes HTML accessibility problems such as ARIA labels, keyboard navigation, focus management, contrast and form errors with minimal changes.

    9.6k GitHub starsUsed in 4 repos~1.2k tokens
    Frontend & DesignAuto-check passed

More from Community-Access/accessibility-agents

All 108 skills in this repo

  • A11y Core

    Community-Access/accessibility-agents

    Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.

    423 GitHub stars~1.2k tokensUpdated 17 days ago
    Auto-check passed

  • Kb Web Scanning

    Community-Access/accessibility-agents

    Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.

    423 GitHub stars~1.2k tokensUpdated 17 days ago
    Auto-check passed

  • Accessibility Lead

    Community-Access/accessibility-agents

    Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.

    423 GitHub stars~932 tokensUpdated 17 days ago
    Auto-check passed

  • Alt Text Headings

    Community-Access/accessibility-agents

    Alt text, SVGs, figures, charts, heading order, page titles and landmarks.

    423 GitHub stars~1.5k tokensUpdated 17 days ago
    Auto-check passed

  • Aria Specialist

    Community-Access/accessibility-agents

    ARIA roles, states and properties for custom widgets and dynamic content.

    423 GitHub stars~1.6k tokensUpdated 17 days ago
    Auto-check passed

  • Cognitive Accessibility

    Community-Access/accessibility-agents

    Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.

    423 GitHub stars~1.4k tokensUpdated 17 days ago
    Auto-check passed

Works with

Categories

Questions about Insiders A11y Tracker

What does Insiders A11y Tracker do?

Track accessibility changes in VS Code and other repos you follow. Insiders A11y Tracker is an agent skill from Community-Access/accessibility-agents. Track accessibility changes in VS Code and other repos you follow.

When should I use Insiders A11y Tracker?

Insiders A11y Tracker fits situations like: tasks that involve Accessibility.

How do I install Insiders A11y Tracker in Claude Code?

Run `npx skills add Community-Access/accessibility-agents --skill insiders-a11y-tracker -a claude-code`. Or copy the skill folder (skills/insiders-a11y-tracker in Community-Access/accessibility-agents) into .claude/skills/insiders-a11y-tracker in your project. Claude Code loads it when a task matches its description.

How do I install Insiders A11y Tracker in Codex?

Run `npx skills add Community-Access/accessibility-agents --skill insiders-a11y-tracker -a codex`. Or copy the skill folder (skills/insiders-a11y-tracker in Community-Access/accessibility-agents) into .agents/skills/insiders-a11y-tracker in your project. Codex loads it when a task matches its description.

Can I use Insiders A11y Tracker in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add Community-Access/accessibility-agents --skill insiders-a11y-tracker -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/insiders-a11y-tracker, .gemini/skills/insiders-a11y-tracker, .github/skills/insiders-a11y-tracker and .opencode/skills/insiders-a11y-tracker in your project.

What does Insiders A11y Tracker need to run?

Going by SKILL.md and its folder, Insiders A11y Tracker needs the command-line tools its instructions call (node).

Does Insiders A11y Tracker access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Insiders A11y Tracker safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Insiders A11y Tracker use?

Insiders A11y Tracker is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Insiders A11y Tracker use?

About 1.6k tokens (SKILL.md is roughly 6.2k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full. Its references folder adds about 3k tokens, read only when the agent opens those files.

What are the alternatives to Insiders A11y Tracker?

Skills that share tags, products or a category with Insiders A11y Tracker: Accessibility Aria Expert (microsoft/vscode-cosmosdb, 200 stars), Vscode Elements Webviews (forcedotcom/salesforcedx-vscode, 1k stars), Web Interface Guidelines Reviewer (vercel-labs/openreview, 1.7k stars) and Accessibility Review (markmead/hyperui, 12k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Insiders A11y Tracker?

Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 423 GitHub stars. The repository holds 108 skills in this directory. The repository was last updated on September 23, 2026.

Source: Community-Access/accessibility-agents on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.