visual-verification skillA
visual-verification is agent-read markdown (skill) from nahid-sparktales/agent-dispatcher: Prove a UI looks right across every state and viewport it has to survive — enumerate the state matrix, make captures deterministic, compare against a baseline captured the same way, and triage every diff. Use before calling a visual change, a style refactor or a redesign done, when running or trusting a screenshot-comparison suite, and when asked whether a screen still looks correct. Not for judging whether a design is good, not for proving controls actually work, and never on its own sufficient.
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
# Visual verification
A screenshot is evidence that pixels were produced. It is not evidence that they were produced by
your change, that they are correct, or that anything behind them works. This procedure turns
screenshots into an argument that survives being questioned.
## When this fires
Before reporting a change to appearance as done — CSS, layout, theming, spacing, a component's
visual states, a design-system swap. Also when a visual regression suite reports a diff, or
reports none and someone is about to treat that as proof. It does not fire for changes with no
visual surface, and it does not fire when the question is whether the design is any good.
## Procedure
1. **Derive the surface from the change, not from the app.** List the components and routes the
change can reach. A shared token or a base component reaches far more than the page you edited
— grep the usages before deciding the surface is one screen.
2. **Write the matrix down before capturing anything.** States × viewports × themes:
- states — default, empty, loading, error, long content, truncated content, disabled, focused,
hovered, selected, and whatever this component's own states are
…Read the whole file at its exact version.
How to install
mdr add nahid-sparktales/agent-dispatcher/visual-verification@git:20260919.a0d4f55mdr add nahid-sparktales/agent-dispatcher/visual-verification@sha256:1b4131bd6c05ce36Pin 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_7v2skfx25f272r77)
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 (7787 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_7v2skfx25f272r77 GET https://markdownregistry.com/api/v1/resolve?ref=nahid-sparktales/agent-dispatcher/visual-verification GET https://markdownregistry.com/api/v1/blob/1b4131bd6c05ce3669df6a2107db494492cdbeeca899edcede62347e43a77ce0
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.
More from nahid-sparktales/agent-dispatcher
Every file in nahid-sparktales/agent-dispatcher