spec-to-code-fidelity SKILL.md skillA
spec-to-code-fidelity from rlaope/ultraprompt is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add rlaope/ultraprompt/spec-to-code-fidelity@git:20260915.a5ced99Pins git:20260915.a5ced99 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- rlaope/ultraprompt
- Path
skills/spec-to-code-fidelity/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260915.a5ced99, committed Sep 15, 2026
- First version recorded
- Jul 5, 2026
- Size
- 12,632 bytes
- Repository stars
- 35
- License
- MIT
Invoke when implementing from an authoritative written source — an RFC, academic paper, binary format spec, protocol document, or mathematical derivation — where correctness means matching the document, not just passing ad-hoc tests.
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
# Spec-to-Code Fidelity > Status: v0.1 baseline draft — derived from the case catalog and axis definitions; awaiting trace evidence from Fable 5.1 case runs. ## When to apply - Implementing a protocol or format from an RFC, W3C/WHATWG spec, or vendor format document (HTTP/1.1, WebSocket framing, GGUF, JWT, WAI-ARIA). - Translating equations from a paper into code (attention math, quantization schemes, PPO loss, numerical integrators). - Writing a parser/serializer for a binary or wire format where a single off-by-one silently corrupts everything downstream. - Porting a reference implementation to another language while claiming behavioral equivalence. - Any task where the acceptance criterion is "conforms to the document" rather than "seems to work." - Debugging interop failures where your implementation and a peer disagree about what the spec says. ## Core loop 1. **Acquire the authoritative text before writing code.** Get the actual RFC/paper/spec section into context — not your memory of it. If the exact document version matters (RFC obsoleted-by chains, paper v1 vs v2 on arXiv), pin the version and record it in a comment at the top of the implementation. …
Read the whole file at its exact version.
How to install
mdr add rlaope/ultraprompt/spec-to-code-fidelity@sha256:84f1a6356ee5623fThe line at the top of this page pins the label git:20260915.a5ced99, 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_n3wor3in2j4asyv7)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 5, 2026 and Sep 15, 2026, about one every 72 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260915.a5ced99 latest | 2026-09-15 | a5ced99 | 12,632 B | A | view · diff |
| git:20260705.c12b4fc | 2026-07-05 | c12b4fc | 12,630 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 (12632 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
rlaope/ultraprompt · 35 stars · license MIT · pushed 2026-10-28 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_n3wor3in2j4asyv7 GET https://markdownregistry.com/api/v1/resolve?ref=rlaope/ultraprompt/spec-to-code-fidelity GET https://markdownregistry.com/api/v1/blob/84f1a6356ee5623fd95c14537a19c1907a206b3d868fe349978d758215bfb7e8
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.