Agent skill

Issue Tracker

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

GitHub issues: find, triage, review and respond, with written reports.

Install Issue Tracker

skills CLI

$ npx skills add Community-Access/accessibility-agents --skill issue-tracker -a claude-code

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

GitHub CLI

$ gh skill install Community-Access/accessibility-agents issue-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/issue-tracker .claude/skills/issue-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/

Paste into Claude Code

Install the "issue-tracker" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/issue-tracker into .claude/skills/issue-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracker", then confirm the skill loads.

Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

$skill-installer

$skill-installer install https://github.com/Community-Access/accessibility-agents/tree/main/skills/issue-tracker

Type this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.

skills CLI

$ npx skills add Community-Access/accessibility-agents --skill issue-tracker -a codex

Project install goes to .agents/skills/; add -g for ~/.codex/skills/.

GitHub CLI

$ gh skill install Community-Access/accessibility-agents issue-tracker --agent codex

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

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

Use ~/.agents/skills/ instead of .agents/skills for a personal install.

Codex skills documentation · loads skills from .agents/skills/

Paste into Codex

Install the "issue-tracker" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/issue-tracker into .agents/skills/issue-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracker", then confirm the skill loads.

Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Community-Access/accessibility-agents --skill issue-tracker -a cursor

Project install goes to .agents/skills/; add -g for ~/.cursor/skills/.

GitHub CLI

$ gh skill install Community-Access/accessibility-agents issue-tracker --agent cursor

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/issue-tracker .cursor/skills/issue-tracker && rm -rf skills-src

Use ~/.cursor/skills/ instead of .cursor/skills for a personal install.

Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/

Paste into Cursor

Install the "issue-tracker" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/issue-tracker into .cursor/skills/issue-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracker", then confirm the skill loads.

Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

gemini skills install

$ gemini skills install https://github.com/Community-Access/accessibility-agents.git --path skills/issue-tracker

--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.

skills CLI

$ npx skills add Community-Access/accessibility-agents --skill issue-tracker -a gemini-cli

Project install goes to .agents/skills/; add -g for ~/.gemini/skills/.

GitHub CLI

$ gh skill install Community-Access/accessibility-agents issue-tracker --agent gemini-cli

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/issue-tracker .gemini/skills/issue-tracker && rm -rf skills-src

Use ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.

Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/

Paste into Gemini CLI

Install the "issue-tracker" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/issue-tracker into .gemini/skills/issue-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracker", then confirm the skill loads.

Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

GitHub CLI

$ gh skill install Community-Access/accessibility-agents issue-tracker

Installs for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).

skills CLI

$ npx skills add Community-Access/accessibility-agents --skill issue-tracker -a github-copilot

Project install goes to .agents/skills/; add -g for ~/.copilot/skills/.

Manual copy

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

Use ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.

GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/

Paste into GitHub Copilot

Install the "issue-tracker" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/issue-tracker into .github/skills/issue-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracker", then confirm the skill loads.

GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

skills CLI

$ npx skills add Community-Access/accessibility-agents --skill issue-tracker -a opencode

OpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.

GitHub CLI

$ gh skill install Community-Access/accessibility-agents issue-tracker --agent opencode

Project scope by default (.agents/skills/); add --scope user for a personal install.

Manual copy

$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/issue-tracker .opencode/skills/issue-tracker && rm -rf skills-src

Use ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.

OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/

Paste into OpenCode

Install the "issue-tracker" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/issue-tracker into .opencode/skills/issue-tracker/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "issue-tracker", then confirm the skill loads.

OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.

Facts

Skill name: issue-tracker
GitHub stars: 421
Token cost: ~1.6k tokens
SKILL.md length: 691 words
Files: 4 (incl. references)
Skills in repo: 108
Repo updated: Sep 23, 2026
First seen: Oct 7, 2026
Licence: MIT

At a glance

GitHub issues: find, triage, review and respond, with written reports.

Works in 12 steps: Check workspace context first. Look for… → Priority score every item. Use the… → Confidence on every inferred action.… → …
Tasks that involve Issue triage
SKILL.md covers Issue Tracker Agent, Intelligence Layer, Progress Announcements and Confidence Levels, plus 4 more sections
Calls node

What it does

Issue Tracker is an agent skill from Community-Access/accessibility-agents. GitHub issues: find, triage, review and respond, with written reports.

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

It sits in Frontend & Design, covering Issue triage and Accessibility. It works with GitHub. 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 Issue triage
Tasks that involve Accessibility

Example prompts

“/issue-tracker”

Workflow steps

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

Check workspace context first. Look for scan config files (.a11y-*-config.json) and previous audit reports in the workspace root.
Priority score every item. Use the scoring formula from github-analytics-scoring skill before presenting any issue list.
Confidence on every inferred action. Action items derived from thread analysis get a High/Medium/Low confidence tag.
Auto-refresh over duplicate. If a workspace doc exists for this issue, offer delta update instead of regenerating.
Narrate collection steps with / announcements during search, scoring, and deep-dive phases.
Parallel data collection. Fetch issue list, linked PRs, and reactions simultaneously - don't wait serially.
Never post a comment without confirmation. Preview the comment, await approval, then submit.
Filter before showing. Default to showing only issues needing user action - offer to expand to all on request.
Surface community sentiment. Always show reaction counts on high-interest issues.
Saved searches from preferences.md. Auto-load named filters if preferences.md exists - don't ask the user to repeat them.
Never auto-close or auto-lock. Always confirm with the user before any state-changing action.
Dual output always. Every workspace document is saved as both .md and .html.

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

Issue Tracker loads about 1.6k tokens when it runs, and up to ~8.5k if it reads all its reference files. Until then it costs about 21 tokens; SKILL.md has 691 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it: ~21
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: ~8.5k

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). 691 words, ~1,563 tokens.

Download SKILL.mdSave it as .claude/skills/issue-tracker/SKILL.md (or your agent's skills folder). This skill also uses 3 other files; get the full folder from GitHub.

name: issue-tracker
description: GitHub issues: find, triage, review and respond, with written reports.
license: MIT
disable-model-invocation: true
metadata.tier: specialist
metadata.domain: github
metadata.output: report
metadata.effort: medium
metadata.title: Issue Tracker

Issue Tracker Agent

Shared instructions

Skills: github-workflow-standards, github-scanning, github-analytics-scoring, github-a11y-scanner, lighthouse-scanner

You are the user's GitHub issue command center -- a senior engineering teammate who doesn't just fetch data but actively triages, prioritizes, cross-references, and produces actionable review documents. You think ahead, surface what matters, and save the user hours of tab-switching.

Critical: You MUST generate both a .md and .html version of every workspace document. Follow the dual output and accessibility standards in shared-instructions.md.

Intelligence Layer

Priority Scoring

Internally score each issue when listing:

+3: User was @mentioned and hasn't responded
+3: Tied to an upcoming release milestone
+2: P0, P1, critical, urgent, blocker label
+2: New comments from others since user's last comment
+2: High community interest (5+ positive reactions)
+1: bug label
+1: Assigned to user
+1: Has active related discussion
-1: wontfix, duplicate, question label
-2: No activity >30 days

Sort by score descending. Show the signal column based on this.

Smart Action Item Inference

When generating documents, analyze the conversation to create action items:

If the last comment is a question directed at the user --> "Respond to @X's question about {topic}"
If the issue has a needs-info label --> "Provide requested information about {topic}"
If the issue is stale and assigned to user --> "Update status or close -- no activity for {N} days"
If a PR is linked and merged --> "Verify fix and close issue -- PR #N: Title was merged on {date}"
If tests or repro steps were requested --> "Add test case / reproduction steps"
If the issue has high community interest --> "Consider prioritizing -- {N} community reactions"
If a discussion thread is active --> "Check Discussion: Title for related context"
If a release is approaching --> "Release v{X} includes this -- verify before deadline"

Auto-Refresh

If a workspace document already exists for an issue, offer to update it rather than creating a duplicate. Diff the new data against the existing file and show what changed.

Progress Announcements

Narrate every data collection step. Never mention tool names:

text

 Searching issues across repos...
 Scoring and prioritizing results...
 Pulling linked PRs and discussions...
 Issue dashboard ready - {N} items found, {M} need your attention.

For deep-dive on a single issue:

text

 Fetching issue #{N} thread, reactions, and timeline...
 Checking linked PRs and discussions...
 Ready. Last activity: {date}.

Confidence Levels

Apply to triage findings and action item inferences:

Level	When to Use
High	Clear signal - e.g., question directed at user is the last comment
Medium	Likely needs action; context could change it
Low	Pattern detected; human judgment required

Format in triage output:

text

| # | Title | Priority Score | Confidence | Action |
|---|-------|---------------|------------|--------|
| 42 | Auth flow broken | 9 | **High** | Respond to @alice's question |

Delta Tracking

When a workspace document already exists for an issue:

Status	Definition
Resolved	Issue was open; now closed
New	Not in previous document
Persistent	Still open, unchanged
Regressed	Was closed; reopened

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

Behavioral Rules

Check workspace context first. Look for scan config files (.a11y-*-config.json) and previous audit reports in the workspace root.
Priority score every item. Use the scoring formula from github-analytics-scoring skill before presenting any issue list.
Confidence on every inferred action. Action items derived from thread analysis get a High/Medium/Low confidence tag.
Auto-refresh over duplicate. If a workspace doc exists for this issue, offer delta update instead of regenerating.
Narrate collection steps with / announcements during search, scoring, and deep-dive phases.
Parallel data collection. Fetch issue list, linked PRs, and reactions simultaneously - don't wait serially.
Never post a comment without confirmation. Preview the comment, await approval, then submit.
Filter before showing. Default to showing only issues needing user action - offer to expand to all on request.
Surface community sentiment. Always show reaction counts on high-interest issues.
Saved searches from preferences.md. Auto-load named filters if preferences.md exists - don't ask the user to repeat them.
Never auto-close or auto-lock. Always confirm with the user before any state-changing action.
Dual output always. Every workspace document is saved as both .md and .html.
Cross-reference automatically. Detect linked PRs, duplicates, and related discussions without being asked.
Project board status visible. Always surface which column an issue is in, and flag if it's stuck.

Reference files

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

references/core-capabilities.md - Core Capabilities
references/workflow.md - Workflow

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.

Files

SKILL.md and 3 other files (references) in skills/issue-tracker of Community-Access/accessibility-agents.

SKILL.md
agents/openai.yaml
references/core-capabilities.md
references/workflow.md

Open the folder on GitHubat commit decf6ba

Compare with similar skills

Issue 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.

Issue Tracker compared with similar skills
Skill	Stars	Used in	Tokens	Auto-check	Licence	Repo updated
Issue Tracker this skillCommunity-Access/accessibility-agents	421	—	~1.6k	Automated safety check: Pass	MIT	14 days ago
OpenClaw Design Auditopenclaw/clawhub	9.5k	—	~498	Automated safety check: Pass	MIT	yesterday
Scraps Reviewgetsentry/sentry	45k	—	~1.2k	Automated safety check: Notes	Custom licence	today
Ant Designkqcoxn/MaaPipelineEditor	408	1 repos	~1.1k	Automated safety check: Pass	MIT	2 days ago
Lofisu Personazclllyybb/lofisu-identity-engine	453	—	~2.8k	Automated safety check: Pass	Unlicense	3 mo ago
Port Upstreamgjtorikian/tailwind_merge	148	—	~1.9k	Automated safety check: Pass	MIT	25 days ago

Similar skills

OpenClaw Design Audit
openclaw/clawhub
Audits OpenClaw frontend code and rendered pages for token misuse, reimplemented primitives, accessibility and responsive defects and off-brand copy, with an evidence-based report.
9.5k GitHub stars~498 tokensUpdated yesterday
Frontend & DesignAuto-check passed
Scraps Review
getsentry/sentry
Official
Filter large Sentry Scraps design-system migration PRs for review by separating mechanical import-path changes, generated baseline updates, snapshot mocks, and pure renames from substantive…
45k GitHub stars~1.2k tokensUpdated today
Frontend & DesignAuto-check: notes
Ant Design
kqcoxn/MaaPipelineEditor
Decision guide for antd 6.x, Ant Design Pro 5/ProComponents, Ant Design X v2, and the offline @ant-design/cli.
408 GitHub starsUsed in 1 repo~1.1k tokens
Frontend & DesignAuto-check passed
Lofisu Persona
zclllyybb/lofisu-identity-engine
LofiSu的行为人格Skill。基于GitHub公开数据(282次commit/150次README迭代/50+fork/100+contribution) 的Codex深度挖掘分析报告+小红书卖课行为报告的系统蒸馏，提炼6个核心心智模型、8条决策启发式和完整的表达DNA。
453 GitHub stars~2.8k tokensUpdated 3 mo ago
Frontend & DesignAuto-check passed
Port Upstream
gjtorikian/tailwind_merge
Check GitHub notifications for upstream dcastil/tailwind-merge pull requests and port merged ones into this Ruby gem (branch, translated code, tests, commit, PR).
148 GitHub stars~1.9k tokensUpdated 25 days ago
Frontend & DesignAuto-check passed
Maplibre Cartography
maplibre/maplibre-agent-skills
Cartographic principles for MapLibre GL JS — label and symbol legibility on imagery vs.
151 GitHub stars~4.8k tokensUpdated 3 days ago
Frontend & DesignAuto-check passed

Questions about Issue Tracker

What does Issue Tracker do?

GitHub issues: find, triage, review and respond, with written reports. Issue Tracker is an agent skill from Community-Access/accessibility-agents. GitHub issues: find, triage, review and respond, with written reports.

When should I use Issue Tracker?

Issue Tracker fits situations like: tasks that involve Issue triage; tasks that involve Accessibility.

How do I install Issue Tracker in Claude Code?

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

How do I install Issue Tracker in Codex?

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

Can I use Issue 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 issue-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/issue-tracker, .gemini/skills/issue-tracker, .github/skills/issue-tracker and .opencode/skills/issue-tracker in your project.

What does Issue Tracker need to run?

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

Does Issue 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 Issue 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 Issue Tracker use?

Issue 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 Issue Tracker use?

About 1.6k tokens (SKILL.md is roughly 6.3k 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 6.9k tokens, read only when the agent opens those files.

What are the alternatives to Issue Tracker?

Skills that share tags, products or a category with Issue Tracker: OpenClaw Design Audit (openclaw/clawhub, 9.5k stars), Scraps Review (getsentry/sentry, 45k stars), Ant Design (kqcoxn/MaaPipelineEditor, 408 stars) and Lofisu Persona (zclllyybb/lofisu-identity-engine, 453 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Issue Tracker?

Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 421 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.

Install Issue Tracker

Facts

At a glance

What it does

When your agent uses it

Example prompts

Workflow steps

What it can do on your machine

Tool permissions

Runs code

Network

Credentials

Context cost

Safety

SKILL.md

Issue Tracker Agent

Intelligence Layer

Priority Scoring

Smart Action Item Inference

Auto-Refresh

Progress Announcements

Confidence Levels

Delta Tracking

Behavioral Rules

Reference files

Output contract

Files

Compare with similar skills

Similar skills

More from Community-Access/accessibility-agents

Related

Questions about Issue Tracker