Lighthouse Bridge
Internal helper: read Lighthouse CI accessibility audits into findings.
Install
/plugin marketplace add Community-Access/accessibility-agentsThe repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.
npx skills add Community-Access/accessibility-agents --skill lighthouse-bridgegit clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p ~/.claude/skills
cp -r /tmp/accessibility-agents/skills/lighthouse-bridge ~/.claude/skills/lighthouse-bridgePersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
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:** `kb-lighthouse-scanner`, `kb-help-url-reference`, `kb-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}`.Details
- Skill name
lighthouse-bridge- Repository
- Community-Access/accessibility-agents
- Path
skills/lighthouse-bridge/SKILL.md- License
- MIT
- Repo updated
- 16 November 2026
FAQ
What does the Lighthouse Bridge skill do?
Internal helper: read Lighthouse CI accessibility audits into findings.
How do I install the Lighthouse Bridge skill?
Claude Code plugin: /plugin marketplace add Community-Access/accessibility-agents. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Lighthouse Bridge popular?
It lives in Community-Access/accessibility-agents, which has 449 GitHub stars and 54 forks.
Related skills
A11y Core
449Community-Access/accessibility-agents
Shared contract for the Accessibility Agents skills - dispatch, findings schema, report rules. Read by skills, never dispatched on its own.
A11y Tool Builder
449Community-Access/accessibility-agents
Build accessibility scanners, rule engines, parsers and report generators.
Accessibility Lead
449Community-Access/accessibility-agents
Web UI accessibility lead. Use before writing or changing HTML, JSX, TSX, Vue, Svelte, CSS or templates. Picks specialists and merges their findings.
Media Accessibility
449Community-Access/accessibility-agents
Captions, transcripts, audio description and accessible media players.
Kb Web Severity Scoring
449Community-Access/accessibility-agents
Reference data, not a reviewer. Compute web accessibility scores (0-100, A-F grades) with severity scoring, confidence levels, and remediation tracking across audits.
Mobile Accessibility
449Community-Access/accessibility-agents
React Native, Expo, iOS and Android: labels, roles and touch targets.
Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.