Repomix Browser Extension Developer
yamadashy/repomix
Use this skill when developing or maintaining browser extension code in the `browser/` directory, including Chrome/Firefox/Edge compatibility, content…
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Install Kb GitHub Analytics Scoring
$ npx skills add Community-Access/accessibility-agents --skill kb-github-analytics-scoring -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Community-Access/accessibility-agents kb-github-analytics-scoring --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/kb-github-analytics-scoring .claude/skills/kb-github-analytics-scoring && 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 "kb-github-analytics-scoring" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-github-analytics-scoring into .claude/skills/kb-github-analytics-scoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-github-analytics-scoring", 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/kb-github-analytics-scoringType 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 kb-github-analytics-scoring -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Community-Access/accessibility-agents kb-github-analytics-scoring --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/kb-github-analytics-scoring .agents/skills/kb-github-analytics-scoring && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "kb-github-analytics-scoring" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-github-analytics-scoring into .agents/skills/kb-github-analytics-scoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-github-analytics-scoring", 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 kb-github-analytics-scoring -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Community-Access/accessibility-agents kb-github-analytics-scoring --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/kb-github-analytics-scoring .cursor/skills/kb-github-analytics-scoring && 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 "kb-github-analytics-scoring" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-github-analytics-scoring into .cursor/skills/kb-github-analytics-scoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-github-analytics-scoring", 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/kb-github-analytics-scoring--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 kb-github-analytics-scoring -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Community-Access/accessibility-agents kb-github-analytics-scoring --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/kb-github-analytics-scoring .gemini/skills/kb-github-analytics-scoring && 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 "kb-github-analytics-scoring" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-github-analytics-scoring into .gemini/skills/kb-github-analytics-scoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-github-analytics-scoring", 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 kb-github-analytics-scoringInstalls 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 kb-github-analytics-scoring -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/kb-github-analytics-scoring .github/skills/kb-github-analytics-scoring && 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 "kb-github-analytics-scoring" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-github-analytics-scoring into .github/skills/kb-github-analytics-scoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-github-analytics-scoring", 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 kb-github-analytics-scoring -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 kb-github-analytics-scoring --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/kb-github-analytics-scoring .opencode/skills/kb-github-analytics-scoring && 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 "kb-github-analytics-scoring" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-github-analytics-scoring into .opencode/skills/kb-github-analytics-scoring/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-github-analytics-scoring", 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
kb-github-analytics-scoring- GitHub stars
- 422
- Token cost
- ~2.4k tokens
- SKILL.md length
- 830 words
- Files
- 2
- Skills in repo
- 108
- Repo updated
- First seen
- Licence
- MIT
At a glance
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
- Development work in your project
- SKILL.md covers GitHub Analytics Scoring, Repository Health Score, Score Grades and Priority Scoring for Issues, plus 10 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Kb GitHub Analytics Scoring is an agent skill from Community-Access/accessibility-agents. Reference data, not a reviewer. Score repository health (0-100, A-F grades), priorities, and delta tracking. Includes velocity metrics, confidence levels, and bottleneck detection.
Its SKILL.md is about 2.4k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `agents/openai.yaml`).
It sits in Development. 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
- Development work in your project
Example prompts
- “/kb-github-analytics-scoring”
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
No scripts in the folder and no shell commands in SKILL.md (its code samples are markdown).
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
Kb GitHub Analytics Scoring loads about 2.4k tokens when it runs. Until then it costs about 52 tokens; SKILL.md has 830 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). 830 words, ~2,380 tokens.
Download SKILL.mdSave it as
.claude/skills/kb-github-analytics-scoring/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- kb-github-analytics-scoring
- description
- Reference data, not a reviewer. Score repository health (0-100, A-F grades), priorities, and delta tracking. Includes velocity metrics, confidence levels, and bottleneck detection.
- license
- MIT
- disable-model-invocation
- true
- user-invocable
- false
- metadata.tier
- reference
- metadata.domain
- cross-cutting
- metadata.output
- none
- metadata.effort
- low
- metadata.title
- Github Analytics Scoring
GitHub Analytics Scoring
Repository Health Score
Health Score = 100 - (sum of weighted penalties)
Penalties - CI & Reliability:
Failing workflow, high confidence: -10 points
Flaky test (3+ failures/week): - 5 points
No CI configured: - 8 points
Penalties - Issues & PRs:
Critical unresolved bug (P0): -10 points
Security alert (critical severity): -10 points
Security alert (high severity): - 5 points
PR open >14 days (stale): - 3 points each (max -9)
Issue @mentioned, no response >7 days: - 5 points each (max -10)
>10 open issues with no labels/triage: - 3 points
Penalties - Community Health:
No CONTRIBUTING.md: - 5 points
No CODE_OF_CONDUCT.md: - 3 points
No branch protection on main: - 5 points
0 open "good first issue" labels: - 2 points
Floor: 0 (minimum score)Score Grades
Each score, with its grade and meaning.
| Score | Grade | Meaning |
|---|---|---|
| 90-100 | A | Excellent - healthy repo, minimal issues |
| 75-89 | B | Good - minor issues, well-managed |
| 50-74 | C | Needs attention - multiple signals requiring action |
| 25-49 | D | Poor - significant problems impacting velocity |
| 0-24 | F | Critical - major issues blocking team progress |
Priority Scoring for Issues
Internally score each issue to determine sort order in dashboards and reports:
| Signal | Points |
|---|---|
| User @mentioned and hasn't responded | +5 |
P0, P1, critical, urgent, blocker label | +3 |
| Tied to upcoming release milestone | +3 |
| New comments from others since user's last activity | +2 |
| High community interest (5+ positive reactions) | +2 |
bug label | +1 |
| Assigned to user | +1 |
| Active related discussion thread | +1 |
wontfix, duplicate, question label | -1 |
| No activity >14 days | -2 |
Priority Scoring for Pull Requests
Each signal, with its points.
| Signal | Points |
|---|---|
| Review requested, user hasn't reviewed | +5 |
| PR has "changes requested" - author needs to update | +4 |
| PR is approved and ready to merge | +3 |
| Targets a release branch with upcoming deadline | +3 |
| CI failed on this PR | +2 |
| Merge conflicts present | +2 |
| High community interest (5+ positive reactions) | +2 |
| New comments on the PR | +1 |
| Active discussion thread linked to this PR | +1 |
| Draft PR | -1 |
| No activity >7 days | -2 |
Priority Scoring for Discussions
Each signal, with its points.
| Signal | Points |
|---|---|
| User was @mentioned | +3 |
| High activity (10+ comments in 24h) | +2 |
| Linked to an issue/PR the user owns | +1 |
| No activity >7 days | -1 |
Confidence Levels for Analytics Findings
Apply confidence levels to all bottleneck findings, health score deductions, and anomaly detections. Every finding in a report MUST include its confidence level.
| Level | When to Use | Impact on Report |
|---|---|---|
| High | Multiple corroborating signals, definitively observed (e.g., CI has failed 5 times this week, confirmed by logs) | Report as fact; recommend remediation |
| Medium | Found by one source, likely issue (e.g., PR open 14 days but author may be on leave) | Report as finding; suggest investigation |
| Low | Possible pattern, needs human review (e.g., velocity seems low but may be seasonal) | Flag as observation; don't deduct from score |
Confidence Tag Format in Reports
| Finding | Severity | Confidence | Recommendation |
|---------|----------|-----------|----------------|
| 3 PRs stale >14 days | High | **High** | Assign reviewers or close |
| Velocity 40% below 4-week avg | Medium | **Medium** | Verify - may be holiday period |
| Issue activity spike on Fridays | Low | **Low** | Monitor for 2 weeks before acting |Delta Tracking
When re-running an analysis against a previous report, classify every finding by change status:
| Status | Definition |
|---|---|
| Fixed | Was in previous report; no longer present |
| New | Not in previous report; appears now |
| Persistent | Remains from previous report, unchanged |
| Regressed | Was previously fixed but has returned |
Delta Report Section Format
## Changes Since Last Report ({previous date})
| Change | Finding | Details |
|--------|---------|---------|
| Fixed | 3 stale PRs resolved | Team cleared the backlog |
| New | CI failing on main | Build broke in last 24h |
| Persistent (#3) | Velocity 30% below baseline | Third consecutive week |
| Regressed | Security alert reopened | lodash advisory re-filed |
**Progress:** {N} fixed, {M} new, {P} persistent, {Q} regressed
**Score change:** {current_score} ({+/-N} from {previous_score})Escalation Rule
If a finding is Persistent for 3+ consecutive reports, escalate:
Escalation: [{Finding}] has been present for {N} consecutive reports. Consider a team discussion or explicit ownership assignment to resolve this.
Velocity Metrics
Each metric, with its formula, healthy, warning and critical.
| Metric | Formula | Healthy | Warning | Critical |
|---|---|---|---|---|
| PR merge rate | PRs merged / week | >3/week | 1-3/week | <1/week |
| Issue close rate | Issues closed / week | >5/week | 2-5/week | <2/week |
| Review turnaround | Avg hours PR open before first review | <24h | 24-72h | >72h |
| Issue response time | Avg hours until first team response | <8h | 8-48h | >48h |
| Stale PR ratio | PRs open >14 days / total open PRs | <10% | 10-30% | >30% |
| CI reliability | Passing runs / total runs (7-day) | >95% | 80-95% | <80% |
Show full SKILL.md (315 more words)Show less
Contributor Metrics
Each metric, with its formula and notes.
| Metric | Formula | Notes |
|---|---|---|
| PR commit ratio | Commits / PRs merged | High ratio = large PRs, consider splitting |
| Review coverage | PRs reviewed by others / total PRs merged | Low = single-contributor bottleneck |
| First-time contributor rate | New contributors / total active contributors | Healthy community growth signal |
| Contributor retention | Active last month AND active this month / active last month | Engagement health |
| Bus factor | Min contributors whose departure halts 50%+ of commits | <3 is high risk |
Bottleneck Categories
Each category, with its signals and example finding.
| Category | Signals | Example Finding |
|---|---|---|
| Review bottleneck | High PR open time, review-requested PRs >3 days | "4 PRs waiting for review >3 days - assign or redistribute" |
| CI bottleneck | Frequent failures, long runtimes | "Test suite 45min avg - 2x slower than 4-week average" |
| Stale work | Issues/PRs with no activity >14 days | "7 issues open >30 days with no recent comments" |
| Knowledge concentration | 80%+ commits from one contributor | "3 of 4 core modules have only one contributor - bus factor 1" |
| Response lag | >24h average first response to new issues | "Average first response: 38h - community may feel unsupported" |
| Security debt | Open Dependabot alerts unresolved >7 days | "2 critical alerts open for 12 days" |
| Release congestion | >10 merged PRs unreleased | "11 merged PRs awaiting release - coordinate cut date" |
Trend Classification
Each trend, with its definition.
| Trend | Definition |
|---|---|
| Improving | Score increased 5+ points vs previous report |
| Stable | Score within 5 points of previous report |
| Declining | Score decreased 5+ points vs previous report |
| Recovering | Score increased after 2+ consecutive Declining reports |
| New | No previous report to compare |
Scorecard Output Format
Single Repo
## Repository Health Score
| Metric | Value |
|--------|-------|
| Repo | [owner/repo](url) |
| Score | {0-100} |
| Grade | {A-F} |
| Trend | {Improving / Stable / Declining} |
| Open Security Alerts | {count} |
| Stale PRs (>14 days) | {count} |
| CI Reliability (7-day) | {%} |
| Unanswered @mentions | {count} |Multi-Repo Scorecard
## Repository Health Scorecard
| Repo | Score | Grade | Trend | Critical Issues | Notes |
|------|-------|-------|-------|-----------------|-------|
| owner/repo-a | 88 | B | Improving | 0 | |
| owner/repo-b | 54 | C | Declining | 1 | Security alert unresolved |
| owner/repo-c | 22 | F | Stable | 3 | Review bottleneck + stale PRs |
| **Average** | **54.7** | **C** | - | **4** | |Sprint & Iteration Metrics
When project boards are configured, track sprint metrics:
| Metric | Formula |
|---|---|
| Sprint completion rate | Done items / total sprint items x 100 |
| Carryover rate | Items moved to next sprint / planned items |
| Cycle time | Average days from "In Progress" to "Done" |
| Throughput | Items completed per sprint |
| Blocked rate | Items in "Blocked" state / total in-progress |
© 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 1 other file in skills/kb-github-analytics-scoring of Community-Access/accessibility-agents.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit decf6ba
Compare with similar skills
Kb GitHub Analytics Scoring 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 |
|---|---|---|---|---|---|---|
| Kb GitHub Analytics Scoring this skillCommunity-Access/accessibility-agents | 422 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Repomix Browser Extension Developeryamadashy/repomix | 29k | 1 repos | ~288 | Automated safety check: Pass | MIT | |
| Docs AuthoringTracecatHQ/tracecat | 3.8k | — | ~3.1k | Automated safety check: Notes | AGPL-3.0 | |
| README Badges and Headersjal-co/shieldcn | 916 | — | ~4.3k | Automated safety check: Pass | MIT | |
| Valgocohesivestack/valgo | 508 | — | ~2.4k | Automated safety check: Pass | MIT | |
| Implement GitHub FeatureAgnosticUI/agnosticui | 827 | — | ~1.6k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Docs Authoring
TracecatHQ/tracecat
A skill your agent uses when adding or updating documentation pages in an existing docs site.
README Badges and Headers
jal-co/shieldcn
Adds shadcn/ui-styled README badges, badge groups, download charts, header banners and sponsor or contributor grids using the shieldcn service.
Valgo
cohesivestack/valgo
Add, refactor, debug, review, explain, or migrate type-safe validation in consumer Go applications using github.com/cohesivestack/valgo.
Implement GitHub Feature
AgnosticUI/agnosticui
Design and implement a new feature or component from a GitHub issue.
Create PR
UniClipboard/UniClipboard
Push the current branch and open a GitHub pull request against main.
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 Kb GitHub Analytics Scoring
What does Kb GitHub Analytics Scoring do?
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents. Kb GitHub Analytics Scoring is an agent skill from Community-Access/accessibility-agents. Reference data, not a reviewer.
When should I use Kb GitHub Analytics Scoring?
Kb GitHub Analytics Scoring fits situations like: development work in your project.
How do I install Kb GitHub Analytics Scoring in Claude Code?
Run `npx skills add Community-Access/accessibility-agents --skill kb-github-analytics-scoring -a claude-code`. Or copy the skill folder (skills/kb-github-analytics-scoring in Community-Access/accessibility-agents) into .claude/skills/kb-github-analytics-scoring in your project. Claude Code loads it when a task matches its description.
How do I install Kb GitHub Analytics Scoring in Codex?
Run `npx skills add Community-Access/accessibility-agents --skill kb-github-analytics-scoring -a codex`. Or copy the skill folder (skills/kb-github-analytics-scoring in Community-Access/accessibility-agents) into .agents/skills/kb-github-analytics-scoring in your project. Codex loads it when a task matches its description.
Can I use Kb GitHub Analytics Scoring 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 kb-github-analytics-scoring -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/kb-github-analytics-scoring, .gemini/skills/kb-github-analytics-scoring, .github/skills/kb-github-analytics-scoring and .opencode/skills/kb-github-analytics-scoring in your project.
What does Kb GitHub Analytics Scoring need to run?
SKILL.md names no scripts, command-line tools or credentials: Kb GitHub Analytics Scoring is instructions for the agent only.
Does Kb GitHub Analytics Scoring 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 Kb GitHub Analytics Scoring 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 Kb GitHub Analytics Scoring use?
Kb GitHub Analytics Scoring 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 Kb GitHub Analytics Scoring use?
About 2.4k tokens (SKILL.md is roughly 9.5k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.
What are the alternatives to Kb GitHub Analytics Scoring?
Skills that share tags, products or a category with Kb GitHub Analytics Scoring: Repomix Browser Extension Developer (yamadashy/repomix, 29k stars), Docs Authoring (TracecatHQ/tracecat, 3.8k stars), README Badges and Headers (jal-co/shieldcn, 916 stars) and Valgo (cohesivestack/valgo, 508 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Kb GitHub Analytics Scoring?
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.