technical-explanation SKILL.md skillA
technical-explanation from metraton/gaia is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add metraton/gaia/technical-explanation@git:20261006.f5d0899Pins git:20261006.f5d0899 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- metraton/gaia
- Path
skills/technical-explanation/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261006.f5d0899, committed Oct 6, 2026
- First version recorded
- Sep 25, 2026
- Size
- 16,055 bytes
- Repository stars
- 4
- License
- MIT
Use when the deliverable explains a system, a process, an architecture, or a failure -- a bare "explain X", "how does this work", "what happened here", "qué es esto", "explicame cómo funciona", a status the reader must understand rather than execute, or the explanatory part of a README, a ticket, a deck, or a report. Loaded by the orchestrator when its answer explains, and by any specialist whose output explains.
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
# Technical Explanation An explanation builds a mental model in the reader's head: what exists, how it connects, what happens, and why -- in that order, at the altitude the reader can hold, with one picture where a picture teaches faster than a sentence. This skill is the shared vocabulary for doing that: the four decisions taken before writing, the fixed order the model is built in, the two registers it is told in, and the drawing rules for the one picture a fenced code block can carry. Whoever produces an explanation loads it -- the orchestrator answering "explain X", a specialist writing the narrative of a README, the objective of a ticket, or the idea behind a deck. The container skills (`readme-writing`, `ticket-writing`, `diagram-builder`) own their format and continue from here; this skill owns what goes inside when the content explains. The skill sits mid-flow. Upstream is a finding, a request, or a status already established by investigation; it never re-derives those. Downstream is a container that consumes the explanation as written -- so an explanation built in the wrong order does not stay a local defect: the README that embeds it teaches …
Read the whole file at its exact version.
How to install
mdr add metraton/gaia/technical-explanation@sha256:10b300d2d39900adThe line at the top of this page pins the label git:20261006.f5d0899, 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_wge52eahlacvesqm)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Sep 25, 2026 and Oct 6, 2026, about one every 12 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261006.f5d0899 latest | 2026-10-06 | f5d0899 | 16,055 B | A | view · diff |
| git:20260925.3549fb0 | 2026-09-25 | 3549fb0 | 16,087 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 (16055 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
metraton/gaia · 4 stars · license MIT · pushed 2026-11-05 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_wge52eahlacvesqm GET https://markdownregistry.com/api/v1/resolve?ref=metraton/gaia/technical-explanation GET https://markdownregistry.com/api/v1/blob/10b300d2d39900ada04541856d62073acdfb8a3919d2858d7f65a576a4f08201
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.