interface-review SKILL.md skillA
interface-review from jakubkrehel/skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add jakubkrehel/skills/interface-review@git:20261118.8d4b209Pins git:20261118.8d4b209 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- jakubkrehel/skills
- Path
skills/interface-review/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261118.8d4b209, committed Nov 18, 2026
- First version recorded
- Aug 29, 2026
- Size
- 10,312 bytes
- Repository stars
- 12,374
- License
- MIT
Reviews a branch, pull request or uncommitted change for the interface problems it introduced or regressed, across accessibility, layout, writing, typography, color, UI and motion.
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
# Interface review This skill reviews a change rather than a screen. It resolves the scope, expands the changed files to the surfaces they affect, reads both sides of the diff and classifies every finding. It owns the scope, the classification and the change-scoped report. Domain rules belong to the `better-*` skills. Severity, consolidation, coverage, the cap and the verdict belong to `better-interface`, which this skill hands the review to. Correctness, tests, security and performance belong to the project's general code review. Name such a concern once, point at that review and drop it. ## The change, not the codebase The author is asking "did I make this worse?". Report what the change caused and stay mostly quiet about what it merely touched. Three pre-existing findings is a courtesy; thirty is a different review and one nobody asked for. Read the whole diff before forming an opinion of it. A skimmed diff produces findings about code the next hunk already fixed. ## 1. Resolve the change scope first …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_yiczavoehc7p26xn/57dbc1dae8b3386a4dbd8ff8b359af255af4b9d3abea905a8959544a10b8efea.json
Then /plugin install interface-review@markdownregistry-yiczavoehc7p26xn in Claude Code. It installs git:20261118.8d4b209, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add jakubkrehel/skills/interface-review@sha256:57dbc1dae8b3386aThe line at the top of this page pins the label git:20261118.8d4b209, 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_yiczavoehc7p26xn)
0 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 jakubkrehel/skills/interface-review 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 interface-review from somewhere else? Ask it: where did my interface-review 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 Aug 29, 2026 and Nov 18, 2026, about one every 20 days.
Watch this file (sign in, one email per new version)
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261118.8d4b209 latest | 2026-11-18 | 8d4b209 | 10,312 B | A | view · diff |
| git:20261117.19ab1fa | 2026-11-17 | 19ab1fa | 10,304 B | A | view · diff |
| git:20261024.1eb03d2 | 2026-10-24 | 1eb03d2 | 10,128 B | A | view · diff |
| git:20261005.da5f6d5 | 2026-10-05 | da5f6d5 | 10,159 B | A | view · diff |
| git:20260829.267330e | 2026-08-29 | 267330e | 10,690 B | A | view |
Copies
1 file in 1 other repository holds the exact bytes of one of this file's versions, each committed after this file had them: it holds an older version.
- aiskillstore/marketplace · pending/jakubkrehel/interface-review/SKILL.md · 4 versions behind · 486 stars
A copy does not update when this file does. Whoever holds one can learn which version it is with the Check your copy box below, or by asking their agent. Matched on exact bytes and commit dates only.
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/interface-review/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 (10312 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
jakubkrehel/skills · 12,374 stars · license MIT · pushed 2026-11-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_yiczavoehc7p26xn GET https://markdownregistry.com/api/v1/resolve?ref=jakubkrehel/skills/interface-review GET https://markdownregistry.com/api/v1/blob/57dbc1dae8b3386a4dbd8ff8b359af255af4b9d3abea905a8959544a10b8efea
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 jakubkrehel/skills
Every file in jakubkrehel/skills