a11y-debuggingUses Chrome DevTools MCP for accessibility (a11y) debugging and auditing based on web.dev guidelines. Use when testing semantic HTML, ARIA labels, focus stat...
Install via ClawdBot CLI:
clawdbot install poiuy1318/a11y-debuggingGrade Fair — based on market validation, documentation quality, package completeness, maintenance status, and authenticity signals.
Calls external URL not in known-safe list
https://web.dev/articles/accessible-tap-targets`Audited Apr 16, 2026 · audit v1.0
Generated May 9, 2026
Use Chrome DevTools MCP to run Lighthouse audits on large corporate websites to detect accessibility violations. This provides a baseline score and identifies failing elements, enabling teams to prioritize fixes based on web.dev guidelines.
Check that all form inputs in an e-commerce checkout flow have proper labels and accessible names. Use the 'Find Orphaned Form Inputs' snippet to ensure no inputs are missing labels, improving screen reader usability.
Verify focus order and keyboard traps in a single-page application by pressing Tab and checking the accessibility tree snapshot. Ensures users can navigate all interactive elements without getting stuck.
Use the 'Measure Tap Target Size' snippet to verify that buttons and links are at least 48x48 pixels. Pass the element's UID from the accessibility tree to script to ensure compliance with mobile accessibility standards.
Offer monthly audits and remediation support using the debugging skill. Clients receive regular reports and actionable insights, billed on a subscription basis.
Perform a comprehensive accessibility audit for a fixed fee, delivering a detailed report with prioritized fixes. Ideal for companies needing compliance before launch.
Train in-house teams to use the skill package for ongoing accessibility maintenance. Revenue comes from training sessions and follow-up support.
💬 Integration Tip
Integrate with CI/CD pipelines by running Lighthouse audits via CLI commands and capturing the report for automatic regression testing.
Scored May 9, 2026
Control desktop applications on Windows — launch, close, focus, resize, move windows, simulate keyboard/mouse input, manage processes, control VSCode, read clipboard, and capture screen info. Use when the user wants to interact with any running program, switch windows, type text, press shortcuts, open files in VSCode, manage running processes, or get system display information.
Conduct rigorous, adversarial code reviews with zero tolerance for mediocrity. Use when users ask to "critically review" my code or a PR, "critique my code", "find issues in my code", or "what's wrong with this code". Identifies security holes, lazy patterns, edge case failures, and bad practices across Python, R, JavaScript/TypeScript, SQL, and front-end code. Scrutinizes error handling, type safety, performance, accessibility, and code quality. Provides structured feedback with severity tiers (Blocking, Required, Suggestions) and specific, actionable recommendations.
Coding style memory that adapts to your preferences, conventions, and patterns for consistent coding.
Pragmatic coding standards for writing clean, maintainable code — naming, functions, structure, anti-patterns, and pre-edit safety checks. Use when writing new code, refactoring existing code, reviewing code quality, or establishing coding standards.
Claude Code integration for OpenClaw. This skill provides interfaces to: - Query Claude Code documentation from https://code.claude.com/docs - Manage subagents and coding tasks - Execute AI-assisted coding workflows - Access best practices and common workflows Use this skill when users want to: - Get help with coding tasks - Query Claude Code documentation - Manage AI-assisted development workflows - Execute complex programming tasks
Plan, draft, version, and refine written content with enforced versioning and quality audits.