check-accessibility 100/100

Is check-accessibility safe to install?

SaferSkills independently audited check-accessibility (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.

CategoryWeightCategory scoreContribution

Securityprompt, exec, net, exfil, eval

35%

100

35.0 pts

Supply chainhash, typosquat, maintainer, lockfile

20%

100

20.0 pts

Maintenancestaleness, pinning, CI

15%

100

15.0 pts

TransparencySKILL.md, perms, README

15%

100

15.0 pts

Communityinstalls, verify, response

15%

100

15.0 pts

Findings & checks · 0 flagged

Securityscore 100 · 0 findings

✓—All security checks passedNo findings in this category for the latest scan.pass

Supply chainscore 100 · 0 findings

✓—All supply chain checks passedNo findings in this category for the latest scan.pass

Maintenancescore 100 · 0 findings

✓—All maintenance checks passedNo findings in this category for the latest scan.pass

Transparencyscore 100 · 0 findings

✓—All transparency checks passedNo findings in this category for the latest scan.pass

Communityscore 100 · 0 findings

✓—All community checks passedNo findings in this category for the latest scan.pass

The primary manifest — the file an agent reads to learn what this artifact does.

.claude/skills/check-accessibility/SKILL.md · 1 file

.claude/skills/check-accessibility/SKILL.md2.5 KB · Markdown

name: check-accessibility

description: Review component for accessibility issues

disable-model-invocation: true

allowed-tools: Read, Grep, Glob, WebSearch, WebFetch

Usage: /check-accessibility COMPONENT_NAME

Examples:

/check-accessibility button
/check-accessibility alert
/check-accessibility v2/lib/src/components/Button.ts

Check accessibility for: $ARGUMENTS

Setup:

Read .claude/PROJECT_CONTEXT.md for AgnosticUI structure and accessibility principles

Process:

Search for latest standards:

Use WebSearch for "WCAG 2.2 [component-type] accessibility"
Use WebSearch for "ARIA [specific-pattern] best practices"
Fetch W3C WAI-ARIA documentation if needed for specific patterns

Locate component files:

Core component: v2/lib/src/components/$ARGUMENTS*
Framework implementations if relevant: v2/playgrounds/*/src/stories/*$ARGUMENTS*
Check PROJECT_CONTEXT for AgnosticUI's accessibility standards location

Analyze against current standards:

Semantic HTML: Proper element usage for meaning and structure
ARIA attributes: Correct, necessary, and following latest specs
Keyboard navigation: Tab order, focus management, keyboard shortcuts
Focus indicators: Visible focus styles meeting contrast requirements
Screen reader support: Meaningful labels, descriptions, live regions
Color contrast: WCAG 2.2 AA requirements (4.5:1 text, 3:1 UI)
Touch targets: Minimum 44x44px for interactive elements
Motion/animation: Respects prefers-reduced-motion

Framework-specific considerations:

Check if accessibility differs across Lit, React, Vue implementations
Verify ARIA is applied correctly in each framework's rendering
Test that events work with keyboard in all frameworks

Report findings:

List issues with severity (Critical/High/Medium/Low)
Reference specific WCAG 2.2 success criteria
Provide remediation steps with code examples
Link to current W3C/MDN documentation
Note AgnosticUI-specific patterns to follow

If fixes requested:

Propose changes that work across all frameworks
Ensure fixes align with AgnosticUI's CSS-first approach
WAIT FOR USER APPROVAL before implementing

AgnosticUI Accessibility Requirements:

WCAG 2.1 AA compliance minimum
Framework-agnostic solutions preferred
CSS custom properties for focus indicators
Consistent behavior across Lit, React, Vue

check-accessibility— agent skill

Is check-accessibility safe to install?

Audit the pieces. Scan the whole. Decide.