Skip to content
TrustedSkillsbeta
Back to all skills

A11Y Checker Ci

Checked
hopeoverture·vlatest·frontend

A11Y Checker Ci automatically audits your frontend code for accessibility issues during CI/CD, ensuring inclusive web experiences.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add hopeoverture/worldbuilding-app-skills --skill a11y-checker-ci -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

hopeoverture

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill passed all 6 checks. We read its files at one commit and looked for the things that make a skill dangerous to run — not for whether it works.

  • Declares what it does: passed

    SKILL.md parses and declares a name and a description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned hopeoverture/worldbuilding-app-skills at 1263b3fb00.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
1263b3fb00
Manifest
skills/testing/a11y-checker-ci/SKILL.md
Scanned
10 files, 2,150 lines
Copies in repo
2 — all of them scanned
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

The a11y-checker-ci skill integrates accessibility checks into your continuous integration (CI) pipeline. It analyzes frontend code for common accessibility issues, providing feedback to developers and ensuring a more inclusive user experience. This helps identify and fix problems early in the development process, preventing regressions and maintaining accessibility standards.

When to use it

  • Automated Accessibility Testing: Integrate into your CI/CD workflow to automatically check new commits for accessibility violations.
  • Pre-Release Validation: Run checks before deploying a frontend application to production to catch any last-minute accessibility issues.
  • Code Review Enhancement: Use the skill's output as part of code review processes, guiding developers towards accessible coding practices.
  • Maintain Accessibility Standards: Ensure ongoing compliance with WCAG or other accessibility guidelines.

Key capabilities

  • Automated accessibility checks
  • Integration into CI pipelines
  • Frontend code analysis
  • Accessibility regression prevention

Example prompts

  • "Run an a11y check on the latest commit to the main branch."
  • "Analyze this pull request for accessibility issues and report any violations."
  • "Perform an accessibility audit of the frontend codebase before deployment."

Tips & gotchas

The skill requires a CI/CD environment (like GitHub Actions, GitLab CI, or Jenkins) configured to execute code analysis tasks. Ensure the necessary dependencies are installed in your CI environment for proper execution and reporting.