visual-evidence SKILL.md skillA
visual-evidence from kamiazya/whiteboard is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add kamiazya/whiteboard/visual-evidence@git:20261005.3fd603dPins git:20261005.3fd603d in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- kamiazya/whiteboard
- Path
.claude/skills/visual-evidence/SKILL.md- Versions recorded
- 7
- Latest version
- git:20261005.3fd603d, committed Oct 5, 2026
- First version recorded
- Aug 23, 2026
- Size
- 10,956 bytes
- Repository stars
- 10
- License
- Apache-2.0
Produce a before/after figure for a rendering change in this repo — render both versions through the real canvas-render pipeline, compose them side by side, and attach the PNG to the PR. Use whenever a change moves pixels (edge routing, layout, theme, SVG backend) and AGENTS.md's PR Visual Evidence rule applies.
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
# Before/after figures for a rendering change AGENTS.md requires visual evidence on a PR whose change has a user-visible effect. For a routing or layout change that means: the same canvas, rendered by the code before and after, side by side. A reviewer should see the defect and the fix without cloning anything. The whole thing is four steps and about five minutes. The traps below are the ones that actually cost time — every one of them has produced a wrong or misleading figure at least once. ## 1. Pick a case the change actually fixes **Do not eyeball this.** A canvas can look wrong for several reasons at once, and the biggest offender is usually not the one you fixed — twice, a case picked by "worst total ink" turned out to be dominated by a defect class the change did not touch, and the figure showed the same flaw on both sides. Select by the metric the change targets, and require it to go to zero: ```ts // throwaway test: score every corpus case before and after, keep the ones // this change actually repaired const fixed = Object.keys(before).filter((name) => before[name] > 0 && after[name] === 0) ``` …
Read the whole file at its exact version.
How to install
mdr add kamiazya/whiteboard/visual-evidence@sha256:5a309132cfe42fa9The line at the top of this page pins the label git:20261005.3fd603d, 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_cffmt2l3ajrxgrmt)
2 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 7 versions of this file, between Aug 23, 2026 and Oct 5, 2026, about one every 7 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261005.3fd603d latest | 2026-10-05 | 3fd603d | 10,956 B | A | view · diff |
| git:20261002.5a9037f | 2026-10-02 | 5a9037f | 10,636 B | A | view · diff |
| git:20260922.5faf649 | 2026-09-22 | 5faf649 | 9,837 B | A | view · diff |
| git:20260920.e1ea281 | 2026-09-20 | e1ea281 | 10,457 B | A | view · diff |
| git:20260902.7056439 | 2026-09-02 | 7056439 | 9,898 B | A | view · diff |
| git:20260823.d106b14 | 2026-08-23 | d106b14 | 9,009 B | A | view · diff |
| git:20260823.2a0aa89 | 2026-08-23 | 2a0aa89 | 7,615 B | A | view |
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 (10956 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
kamiazya/whiteboard · 10 stars · license Apache-2.0 · pushed 2026-10-19 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_cffmt2l3ajrxgrmt GET https://markdownregistry.com/api/v1/resolve?ref=kamiazya/whiteboard/visual-evidence GET https://markdownregistry.com/api/v1/blob/5a309132cfe42fa93d709e7592a2c112918482fac732a646223bd60c6ac9f9e3
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.