AgentStack
SKILL verified MIT Self-run

Evaluate

skill-bromso-metapowers-evaluate · by bromso

Run accessibility checks and discover issues mapped to WCAG criteria

No reviews yet
0 installs
1 views
0.0% view→install

Install

$ agentstack add skill-bromso-metapowers-evaluate

✓ scanned · ✓ verified — works with Claude Code, Cursor, and more.

Security review

✓ Passed

No issues found. Passed automated security review. · v0.1.0 How review works →

  • Prompt-injection patterns
  • Secret / credential exfiltration
  • Dangerous shell & filesystem operations
  • Untrusted network calls
  • Known-malicious package signatures

What it can access

  • Network access No
  • Filesystem access No
  • Shell / process execution No
  • Environment & secrets No
  • Dynamic code execution No

From automated source analysis of v0.1.0. “Used” means the capability is present in the source — more access means more to trust, not that it’s unsafe.

Are you the author of Evaluate? Claim this listing to set pricing, connect Stripe payouts, and keep 70% of every sale.
Sign up to claim

About

Evaluate

Evaluate "$ARGUMENTS" for accessibility issues. Run automated and manual checks, discover barriers, and map each issue to specific WCAG success criteria.

Prerequisites

Read .metapowers/accessibility/$ARGUMENTS/01-scope.md. If this file does not exist, tell the user:

> Phase 1 (Scope) has not been completed for "$ARGUMENTS". Run /accessibility:scope $ARGUMENTS first, or use --skip-checks to bypass.

If --skip-checks is present in $ARGUMENTS, skip this check and log to .metapowers/accessibility/$ARGUMENTS/skip-log.md.

Process

  1. Read context files:
  • Read .metapowers/accessibility/$ARGUMENTS/01-scope.md for audit scope and target pages
  • Read plugins/accessibility/shared/wcag-21-aa-criteria.md for the full criteria reference
  1. Automated evaluation:
  • Read the source code of the target pages/components
  • Check for: missing alt text, missing form labels, heading hierarchy violations, missing ARIA attributes, color contrast issues, missing lang attribute, keyboard trap risks
  1. Manual evaluation:
  • Trace keyboard navigation flow — can all interactive elements be reached and operated?
  • Check focus visibility — is focus indicator visible on every interactive element?
  • Check reading order — does DOM order match visual order?
  • Check form error handling — are errors identified and described in text?
  • Check dynamic content — are updates announced via ARIA live regions?
  1. Map each issue to WCAG criteria:
  • For each issue found, identify the specific WCAG success criterion violated
  • Classify severity: Critical (blocks access), Major (significant barrier), Minor (inconvenience)
  • Note the location (file, line, component)
  1. Write the artifact to .metapowers/accessibility/$ARGUMENTS/02-evaluate.md with sections:
  • Issues Found — each issue with WCAG mapping, severity, location
  • Conformance Status — per-principle pass/fail summary
  • Critical Barriers — issues that completely block access
  • Positive Findings — what's already working well

Output

The evaluation results written to .metapowers/accessibility/$ARGUMENTS/02-evaluate.md. Present a summary to the user highlighting:

  • Total issues found by severity
  • Critical barriers requiring immediate attention
  • WCAG principles with most violations

Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

Install and usage instructions live in the source repository linked above.

Reviews

No reviews yet — be the first.

Versions

  • v0.1.0 Imported from the upstream source.