Cli Audit logo

Cli Audit

Community
mgifford
cli-audit

Audit live URLs using Playwright and Axe combined with WCAG skills

Overview

Publishermgifford
Repositoryaccessibility-skills
Skill namecli-audit
Stars
57
Forks
5
Bundled files
1
LicenseAGPL-3.0
Links
  • 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.

  • 1 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by mgifford on GitHub. Read the source before you install it.

Installation

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

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/mgifford/accessibility-skills/tree/main/skills/cli-audit
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

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/mgifford/accessibility-skills.git /tmp/accessibility-skills
mkdir -p .claude/skills
cp -r /tmp/accessibility-skills/skills/cli-audit .claude/skills/cli-audit
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Cli Audit 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 Cli Audit 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 Cli Audit 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.

CLI Audit Skill

Use this skill when asked to audit a live URL from Claude CLI.

Respect robots directives and site terms of service for every live-site audit request.

Required Execution

When the user asks to audit a page URL, run:

bash
npx --yes --package=github:mgifford/accessibility-skills cli-audit-inspect <URL>

This invocation is portable for Claude CLI users because it pulls the inspection command from this repository package instead of requiring a local scripts/ file in the target project.

Be Polite With Live Sites

When auditing live URLs, keep behavior respectful and low impact:

  • Prefer single-page or small-batch checks first.
  • Avoid rapid repeated scans against production pages.
  • If Cloudflare/WAF blocks requests, do not brute-force retries.
  • Recommend owner-approved alternatives: staging URLs, allowlisting, or manual checks.

Required Parsing

Parse the emitted JSON and evaluate:

  1. axe.violations for automated WCAG and best-practice failures.
  2. axe.incomplete for potential violations that need manual confirmation.
  3. accessibilityTree for behavioral issues that automated rules miss, including:
    • Missing or unclear names for interactive elements
    • Unexpected roles or role mismatches
    • Landmark and heading structure problems
    • State communication gaps (expanded, checked, selected, disabled state)
    • Dialog and menu semantics that can indicate focus-management risk

Required Evaluation Method

Map findings to this repository's guidance before reporting:

  • Start with skills/ACCESSIBILITY-general/SKILL.md.
  • Then apply relevant topic skills based on observed problems (for example: forms, keyboard, navigation, color-contrast, aria-live-regions, image-alt-text, tables, svg, touch-pointer, tooltips).

Reporting Requirements

For each issue reported:

  1. Identify source: axe or accessibilityTree.
  2. Include affected selector/path from axe nodes when available.
  3. Provide impact summary and severity using the relevant skill scale.
  4. Cite WCAG 2.2 success criteria when determinable, and cite the source of the mapping (the axe rule's documented mapping, or the specific skill rule) — do not invent a WCAG mapping this audit's evidence does not support.
  5. Provide a concrete remediation recommendation tied to a skill rule.
  6. Preserve the tool's raw outcome (axe.violations vs. axe.incomplete, or the accessibility-tree evidence) rather than collapsing it into a single pass/fail label.
  7. Report every axe.violations and accessibilityTree finding from this audit as evidence_status: automated-indicator with handling: review — this audit alone does not constitute the human confirmation needed for confirmed-standards-failure, confirmed-user-facing-barrier, or handling: report/suppress. See Accessibility Finding Tracking: Policy Classification.

If no issues are found, report residual risk clearly:

  • Automated scans can miss interaction, timing, focus-flow, and assistive-tech behavior issues.
  • Recommend manual keyboard and screen-reader validation using skills/manual-testing/SKILL.md.

Bundled files

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

Frequently asked questions

What does the Cli Audit AI skill do?

Audit live URLs using Playwright and Axe combined with WCAG skills

Why use Cli Audit on TypingMind?

Because you install it once and use it with any model. Cli Audit 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 Cli Audit in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/mgifford/accessibility-skills/tree/main/skills/cli-audit. 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 Cli Audit?

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 Cli Audit?

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

Is the Cli Audit AI skill free?

Yes. It is published on GitHub by mgifford under the AGPL-3.0 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇