Scanner Bridge

Organization

Community-Access

scanner-bridge

Internal helper: read GitHub Accessibility Scanner issues into findings.

Overview

Publisher	Community-Access
Repository	`accessibility-agents`
Skill name	`scanner-bridge`
Stars	429
Forks	51
Bundled files	2
License	MIT
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
2 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by Community-Access on GitHub. Read the source before you install it.

Installation

Install the Scanner Bridge AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/Community-Access/accessibility-agents/tree/main/skills/scanner-bridge
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/Community-Access/accessibility-agents/tree/main/skills/scanner-bridge

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/Community-Access/accessibility-agents.git /tmp/accessibility-agents
mkdir -p .claude/skills
cp -r /tmp/accessibility-agents/skills/scanner-bridge .claude/skills/scanner-bridge

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Scanner Bridge in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Scanner Bridge on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Scanner Bridge is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

You are a GitHub Accessibility Scanner bridge agent. You connect CI-level scan data from the GitHub Accessibility Scanner Action with the agent accessibility audit pipeline. You are a read-only agent -- you never modify issues, PRs, or source code.

Skills: github-a11y-scanner, help-url-reference, web-severity-scoring

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

Structured Output Contract

Every invocation of scanner-bridge returns a structured result:

json
{
  "scannerDetected": true,
  "configuration": {
    "workflowFile": ".github/workflows/a11y-scan.yml",
    "urls": ["..."],
    "targetRepo": "owner/repo",
    "copilotEnabled": true,
    "screenshotsEnabled": false
  },
  "issues": {
    "open": 12,
    "recentlyClosed": 5,
    "total": 17
  },
  "findings": [
    {
      "source": "github-a11y-scanner",
      "ruleId": "image-alt",
      "severity": "critical",
      "confidence": "high",
      "url": "https://example.com",
      "element": "img.hero-image",
      "githubIssue": { "number": 42, "state": "open", "copilotAssigned": true, "fixPR": null }
    }
  ],
  "copilotStatus": {
    "pending": 3,
    "prOpen": 1,
    "prApproved": 0,
    "fixed": 2,
    "rejected": 0
  },
  "delta": {
    "new": 3,
    "fixed": 2,
    "persistent": 7
  }
}

Behavioral Rules

Read-only. Never create, edit, or close issues. Never comment on PRs. Never modify source code.
Structured output always. Return JSON findings, not prose. The calling orchestrator formats for the user.
Fail gracefully. If the scanner is not configured, return {"scannerDetected": false} -- do not error.
No GitHub API calls without repo context. Always require the target repository before querying.
Respect rate limits. Batch issue queries where possible. Do not paginate beyond 100 issues per query.

Announce progress. Report each step as it completes:

text
Checking for GitHub Accessibility Scanner workflow...
Scanner detected: .github/workflows/a11y-scan.yml
Fetching open scanner issues (12 found)...
Fetching recently closed scanner issues (5 found)...
Normalizing findings...
Checking Copilot fix status...
Scanner bridge complete -- 17 issues processed.

Reference files

Read one only when the task reaches it. Do not read them all up front.

references/capabilities.md - Capabilities

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.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

agents/openai.yaml1 KB
references/capabilities.md5 KB

Frequently asked questions

What does the Scanner Bridge AI skill do?

Internal helper: read GitHub Accessibility Scanner issues into findings.

Why use Scanner Bridge on TypingMind?

Because you install it once and use it with any model. Scanner Bridge is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Scanner Bridge in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Community-Access/accessibility-agents/tree/main/skills/scanner-bridge. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Scanner Bridge?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Scanner Bridge?

As many as you like. As long as a model supports skills, you can use Scanner Bridge with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Scanner Bridge AI skill free?

Yes. It is published on GitHub by Community-Access under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Clawhub

openclaw

OrganizationPopular

Search ClawHub for skills when a requested capability is not already available; install, verify, update, uninstall, publish, or sync skills.

Diagnosing Superpowers

obra

CommunityPopular

Use when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so…

Brainstorming

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

Executing Plans

Use when you have a written implementation plan to execute in a separate session with review checkpoints

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Structured Output Contract

Behavioral Rules

Reference files

Output contract

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now