testing-and-benchmarking SKILL.md skillA
testing-and-benchmarking from yuiseki/map-from-scratch is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add yuiseki/map-from-scratch/testing-and-benchmarking@git:20261027.231c915Pins git:20261027.231c915 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- yuiseki/map-from-scratch
- Path
.agents/skills/testing-and-benchmarking/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261027.231c915, committed Oct 27, 2026
- First version recorded
- Oct 26, 2026
- Size
- 36,055 bytes
- Repository stars
- 24
- License
- GPL-3.0
What 41 map engines learnt about measuring renderers honestly (which build to time, GPU time versus frame time, noise floors and A/B order, validating a frame before timing it) and about checking their output (pixel-identical versus tolerant image tests, independent references, golden bake outputs, ratchets of known failures). Load it when writing or changing a bench.ts, spec.yaml budgets or verification checks, a bake test, or a native build line; before claiming that a change made something…
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
# Testing and benchmarking: numbers you can trust, pixels you can check A renderer is judged by two kinds of evidence: timings and checks of what it drew. Both lie in the same few ways across all 41 engines read here. Timings come from the wrong build (a debug or dev-transpiled one, 3.7x off in Mapnik [85]), from frames that drew nothing (very high FPS that means nothing [10]), from a clock that saturates at vsync [33], or from a single A/B run that heat and run order move by ±50% [33]. Checks compare against the renderer's own earlier output and so bless a consistent bug for years [92] [76], use one tolerance where a refactor should have been exact [8], or are golden files so large that nobody can debug a failure [37]. The engines that got this right fixed the definition of "done" before the code (size, startup, frame-rate budgets and pixel identity [6]), timed the shipped artifact [1][5], reported a noise floor next to every difference [1][18], validated output before timing it [86], and tested against references the renderer did not produce [76][79][92]. This repo already does the first part (every requirement is a budget, every bench has read-back checks …
Read the whole file at its exact version.
How to install
mdr add yuiseki/map-from-scratch/testing-and-benchmarking@sha256:47d92d88c62aa510The line at the top of this page pins the label git:20261027.231c915, 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_jytqdzvoa73tgd7a)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Oct 26, 2026 and Oct 27, 2026, more than one a day.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261027.231c915 latest | 2026-10-27 | 231c915 | 36,055 B | A | view · diff |
| git:20261026.79a684e | 2026-10-26 | 79a684e | 36,052 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 (36055 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
yuiseki/map-from-scratch · 24 stars · license GPL-3.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_jytqdzvoa73tgd7a GET https://markdownregistry.com/api/v1/resolve?ref=yuiseki/map-from-scratch/testing-and-benchmarking GET https://markdownregistry.com/api/v1/blob/47d92d88c62aa510720c9a41db1f7c1662c4bb96e68b8318c6ad97d4699fb51a
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.