t4-engineering-records SKILL.md skillA
t4-engineering-records from xenodeve/xeno-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add xenodeve/xeno-skills/t4-engineering-records@git:20260718.e34b209Pins git:20260718.e34b209 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- xenodeve/xeno-skills
- Path
skills/t4/t4-engineering-records/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260718.e34b209, committed Jul 18, 2026
- First version recorded
- Jul 13, 2026
- Size
- 4,658 bytes
- Repository stars
- 2
- License
- MIT
Use when working in a T4-team repo (T4 Labs / Slow-Inc) and something notable just happened that a future agent will need the "why" of — you fixed and validated a bug, made a hard-to-reverse architectural decision, shipped a system-affecting change, or hit a bug whose lesson is worth keeping. Helps pick the right record (post-mortem vs ADR vs system-impact entry vs bug-case-catalog) and write it so it stays a reliable index (file:line, commit SHAs, validated-only). Triggers include…
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
# T4 Engineering Records ## Overview In an agent-primary repo, the record you write *is* the memory the next agent inherits — it can't ask you later. A record has value only if it is **findable, grounded, and true**: code identifiers (`file:line`, function names, commit SHAs) are the index that lets the next agent grep back to the actual change, and an unverified record is worse than none because it looks authoritative while being wrong. This skill answers two questions: **which record** to write, and **how** to write it so it stays reliable. ## Which record — decide first | What just happened | Record | Home | |---|---|---| | A bug is **fixed and validated** (reliable repro + known root cause + validated fix) | **post-mortem** | `docs/reports/YYYY-MM-DD-<slug>.md` + a pointer in the impact register | | A significant, **hard-to-reverse decision** — or a **quality / performance decision** whose rationale or benchmark would otherwise be lost — was made (already in the code, or explicitly planned) | **ADR** | `docs/adr/NNNN-<kebab>.md` + a row in `docs/adr/README.md` | …
Read the whole file at its exact version.
How to install
mdr add xenodeve/xeno-skills/t4-engineering-records@sha256:cb5174e5f4f29201The line at the top of this page pins the label git:20260718.e34b209, 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_qcqnjppxe5waa4zs)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Jul 13, 2026 and Jul 18, 2026, about one every 5 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260718.e34b209 latest | 2026-07-18 | e34b209 | 4,658 B | A | view · diff |
| git:20260713.89ec2dd | 2026-07-13 | 89ec2dd | 4,557 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 (4658 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
xenodeve/xeno-skills · 2 stars · license MIT · pushed 2026-10-12 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_qcqnjppxe5waa4zs GET https://markdownregistry.com/api/v1/resolve?ref=xenodeve/xeno-skills/t4-engineering-records GET https://markdownregistry.com/api/v1/blob/cb5174e5f4f292012b09ad6aa3e4c1873d75a46ccfaeedfd606a762d2a2a4e59
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.