Web Quality Audit
addyosmani/web-quality-skills
Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing.
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents.
Install Kb Lighthouse Scanner
$ npx skills add Community-Access/accessibility-agents --skill kb-lighthouse-scanner -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install Community-Access/accessibility-agents kb-lighthouse-scanner --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-lighthouse-scanner .claude/skills/kb-lighthouse-scanner && 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-lighthouse-scanner" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-lighthouse-scanner into .claude/skills/kb-lighthouse-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-lighthouse-scanner", 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-lighthouse-scannerType 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-lighthouse-scanner -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install Community-Access/accessibility-agents kb-lighthouse-scanner --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-lighthouse-scanner .agents/skills/kb-lighthouse-scanner && 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-lighthouse-scanner" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-lighthouse-scanner into .agents/skills/kb-lighthouse-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-lighthouse-scanner", 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-lighthouse-scanner -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install Community-Access/accessibility-agents kb-lighthouse-scanner --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-lighthouse-scanner .cursor/skills/kb-lighthouse-scanner && 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-lighthouse-scanner" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-lighthouse-scanner into .cursor/skills/kb-lighthouse-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-lighthouse-scanner", 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-lighthouse-scanner--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-lighthouse-scanner -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install Community-Access/accessibility-agents kb-lighthouse-scanner --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-lighthouse-scanner .gemini/skills/kb-lighthouse-scanner && 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-lighthouse-scanner" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-lighthouse-scanner into .gemini/skills/kb-lighthouse-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-lighthouse-scanner", 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-lighthouse-scannerInstalls 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-lighthouse-scanner -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-lighthouse-scanner .github/skills/kb-lighthouse-scanner && 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-lighthouse-scanner" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-lighthouse-scanner into .github/skills/kb-lighthouse-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-lighthouse-scanner", 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-lighthouse-scanner -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-lighthouse-scanner --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-lighthouse-scanner .opencode/skills/kb-lighthouse-scanner && 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-lighthouse-scanner" agent skill from https://github.com/Community-Access/accessibility-agents/tree/main/skills/kb-lighthouse-scanner into .opencode/skills/kb-lighthouse-scanner/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "kb-lighthouse-scanner", 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-lighthouse-scanner- GitHub stars
- 422
- Token cost
- ~2.1k tokens
- SKILL.md length
- 687 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.
- Works in 3 steps: Match by audit/rule ID: Lighthouse audit… → Match by URL: Compare scanned URLs from… → Boost confidence: Findings confirmed by…
- Tasks that involve Web performance
- SKILL.md covers Lighthouse CI Accessibility…, What Is Lighthouse CI?, Detecting Lighthouse CI Presence and Parsing Lighthouse…, plus 4 more sections
- Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md
What it does
Kb Lighthouse Scanner is an agent skill from Community-Access/accessibility-agents. Reference data, not a reviewer. Integrate Lighthouse CI accessibility audits. Detects configuration, parses results, maps findings to severity model, and tracks score regressions.
Its SKILL.md is about 2.1k 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 Frontend & Design, covering Web performance and Accessibility. 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 Web performance
- Tasks that involve Accessibility
Example prompts
- “/kb-lighthouse-scanner”
Workflow steps
3 steps, taken from the first numbered list in SKILL.md.
- Match by audit/rule ID: Lighthouse audit IDs correspond directly to axe-core rule IDs
- Match by URL: Compare scanned URLs from Lighthouse config with local scan targets
- Boost confidence: Findings confirmed by both Lighthouse CI and local axe-core scan receive high confidence
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 json, bash and yaml).
From the folder's file list and the shell code blocks in SKILL.md.
Network
Links to these hosts (documentation or services it may open):
github.com
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 Lighthouse Scanner loads about 2.1k tokens when it runs. Until then it costs about 50 tokens; SKILL.md has 687 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). 687 words, ~2,086 tokens.
Download SKILL.mdSave it as
.claude/skills/kb-lighthouse-scanner/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.- name
- kb-lighthouse-scanner
- description
- Reference data, not a reviewer. Integrate Lighthouse CI accessibility audits. Detects configuration, parses results, maps findings to severity model, and tracks score regressions.
- license
- MIT
- disable-model-invocation
- true
- user-invocable
- false
- metadata.tier
- reference
- metadata.domain
- cross-cutting
- metadata.output
- none
- metadata.effort
- low
- metadata.title
- Lighthouse Scanner
Lighthouse CI Accessibility Integration
What Is Lighthouse CI?
Lighthouse CI is a suite of tools for running Google Lighthouse audits in CI pipelines. The most common GitHub Actions integration uses treosh/lighthouse-ci-action.
Lighthouse provides:
- Performance, accessibility, best practices, and SEO scoring (0-100)
- Individual audit results with pass/fail status and detailed findings
- Score budgets and assertions to fail builds on regressions
- HTML and JSON report artifacts
- Score comparison across runs for trend tracking
Accessibility focus: The Lighthouse accessibility category runs a subset of axe-core rules and reports a weighted score from 0-100 along with individual audit violations.
Detecting Lighthouse CI Presence
Workflow File Detection
Search for workflow files referencing Lighthouse CI:
# Search for the treosh Lighthouse CI action
grep -rl "treosh/lighthouse-ci-action" .github/workflows/
# Search for official Lighthouse CI CLI usage
grep -rl "lhci autorun\|lighthouse-ci" .github/workflows/Patterns to match in YAML:
- uses: treosh/lighthouse-ci-action@v12Configuration File Detection
Lighthouse CI uses configuration files in the repository root:
# Check for Lighthouse CI config files
ls lighthouserc.js lighthouserc.json .lighthouserc.js .lighthouserc.json .lighthouserc.yml 2>/dev/null| Config File | Format |
|---|---|
lighthouserc.js | JavaScript module |
lighthouserc.json | JSON |
.lighthouserc.js | JavaScript module (dotfile) |
.lighthouserc.json | JSON (dotfile) |
.lighthouserc.yml | YAML (dotfile) |
Configuration Structure
Key fields in Lighthouse CI config:
{
"ci": {
"collect": {
"url": ["https://example.com", "https://example.com/about"],
"numberOfRuns": 3
},
"assert": {
"assertions": {
"categories:accessibility": ["error", {"minScore": 0.9}]
}
},
"upload": {
"target": "temporary-public-storage"
}
}
}| Section | Purpose | Agent Use |
|---|---|---|
ci.collect.url | URLs to audit | Scope of CI scanning |
ci.collect.numberOfRuns | How many times to run each URL | Reliability indicator |
ci.assert.assertions | Score budgets and thresholds | Regression detection |
ci.upload.target | Where to store reports | Report retrieval |
Parsing Lighthouse Accessibility Results
Accessibility Score
Lighthouse computes a weighted accessibility score from 0-100 based on individual audit results.
| Score Range | Grade | Interpretation |
|---|---|---|
| 90-100 | A | Good accessibility |
| 70-89 | B-C | Some issues to address |
| 50-69 | D | Significant issues |
| 0-49 | F | Critical accessibility failures |
Individual Audit Results
Each Lighthouse accessibility audit corresponds to an axe-core rule:
| Audit ID | axe-core Rule | WCAG Criterion | Weight |
|---|---|---|---|
image-alt | image-alt | 1.1.1 | 10 |
color-contrast | color-contrast | 1.4.3 | 7 |
label | label | 1.3.1 | 7 |
button-name | button-name | 4.1.2 | 7 |
link-name | link-name | 2.4.4 | 7 |
html-has-lang | html-has-lang | 3.1.1 | 7 |
document-title | document-title | 2.4.2 | 7 |
heading-order | heading-order | 1.3.1 | 3 |
meta-viewport | meta-viewport | 1.4.4 | 10 |
bypass | bypass | 2.4.1 | 7 |
tabindex | tabindex | 2.4.3 | 7 |
aria-allowed-attr | aria-allowed-attr | 4.1.2 | 10 |
aria-hidden-body | aria-hidden-body | 4.1.2 | 10 |
aria-required-attr | aria-required-attr | 4.1.2 | 10 |
aria-roles | aria-roles | 4.1.2 | 7 |
aria-valid-attr-value | aria-valid-attr-value | 4.1.2 | 7 |
aria-valid-attr | aria-valid-attr | 4.1.2 | 10 |
Severity Mapping
Lighthouse uses weights rather than impact levels. Map to the agent severity model based on weight and audit pass/fail:
| Lighthouse Weight | Audit Status | Agent Severity |
|---|---|---|
| 10 | Fail | Critical |
| 7 | Fail | Serious |
| 3 | Fail | Moderate |
| 1 | Fail | Minor |
| Any | Pass | N/A (not reported) |
Correlation with Local Scans
Lighthouse-to-axe-core Mapping
Since Lighthouse uses axe-core under the hood, correlation is straightforward:
- Match by audit/rule ID: Lighthouse audit IDs correspond directly to axe-core rule IDs
- Match by URL: Compare scanned URLs from Lighthouse config with local scan targets
- Boost confidence: Findings confirmed by both Lighthouse CI and local axe-core scan receive
highconfidence
Show full SKILL.md (266 more words)Show less
Source Comparison
Each scenario, with its interpretation and action.
| Scenario | Interpretation | Action |
|---|---|---|
| Found by Lighthouse AND local scan | High confidence | Report as high confidence, full severity weight |
| Found by Lighthouse only | Environment-specific | Report as medium confidence, note "CI-only finding" |
| Found by local scan only | Not covered by Lighthouse subset | Report as medium confidence, note "local-only finding" |
| Lighthouse score regressed | New accessibility issues introduced | Flag as regression, prioritize in report |
Score Regression Detection
Track Lighthouse accessibility scores across runs to detect regressions:
Comparing Scores
{
"url": "https://example.com",
"previousScore": 95,
"currentScore": 87,
"delta": -8,
"status": "regressed",
"newFailures": ["color-contrast", "image-alt"],
"newPasses": []
}Regression Thresholds
Each delta, with its severity and action.
| Delta | Severity | Action |
|---|---|---|
| Score drops 10+ points | Critical | Immediate attention, likely multiple new violations |
| Score drops 5-9 points | Serious | New violations introduced, review before merge |
| Score drops 1-4 points | Moderate | Minor regression, track for follow-up |
| Score unchanged or improved | N/A | No regression detected |
Structured Output Format
When lighthouse-bridge normalizes Lighthouse data, it produces findings in this format:
{
"source": "lighthouse-ci",
"ruleId": "color-contrast",
"wcagCriterion": "1.4.3",
"wcagLevel": "AA",
"severity": "serious",
"confidence": "high",
"url": "https://example.com/login",
"element": "button.submit-btn",
"description": "Element has insufficient color contrast ratio",
"lighthouseWeight": 7,
"lighthouseScore": {
"overall": 87,
"previousOverall": 95,
"delta": -8,
"status": "regressed"
}
}GitHub Actions Integration
treosh/lighthouse-ci-action
The most common Lighthouse CI GitHub Action:
- name: Run Lighthouse CI
uses: treosh/lighthouse-ci-action@v12
with:
urls: |
https://example.com
https://example.com/about
uploadArtifacts: true
configPath: ./lighthouserc.jsonAction Inputs
Each input, with its required and description.
| Input | Required | Description |
|---|---|---|
urls | Yes (or in config) | Newline-separated URLs to audit |
configPath | No | Path to Lighthouse CI config file |
uploadArtifacts | No | Upload HTML reports as workflow artifacts |
temporaryPublicStorage | No | Upload to temporary public storage for sharing |
runs | No | Number of runs per URL (default: 1) |
budgetPath | No | Path to a Lighthouse budget JSON file |
Extracting Results from Artifacts
Lighthouse CI uploads results as workflow artifacts. To retrieve scores:
- Download the artifact from the workflow run
- Parse the JSON report files
- Extract
categories.accessibility.scorefor the overall score - Extract individual
audits.{audit-id}results for violations
© 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-lighthouse-scanner of Community-Access/accessibility-agents.
- SKILL.md
- agents/openai.yaml
Open the folder on GitHubat commit decf6ba
Compare with similar skills
Kb Lighthouse Scanner 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 Lighthouse Scanner this skillCommunity-Access/accessibility-agents | 422 | — | ~2.1k | Automated safety check: Pass | MIT | |
| Web Quality Auditaddyosmani/web-quality-skills | 2.9k | — | ~2.6k | Automated safety check: Pass | MIT | |
| Web Quality Auditmidudev/100cosas.dev | 114 | 3 repos | ~1.7k | Automated safety check: Pass | MIT | |
| Optimize Loadtextura-agency/next16-claude-starter | 132 | — | ~4.6k | Automated safety check: Notes | Unlicense | |
| Accessibilityericrisco/rsc-harness | 167 | — | ~3.4k | Automated safety check: Pass | MIT | |
| Accessibility Checkmakifbaysal/tasktrooper | 109 | — | ~1.1k | Automated safety check: Pass | Apache-2.0 |
Similar skills
Web Quality Audit
midudev/100cosas.dev
Comprehensive web quality audit covering performance, accessibility, SEO, and best practices.
Optimize Load
textura-agency/next16-claude-starter
Get a page into Lighthouse's green zone on desktop and mobile, for people AND for the robot form crawlers get — build it, audit all four categories (Performance, Accessibility, Best Practices, SEO)…
Accessibility
ericrisco/rsc-harness
A skill your agent uses when making a web UI conform to WCAG 2.2 Level AA — axe-core or Lighthouse a11y violations, keyboard operability, focus management, ARIA roles/names/live regions, contrast…
Accessibility Check
makifbaysal/tasktrooper
A skill your agent uses when a task changes any screen, form, dialog, menu or control - Lighthouse/axe scan of the changed screens, a keyboard walk, and the thresholds that fail a task
Web Perf
elithrar/dotfiles
Diagnose page-load and interaction performance using browser traces, network evidence, and source code.
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
Categories
Questions about Kb Lighthouse Scanner
What does Kb Lighthouse Scanner do?
Reference data, not a reviewer. An agent skill from Community-Access/accessibility-agents. Kb Lighthouse Scanner is an agent skill from Community-Access/accessibility-agents. Reference data, not a reviewer.
When should I use Kb Lighthouse Scanner?
Kb Lighthouse Scanner fits situations like: tasks that involve Web performance; tasks that involve Accessibility.
How do I install Kb Lighthouse Scanner in Claude Code?
Run `npx skills add Community-Access/accessibility-agents --skill kb-lighthouse-scanner -a claude-code`. Or copy the skill folder (skills/kb-lighthouse-scanner in Community-Access/accessibility-agents) into .claude/skills/kb-lighthouse-scanner in your project. Claude Code loads it when a task matches its description.
How do I install Kb Lighthouse Scanner in Codex?
Run `npx skills add Community-Access/accessibility-agents --skill kb-lighthouse-scanner -a codex`. Or copy the skill folder (skills/kb-lighthouse-scanner in Community-Access/accessibility-agents) into .agents/skills/kb-lighthouse-scanner in your project. Codex loads it when a task matches its description.
Can I use Kb Lighthouse Scanner 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-lighthouse-scanner -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-lighthouse-scanner, .gemini/skills/kb-lighthouse-scanner, .github/skills/kb-lighthouse-scanner and .opencode/skills/kb-lighthouse-scanner in your project.
What does Kb Lighthouse Scanner need to run?
SKILL.md names no scripts, command-line tools or credentials: Kb Lighthouse Scanner is instructions for the agent only.
Does Kb Lighthouse Scanner access the network?
SKILL.md names 1 domain. As links in the text: github.com. This is read from the text; nothing was executed.
Is Kb Lighthouse Scanner 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 Lighthouse Scanner use?
Kb Lighthouse Scanner 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 Lighthouse Scanner use?
About 2.1k tokens (SKILL.md is roughly 8.3k 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 Lighthouse Scanner?
Skills that share tags, products or a category with Kb Lighthouse Scanner: Web Quality Audit (addyosmani/web-quality-skills, 2.9k stars), Web Quality Audit (midudev/100cosas.dev, 114 stars), Optimize Load (textura-agency/next16-claude-starter, 132 stars) and Accessibility (ericrisco/rsc-harness, 167 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.
Who maintains Kb Lighthouse Scanner?
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.