ui-audit skillA
ui-audit is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Review an existing interface and return ranked, concrete findings — each with its location, the user consequence, and a specific fix — instead of taste notes. Use when asked to critique, audit or review a screen or flow, when someone's UI work needs judging, or when an interface "feels off" and the problem needs naming. Not for proving a change renders and functions, not for inventing a new visual direction, and not for an accessibility conformance audit, which is its own discipline..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified against the hash recorded here before it reaches your agent. The deterministic audit below grades the latest version, and the same file always earns the same grade.
What the file says
# UI audit An audit that returns "the spacing feels cramped and the blue is a bit harsh" is worth nothing: it cannot be prioritised, argued with, or fixed. Every finding names a place, a consequence to a person trying to do something, and a change. ## When this fires An interface already exists and someone wants to know what is wrong with it — your work or theirs, a shipped screen or a prototype. It does not fire to prove a change works (`browser-verification`) or to establish a direction where none exists (`frontend-design`). ## Procedure 1. **Get the interface in front of you, rendered.** Source is not the interface. If you can only see screenshots or code, say so up front and mark the audit partial — several lens passes below are simply not available to you, and pretending otherwise is the main way these go wrong. 2. **Establish what the screen is for** before judging it: the primary task, who does it, and how often. An audit without this produces preferences. If nobody can tell you, write down your assumption and audit against it explicitly. 3. **Walk the primary task end to end**, as the user, at realistic data volume — not the demo …
Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/ui-audit@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/ui-audit@sha256:d2747d06c03e9cc5Pin to a label to follow the author's releases, or to a sha256 to freeze the exact bytes forever. Either way the resolved hash is written to mdr.lock, and mdr install reproduces it on any machine.
[](https://markdownregistry.com/a/art_3wog5i6wqkrssath)
1 badge views in 30 days
Versions
Audit of the latest version
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (6125 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No link to a raw IP address
- pass: No script tag
Source
nahid-sparktales/agent-dispatcher · 49 stars · license MIT · pushed 2026-09-23 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_3wog5i6wqkrssath GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/ui-audit GET https://markdownregistry.com/api/v1/blob/d2747d06c03e9cc50bf3c14326b2fac38cbf5483415be7e4494bb0fead8aae46
Your agent does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.