Agent skill

UI Verification Skill: Browser Probes for UI Bugs

A skill that has your coding agent load the page and measure UI problems with browser probes for focus, hit targets, overflow, themes, failed requests and performance.

Install
git clone https://github.com/mblode/agent-skills.git
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the ui-verification skill?

The ui-verification skill is a SKILL.md from the mblode/agent-skills repo. It owns the browser session: your coding agent runs probes for focus order, target size, layout shift, overflow, failure states and axe violations, then reports reproduced, not-reproduced or unknown findings with evidence.

ui-verification is a skill in the mblode/agent-skills repo. Where its sibling UI skills reason about source code, this one loads the page in a browser and measures what a user would see, such as a 40 pixel control or a retry button wired to nothing.

Its output is findings tied to rule ids with reproducible evidence, plus a clearing re-run after a fix. It also has an exploratory mode that uses a finished feature like a real tester.

What changes in your agent's output

  • Nine probes: axe scan, target size, focus walk, layout shift, viewport stress, failure injection, theme and locale matrix, console and network, and web vitals
  • Each finding is marked reproduced, not-reproduced or unknown, never silently passed
  • Measurements carry units and conditions, for example 44 by 44 pixels at 360 pixels width
  • Skipped probes are listed with the reason, so missing coverage is visible
  • After a fix, the identical probe runs again and the result is recorded

The skill assigns no severity tier or ship verdict. It hands evidence back to the repo's ui-design audit skill for tiering. If you only need source level checks, fixing-accessibility works without a browser.

Who it is for

Best for

  • Confirming or killing suspected UI findings with a measurement
  • Re-checking a fix by repeating the same route, viewport and theme
  • Trying to break a finished feature before it ships

Not for

  • Reading source to find defects, which the repo assigns to its ui-design audit mode
  • Writing a durable test suite or maintaining pixel baselines
  • Field performance data. Lighthouse style numbers are lab measurements

Use it with UiChemy

Run it against a WordPress page you built with UiChemy once it is live or on staging. Probes for overflow at 320 pixels, target size and focus order will show what the Elementor or Gutenberg output actually does.