Scraps Review
getsentry/sentry
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…
GitHub metrics: velocity, review turnaround, churn and bottlenecks.
Install Analytics
$ npx skills add Community-Access/accessibility-agents --skill analytics -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Community-Access/accessibility-agents analytics --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/analytics .claude/skills/analytics && rm -rf skills-srcUse ~/.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/
Install the "analytics" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/analytics into .claude/skills/analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analytics", 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 install https://github.com/Community-Access/accessibility-agents/tree/main/skills/analyticsType 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.
$ npx skills add Community-Access/accessibility-agents --skill analytics -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Community-Access/accessibility-agents analytics --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/analytics .agents/skills/analytics && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "analytics" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/analytics into .agents/skills/analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analytics", 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.
$ npx skills add Community-Access/accessibility-agents --skill analytics -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Community-Access/accessibility-agents analytics --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/analytics .cursor/skills/analytics && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "analytics" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/analytics into .cursor/skills/analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analytics", 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 https://github.com/Community-Access/accessibility-agents.git --path skills/analytics--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add Community-Access/accessibility-agents --skill analytics -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Community-Access/accessibility-agents analytics --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/analytics .gemini/skills/analytics && rm -rf skills-srcUse ~/.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/
Install the "analytics" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/analytics into .gemini/skills/analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analytics", 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.
$ gh skill install Community-Access/accessibility-agents analyticsInstalls 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).
$ npx skills add Community-Access/accessibility-agents --skill analytics -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/analytics .github/skills/analytics && rm -rf skills-srcUse ~/.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/
Install the "analytics" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/analytics into .github/skills/analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analytics", 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.
$ npx skills add Community-Access/accessibility-agents --skill analytics -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install Community-Access/accessibility-agents analytics --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/analytics .opencode/skills/analytics && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "analytics" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/analytics into .opencode/skills/analytics/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "analytics", 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
analytics- GitHub stars
- 422
- Token cost
- ~1.4k tokens
- SKILL.md length
- 707 words
- Files
- 3 (incl. references)
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
GitHub metrics: velocity, review turnaround, churn and bottlenecks.
- Works in 7 steps: Review Turnaround Metrics -- Average… → Issue Resolution Metrics -- Average time… → Contribution Activity -- Commits, PRs… → …
- Frontend & Design work in your project
- SKILL.md covers Analytics & Insights Agent, Core Capabilities, Intelligence Layer and Behavioral Rules, plus 2 more sections
- Calls node
What it does
Analytics is an agent skill from Community-Access/accessibility-agents. GitHub metrics: velocity, review turnaround, churn and bottlenecks.
Its SKILL.md is about 1.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 4 other files, including reference files (for example `agents/openai.yaml` and `references/workflow.md`).
It sits in Frontend & Design. 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
- Frontend & Design work in your project
Example prompts
- “/analytics”
Workflow steps
7 steps, taken from the first numbered list in SKILL.md.
- Review Turnaround Metrics -- Average time from PR open to first review, to approval, and to merge. Breakdown by repo, author, and reviewer.
- Issue Resolution Metrics -- Average time to close, comments before close, reopen rates, label distribution.
- Contribution Activity -- Commits, PRs authored/reviewed, issues opened/closed per person per period.
- Team Velocity -- Throughput trends, WIP counts, cycle time, week-over-week and month-over-month comparisons.
- Bottleneck Detection -- PRs waiting >7 days for review, issues with no response, overloaded reviewers, stuck items.
- Code Churn Analysis -- Files most frequently changed, hotspot detection, change coupling patterns.
- Comparative Insights -- Individual vs. team average, period-over-period trends.
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
Analytics loads about 1.4k tokens when it runs, and up to ~5.3k if it reads all its reference files. Until then it costs about 19 tokens; SKILL.md has 707 words of instructions outside code blocks.
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). 707 words, ~1,405 tokens.
Download SKILL.mdSave it as
.claude/skills/analytics/SKILL.md (or your agent's skills folder). This skill also uses 2 other files; get the full folder from GitHub.- name
- analytics
- description
- GitHub metrics: velocity, review turnaround, churn and bottlenecks.
- license
- MIT
- disable-model-invocation
- true
- metadata.tier
- specialist
- metadata.domain
- github
- metadata.output
- report
- metadata.effort
- medium
- metadata.title
- Analytics
Analytics & Insights Agent
Skills: github-workflow-standards, github-scanning, github-analytics-scoring
You are the user's GitHub analytics engine -- a data-driven teammate who turns raw GitHub activity into actionable insights. You track metrics, spot trends, detect bottlenecks, and help the team understand where time is being spent and where improvements can be made.
Critical: You MUST generate both a .md and .html version of every analytics document. Follow the dual output and accessibility standards in shared-instructions.md.
Core Capabilities
- Review Turnaround Metrics -- Average time from PR open to first review, to approval, and to merge. Breakdown by repo, author, and reviewer.
- Issue Resolution Metrics -- Average time to close, comments before close, reopen rates, label distribution.
- Contribution Activity -- Commits, PRs authored/reviewed, issues opened/closed per person per period.
- Team Velocity -- Throughput trends, WIP counts, cycle time, week-over-week and month-over-month comparisons.
- Bottleneck Detection -- PRs waiting >7 days for review, issues with no response, overloaded reviewers, stuck items.
- Code Churn Analysis -- Files most frequently changed, hotspot detection, change coupling patterns.
- Comparative Insights -- Individual vs. team average, period-over-period trends.
Intelligence Layer
Anomaly Detection
Flag unusual patterns automatically:
- Sudden spike in issue creation (2x normal rate)
- PR merge time suddenly increasing
- A team member's activity dropping significantly
- A repo's CI failure rate increasing
- Unusual file churn in a normally stable area
Load Balancing Recommendations
When review load is unbalanced:
- Identify who has capacity (fewest pending reviews relative to their normal load)
- Suggest specific redistributions: "Move 2 of @charlie's reviews to @dana -- she has capacity and expertise in frontend."
- Factor in team roster expertise areas from preferences.
Trend Narrative
Don't just show numbers -- tell the story:
- "Your team merged 15 PRs this sprint, up from 12 last sprint. The improvement came from faster reviews -- turnaround dropped from 2.1 days to 1.4 days after you redistributed @charlie's review load."
- "Issue resolution time increased this month because 3 complex bugs took 10+ days each. Excluding those outliers, your resolution time actually improved."
Predictive Signals
When enough data is available:
- "At current velocity, the v2.0 milestone will complete in ~3 weeks. You have 8 items remaining."
- "Your review backlog is growing at 2 PRs/week faster than you clear it. Consider a review sprint."
- "This repo's issue creation rate suggests you'll hit 100 open issues by end of month."
Show full SKILL.md (326 more words)Show less
Behavioral Rules
- Announce progress throughout data collection. Use the
/pattern before and after each data collection step. Never silently collect data for minutes with no user feedback. - Generate both .md and .html outputs. Always. Both files every time. Verify they were written before completing.
- Tag all bottleneck findings with confidence levels. High/medium/low. Helps users know what to act on vs. verify.
- Compare against previous reports when they exist. Delta tracking (Resolved/New/Persistent) is more valuable than a standalone snapshot. Check
.github/reviews/analytics/at startup. - Escalate persistent bottlenecks. If same bottleneck appears in 3+ consecutive reports, flag for escalation.
- Always include period comparison. Never show just current numbers - always show last period and direction.
- Tell the story, not just the numbers. The Trend Narrative is not optional - it turns raw metrics into actionable insight.
- Flag anomalies proactively. Don't wait to be asked - surface sudden spikes, drops, and unusual patterns.
- Respect preferences.md scope. The user's configured discovery mode, include/exclude lists, and per-repo tracking settings control what's analyzed.
- Show compact summary in chat, full detail in files. Don't dump the entire table output into chat - lead with the 3-5 key insights, then point to the saved document.
- Never silence review load imbalance. If a reviewer is overloaded, always surface it - it's the single most actionable bottleneck.
- Verify reports exist before finishing. Before ending, confirm
.mdand.htmlfiles exist at the expected paths and are non-empty. - Default scope is 30 days, all accessible repos. State the scope at the top of every response. Offer to change it.
Reference files
Read one only when the task reaches it. Do not read them all up front.
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.
© 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 2 other files (references) in skills/analytics of Community-Access/accessibility-agents.
- SKILL.md
- agents/openai.yaml
- references/workflow.md
Open the folder on GitHubat commit decf6ba
Compare with similar skills
Analytics 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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Analytics this skillCommunity-Access/accessibility-agents | 422 | — | ~1.4k | Automated safety check: Pass | MIT | |
| Scraps Reviewgetsentry/sentry | 46k | — | ~1.2k | Automated safety check: Notes | Custom licence | |
| Readme I18nY80/bmm | 344 | 2 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Uncodixfypdsuwwz/chatgpt-vue3-light-mvp | 578 | 2 repos | ~3k | Automated safety check: Pass | MIT | |
| Paper2htmlQuZhan51496/paper2anything | 468 | — | ~3.3k | Automated safety check: Notes | Apache-2.0 | |
| Fumadocsbetter-notify/better-notify | 313 | — | ~2.3k | Automated safety check: Pass | MIT |
Similar skills
- Official
Readme I18n
Y80/bmm
A skill your agent uses when the user wants to translate a repository README, make a repo multilingual, localize docs, add a language switcher, internationalize the README, or update localized…
Uncodixfy
pdsuwwz/chatgpt-vue3-light-mvp
Prevents generic AI/Codex UI patterns when generating frontend code.
Paper2html
QuZhan51496/paper2anything
Convert an academic paper PDF into a publish-ready, self-contained single-page project homepage (a self-contained index.html) — the kind of paper landing page researchers host on GitHub Pages.
Fumadocs
better-notify/better-notify
A skill your agent uses when writing MDX documentation pages for a Fumadocs project — frontmatter, meta.json, page ordering, and fumadocs-ui React components available inside MDX content.
Great Docs
pymc-labs/pathmc
Generate documentation sites for Python packages with Great Docs.
More from Community-Access/accessibility-agents
All 108 skills in this repoA11y Core
Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules.
Kb Web Scanning
Community-Access/accessibility-agents
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Accessibility Lead
Community-Access/accessibility-agents
Web UI accessibility lead. An agent skill from Community-Access/accessibility-agents.
Alt Text Headings
Community-Access/accessibility-agents
Alt text, SVGs, figures, charts, heading order, page titles and landmarks.
Aria Specialist
Community-Access/accessibility-agents
ARIA roles, states and properties for custom widgets and dynamic content.
Cognitive Accessibility
Community-Access/accessibility-agents
Plain language, WCAG 2.2 cognitive criteria, COGA guidance and auth UX.
Related
Works with
Categories
Questions about Analytics
What does Analytics do?
GitHub metrics: velocity, review turnaround, churn and bottlenecks. Analytics is an agent skill from Community-Access/accessibility-agents. GitHub metrics: velocity, review turnaround, churn and bottlenecks.
When should I use Analytics?
Analytics fits situations like: frontend & Design work in your project.
How do I install Analytics in Claude Code?
Run `npx skills add Community-Access/accessibility-agents --skill analytics -a claude-code`. Or copy the skill folder (skills/analytics in Community-Access/accessibility-agents) into .claude/skills/analytics in your project. Claude Code loads it when a task matches its description.
How do I install Analytics in Codex?
Run `npx skills add Community-Access/accessibility-agents --skill analytics -a codex`. Or copy the skill folder (skills/analytics in Community-Access/accessibility-agents) into .agents/skills/analytics in your project. Codex loads it when a task matches its description.
Can I use Analytics 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 analytics -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/analytics, .gemini/skills/analytics, .github/skills/analytics and .opencode/skills/analytics in your project.
What does Analytics need to run?
Going by SKILL.md and its folder, Analytics needs the command-line tools its instructions call (node).
Does Analytics 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 Analytics 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 Analytics use?
Analytics 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 Analytics use?
About 1.4k tokens (SKILL.md is roughly 5.6k 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 3.9k tokens, read only when the agent opens those files.
What are the alternatives to Analytics?
Skills that share tags, products or a category with Analytics: Scraps Review (getsentry/sentry, 46k stars), Readme I18n (Y80/bmm, 344 stars), Uncodixfy (pdsuwwz/chatgpt-vue3-light-mvp, 578 stars) and Paper2html (QuZhan51496/paper2anything, 468 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Analytics?
Community-Access (a GitHub organization) maintains it in Community-Access/accessibility-agents, which has 422 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.