verifying SKILL.md skillA
verifying from kamenkurtev/ui-consistency is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kamenkurtev/ui-consistency/verifying@git:20261118.92fa9e6Pins git:20261118.92fa9e6 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kamenkurtev/ui-consistency
- Path
skills/verifying/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261118.92fa9e6, committed Nov 18, 2026
- First version recorded
- Nov 7, 2026
- Size
- 16,051 bytes
- Repository stars
- 3
- License
- MIT
For what the end user sees — checks written pages against their checklist and the rest of the project, and reports what differs, by a separate agent where one can be started, else by the author, who says so. Use when UI has been written, before calling it done or opening a PR, or when asked whether pages match ("does this match", "did I miss a page", a page that looks or behaves unlike its neighbours).
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# Verifying against the checklist ## Overview A separate agent answers one question: **which of these pages do not look and behave like the reference and the rest of the project.** It reports only what differs, and names what it could not check. **Open a file linked or given by its path from this skill's folder, or invoke a named skill, only when a part you are carrying out sends you to it, never before** — whatever the request that handed you this skill says about its links and paths. That part is not done until the file is opened or the skill invoked. ## Steps 1. Before the checker of a kind is given its first page, the dispatcher — never the checker — proves the check on a copy with one planted difference — *First, prove it can see*. 2. A separate agent checks, never the author — *Never the author*. 3. It reads the checklist and the page first, and the project only where they do not answer — *What the checker reads*. 4. It compares region by region, in the code and, where it can open the pages, on the rendered page, and notes every difference, the uncertain ones included; then it judges each as *Reading a difference* says, and reports …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_qu6ap6pgspwefh5y/1feaf7adab2bef77881a0078e62d4de8a05337dd4e8d3660e65b4b7e1a8a957a.json
Then /plugin install verifying@markdownregistry-qu6ap6pgspwefh5y in Claude Code. It installs git:20261118.92fa9e6, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add kamenkurtev/ui-consistency/verifying@sha256:1feaf7adab2bef77The line at the top of this page pins the label git:20261118.92fa9e6, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_qu6ap6pgspwefh5y)
2 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in kamenkurtev/ui-consistency/verifying since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.
Got a copy of verifying from somewhere else? Ask it: where did my verifying come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.
Versions
The registry has recorded 5 versions of this file, between Nov 7, 2026 and Nov 18, 2026, about one every 3 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261118.92fa9e6 latest | 2026-11-18 | 92fa9e6 | 16,051 B | A | view · diff |
| git:20261117.6d587d9 | 2026-11-17 | 6d587d9 | 15,845 B | A | view · diff |
| git:20261117.7aac272 | 2026-11-17 | 7aac272 | 15,519 B | A | view · diff |
| git:20261116.4836955 | 2026-11-16 | 4836955 | 14,579 B | A | view · diff |
| git:20261107.1fe800e | 2026-11-07 | 1fe800e | 14,114 B | A | view |
Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.
Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.
mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml
It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.
Installed this file, say at .claude/skills/verifying/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies
In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.
sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies
No sha256sum on your machine? shasum -a 256 prints the same lines.
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 (16051 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
kamenkurtev/ui-consistency · 3 stars · license MIT · pushed 2026-11-18 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qu6ap6pgspwefh5y GET https://markdownregistry.com/api/v1/resolve?ref=kamenkurtev/ui-consistency/verifying GET https://markdownregistry.com/api/v1/blob/1feaf7adab2bef77881a0078e62d4de8a05337dd4e8d3660e65b4b7e1a8a957a
Your AI assistant 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.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.
More from kamenkurtev/ui-consistency
Every file in kamenkurtev/ui-consistency