Name: Ui Audit
Author: tommygeoco

What breaks without openclaw ui audit skill

Design regressions merged without detection. Spacing and colour inconsistencies compounding across pages. No automated quality gate before PR approval.

→

Automated UI consistency audit × prioritised issue output ÷ 10–20 minutes ÷ no manual visual review = design regressions caught before production.

openclaw ui audit skill — what it actually does

Audit any HTML file, URL, or screenshot for visual consistency issues.

Receive a prioritised issue list with actionable fix recommendations.

Run UI audits as a CI/CD quality gate on every pull request.

Prefer HTML or code input over screenshots for semantic-rich analysis.

Identify spacing, colour, and layout regressions across multiple pages.

Security check — openclaw ui audit skill

Privacy score: 7/10 — accesses connected platform APIs only. Lock it: review OAuth scopes before install, confirm macOS, Linux; OpenClaw ≥1.0 compatibility.

Quick start — openclaw ui audit skill in 10–20 minutes

Setup time: 10–20 minutes

You need: OpenClaw core

Install the package:

# Install via ClawhHub
clawhub install tommygeoco/ui-audit

Install the skill

Provide an HTML file, URL, or screenshot path

Run /ui-audit <target> to start the audit

Receive a prioritised issue list with fix recommendations

Troubleshooting openclaw ui audit skill

1. Audits are static — dynamic state changes are not analysed

2. Screenshot input loses semantic information — HTML/code input produces richer results

Compatibility & status

Works with: macOS, Linux; OpenClaw ≥1.0 intermediate Last updated: Nov 2025 ★ 145 on GitHub MIT

Official docs →

View on GitHub →

Related — more like openclaw ui audit skill

More by tommygeoco

Every PR merged without a UI audit ships a visual regression you will pay to fix later. Install and add the audit to your CI/CD pipeline before the next merge window.

Get it on GitHub →