Report
A Claude Code plugin that adds an agentic skills framework, with MCP's and a meta prompting processes. Inspired by "Superpowers" & "Figma Console MCP", but not just for development or design; but for all aspect within the digital production cycle.
npx -y skills add bromso/metapowers --skill reportAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Generate a structured accessibility audit report with remediation guidance
SKILL.md
1.9 KB, as published. Nobody here has run it
Report
Generate a comprehensive accessibility audit report for "$ARGUMENTS" with executive summary, detailed findings, and prioritized remediation steps.
Prerequisites
Read .metapowers/accessibility/$ARGUMENTS/02-evaluate.md. If this file does not exist, tell the user:
Phase 2 (Evaluate) has not been completed for "$ARGUMENTS". Run
/accessibility:evaluate $ARGUMENTSfirst, or use--skip-checksto bypass.
If --skip-checks is present in $ARGUMENTS, skip this check and log to .metapowers/accessibility/$ARGUMENTS/skip-log.md.
Process
-
Read context files:
- Read
.metapowers/accessibility/$ARGUMENTS/01-scope.mdfor audit scope - Read
.metapowers/accessibility/$ARGUMENTS/02-evaluate.mdfor discovered issues - Read
plugins/accessibility/shared/audit-report-template.mdfor output structure - Read
plugins/accessibility/shared/remediation-patterns.mdfor fix guidance
- Read
-
Create executive summary:
- Overall conformance status
- Total issues by severity
- Key findings in plain language
- Business impact assessment
-
Document detailed findings:
- For each issue: description, WCAG criterion, severity, location, impact, remediation steps
- Include code examples (before/after) where applicable
- Group by WCAG principle for easy navigation
-
Prioritize remediation:
- Critical issues first (blocking access)
- Then major issues (significant barriers)
- Then minor issues (enhancements)
- Estimate effort for each fix (quick fix vs. significant rework)
-
Write the artifact to
.metapowers/accessibility/$ARGUMENTS/03-report.mdfollowing the audit report template.
Output
The audit report written to .metapowers/accessibility/$ARGUMENTS/03-report.md. Present a summary to the user highlighting:
- Conformance status
- Top priority issues to fix
- Estimated remediation effort