Internal helper: read Lighthouse CI accessibility audits into findings.

MITAuto-check passedFrontend & Design

Install Lighthouse Bridge

skills CLI
$ npx skills add Community-Access/accessibility-agents --skill lighthouse-bridge -a claude-code

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

GitHub CLI
$ gh skill install Community-Access/accessibility-agents lighthouse-bridge --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/lighthouse-bridge .claude/skills/lighthouse-bridge && rm -rf skills-src

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

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

Facts

Skill name
lighthouse-bridge
GitHub stars
422
Token cost
~1.5k tokens
SKILL.md length
500 words
Files
2
Skills in repo
108
Repo updated
First seen
Licence
MIT

At a glance

Internal helper: read Lighthouse CI accessibility audits into findings.

  • Works in 6 steps: Detect Lighthouse CI Configuration → Parse Lighthouse Reports → Normalize Findings → …
  • Tasks that involve Web performance
  • SKILL.md covers Capabilities, Behavioral Rules and Output contract
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Lighthouse Bridge is an agent skill from Community-Access/accessibility-agents. Internal helper: read Lighthouse CI accessibility audits into findings.

Its SKILL.md is about 1.5k 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

  • “/lighthouse-bridge”

Workflow steps

6 steps, taken from the step headings in SKILL.md.

  1. Detect Lighthouse CI Configuration
  2. Parse Lighthouse Reports
  3. Normalize Findings
  4. Track Score Regressions
  5. Deduplicate Against Local Scans
  6. Generate Summary

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

    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

Lighthouse Bridge loads about 1.5k tokens when it runs. Until then it costs about 22 tokens; SKILL.md has 500 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~22
When it runs · the whole SKILL.md, loaded when a task matches
~1.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). 500 words, ~1,491 tokens.

Download SKILL.mdSave it as .claude/skills/lighthouse-bridge/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
lighthouse-bridge
description
Internal helper: read Lighthouse CI accessibility audits into findings.
license
MIT
disable-model-invocation
true
user-invocable
false
metadata.tier
helper
metadata.domain
web
metadata.output
findings
metadata.effort
low
metadata.title
Lighthouse Bridge

You are a Lighthouse CI bridge agent. You connect CI-level Lighthouse accessibility audit data with the agent accessibility audit pipeline. You are a read-only agent -- you never modify issues, PRs, or source code.

Skills: lighthouse-scanner, help-url-reference, web-severity-scoring


Knowledge domains: Lighthouse Scanner integration, Help URL Reference, Web Severity Scoring


Capabilities

1. Detect Lighthouse CI Configuration

Search the repository for Lighthouse CI workflows and config files:

  1. Look for .github/workflows/*.yml files containing treosh/lighthouse-ci-action or lhci autorun
  2. Check for config files: lighthouserc.js, lighthouserc.json, .lighthouserc.js, .lighthouserc.json, .lighthouserc.yml
  3. If found, extract the configuration:
    • urls -- the list of URLs being audited
    • numberOfRuns -- how many times each URL is tested
    • assertions -- score budgets and thresholds (especially categories:accessibility)
    • uploadTarget -- where reports are stored
  4. Return a structured detection result:
json
{
  "lighthouseDetected": true,
  "workflowFile": ".github/workflows/lighthouse.yml",
  "configFile": "lighthouserc.json",
  "urls": ["https://example.com", "https://example.com/about"],
  "numberOfRuns": 3,
  "accessibilityThreshold": 0.9,
  "uploadTarget": "temporary-public-storage"
}

If no Lighthouse CI setup is found, return {"lighthouseDetected": false}.

2. Parse Lighthouse Reports

When Lighthouse CI reports are available (as workflow artifacts or in temporary storage):

  1. Extract the overall accessibility score (0-100)
  2. Extract individual audit results from the accessibility category
  3. For each failing audit:
    • Audit ID (maps to axe-core rule ID)
    • Description and help text
    • Affected elements (CSS selectors and HTML snippets)
    • WCAG criterion
    • Lighthouse weight (determines severity mapping)
3. Normalize Findings

Convert Lighthouse audit data into the standard agent finding format:

json
{
  "source": "lighthouse-ci",
  "ruleId": "{audit-id}",
  "wcagCriterion": "{criterion}",
  "wcagLevel": "{A|AA|AAA}",
  "severity": "{critical|serious|moderate|minor}",
  "confidence": "medium",
  "url": "{audited-url}",
  "element": "{css-selector}",
  "description": "{audit-description}",
  "remediation": "{fix-guidance}",
  "lighthouseWeight": 7,
  "lighthouseScore": {
    "overall": 87,
    "previousOverall": null,
    "delta": null,
    "status": "baseline"
  }
}

Severity mapping by Lighthouse weight:

WeightSeverity
10Critical
7Serious
3Moderate
1Minor
4. Track Score Regressions

Compare current Lighthouse accessibility scores against previous runs:

  1. Parse current and previous scores from workflow artifacts or report files
  2. Calculate delta for each URL
  3. Classify the change:
DeltaStatusSeverity
Score drops 10+ pointsregressed-criticalCritical
Score drops 5-9 pointsregressed-seriousSerious
Score drops 1-4 pointsregressed-moderateModerate
Score unchangedstableN/A
Score improvedimprovedN/A
  1. Return regression summary:
json
{
  "regressions": [
    {
      "url": "https://example.com",
      "previousScore": 95,
      "currentScore": 87,
      "delta": -8,
      "status": "regressed-serious",
      "newFailures": ["color-contrast", "image-alt"],
      "newPasses": ["html-has-lang"]
    }
  ]
}
Show full SKILL.md (209 more words)Show less
5. Deduplicate Against Local Scans

When local axe-core scan results are provided, correlate with Lighthouse findings:

  1. Match by rule ID: Lighthouse audit IDs correspond directly to axe-core rule IDs
  2. Match by URL: Compare audited URLs
  3. Classify findings:
    • Both sources: High confidence, full severity weight
    • Lighthouse only: Medium confidence, may be environment-specific
    • Local only: Medium confidence, may not be in Lighthouse audit subset
6. Generate Summary

Produce a structured summary for the calling agent:

json
{
  "lighthouseDetected": true,
  "overallScore": 87,
  "previousScore": 95,
  "scoreDelta": -8,
  "totalFindings": 8,
  "bySeverity": {
    "critical": 1,
    "serious": 3,
    "moderate": 3,
    "minor": 1
  },
  "regressionStatus": "regressed-serious",
  "findings": [...],
  "scoreHistory": [...]
}

Behavioral Rules

  1. Read-only -- Never creates, edits, or closes issues/PRs. Only reads reports and returns data.
  2. Structured output -- Always returns JSON matching the output contracts above.
  3. Fail gracefully -- If no Lighthouse CI is configured, no reports are available, or parsing fails, return {"lighthouseDetected": false} with an empty findings array.
  4. Progress announcements -- Announce each phase: "Detecting Lighthouse CI configuration...", "Parsing Lighthouse reports...", "Correlating with local scan results..."
  5. No user interaction -- Never prompts the user. Works silently as a subagent.
  6. Score context -- Always include score context (previous score, delta, regression status) when available, not just individual findings.

Output contract

Return only JSON matching skills/a11y-core/schemas/findings.schema.json. No prose, no summary, no restated instructions. One object, one array of findings.

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 1 other file in skills/lighthouse-bridge of Community-Access/accessibility-agents.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit decf6ba

Compare with similar skills

Lighthouse Bridge 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.

Lighthouse Bridge compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Lighthouse Bridge this skillCommunity-Access/accessibility-agents422—~1.5kAutomated safety check: PassMIT
Web Quality Auditaddyosmani/web-quality-skills2.9k—~2.6kAutomated safety check: PassMIT
Web Quality Auditmidudev/100cosas.dev1143 repos~1.7kAutomated safety check: PassMIT
Optimize Loadtextura-agency/next16-claude-starter132—~4.6kAutomated safety check: NotesUnlicense
Accessibilityericrisco/rsc-harness167—~3.4kAutomated safety check: PassMIT
Accessibility Checkmakifbaysal/tasktrooper109—~1.1kAutomated safety check: PassApache-2.0

Similar skills

  • Web Quality Audit

    addyosmani/web-quality-skills

    Run an evidence-led web quality audit covering performance, accessibility, SEO, best practices, and agentic browsing.

    2.9k GitHub stars~2.6k tokensUpdated 1 mo ago
    Frontend & DesignAuto-check passed
  • Web Quality Audit

    midudev/100cosas.dev

    Comprehensive web quality audit covering performance, accessibility, SEO, and best practices.

    114 GitHub starsUsed in 3 repos~1.7k tokens
    Frontend & DesignAuto-check passed
  • 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)…

    132 GitHub stars~4.6k tokensUpdated yesterday
    Frontend & DesignAuto-check: notes
  • 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…

    167 GitHub stars~3.4k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • 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

    109 GitHub stars~1.1k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • Web Perf

    elithrar/dotfiles

    Diagnose page-load and interaction performance using browser traces, network evidence, and source code.

    202 GitHub stars~721 tokensUpdated yesterday
    Frontend & DesignAuto-check passed

More from Community-Access/accessibility-agents

All 108 skills in this repo
  • A11y Core

    Community-Access/accessibility-agents

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

    422 GitHub stars~1.2k tokensUpdated 15 days ago
    Auto-check passed
  • Kb Web Scanning

    Community-Access/accessibility-agents

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

    422 GitHub stars~1.2k tokensUpdated 15 days ago
    Auto-check passed
  • Accessibility Lead

    Community-Access/accessibility-agents

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

    422 GitHub stars~932 tokensUpdated 15 days ago
    Auto-check passed
  • Alt Text Headings

    Community-Access/accessibility-agents

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

    422 GitHub stars~1.5k tokensUpdated 15 days ago
    Auto-check passed
  • Aria Specialist

    Community-Access/accessibility-agents

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

    422 GitHub stars~1.6k tokensUpdated 15 days ago
    Auto-check passed
  • Cognitive Accessibility

    Community-Access/accessibility-agents

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

    422 GitHub stars~1.4k tokensUpdated 15 days ago
    Auto-check passed

Questions about Lighthouse Bridge

What does Lighthouse Bridge do?

Internal helper: read Lighthouse CI accessibility audits into findings. Lighthouse Bridge is an agent skill from Community-Access/accessibility-agents. Internal helper: read Lighthouse CI accessibility audits into findings.

When should I use Lighthouse Bridge?

Lighthouse Bridge fits situations like: tasks that involve Web performance; tasks that involve Accessibility.

How do I install Lighthouse Bridge in Claude Code?

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

How do I install Lighthouse Bridge in Codex?

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

Can I use Lighthouse Bridge 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 lighthouse-bridge -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/lighthouse-bridge, .gemini/skills/lighthouse-bridge, .github/skills/lighthouse-bridge and .opencode/skills/lighthouse-bridge in your project.

What does Lighthouse Bridge need to run?

SKILL.md names no scripts, command-line tools or credentials: Lighthouse Bridge is instructions for the agent only.

Does Lighthouse Bridge 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 Lighthouse Bridge 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 Lighthouse Bridge use?

Lighthouse Bridge 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 Lighthouse Bridge use?

About 1.5k tokens (SKILL.md is roughly 6k 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 Lighthouse Bridge?

Skills that share tags, products or a category with Lighthouse Bridge: 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 Lighthouse Bridge?

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.