explain SKILL.md skillA
explain from mickeyyaya/evolve-loop is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add mickeyyaya/evolve-loop/explain@git:20261008.8a0662ePins git:20261008.8a0662e in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- mickeyyaya/evolve-loop
- Path
skills/explain/SKILL.md- Versions recorded
- 2
- Latest version
- git:20261008.8a0662e, committed Oct 8, 2026
- First version recorded
- Jul 13, 2026
- Size
- 8,029 bytes
- Repository stars
- 6
- License
- Apache-2.0
Use when the user asks to explain how a feature/subsystem works and how the loops built it, or what the concurrent loops/lanes/cycles did and why. Default output = per-FEATURE HTML explainer pages (two movements — how it works today, then how it got built, with verified file:line claims and drift callouts) under docs/explain/; per-batch/per-lane story pages are the fallback framing. Derived from geoffreylitt/explain-diff-html, customized for evolve-loop.
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
# /evo:explain — per-feature HTML explainer Produce a rich, interactive HTML explanation of **how a feature/subsystem works and how the loops collectively built it**. The default unit of explanation is the **feature** (campaign/subsystem — e.g. token-telemetry, fleet-width, queue-integrity), aggregating ALL its contributing cycles across batches: one feature = many lanes/cycles = the complete idea. Per-lane or per-batch framing is the fallback when the user asks for a specific cycle range or batch story. Each feature page has two movements: first **how it works today** (architecture, data flow end to end, with diagrams and real example data), then **how it got built** (the contributing cycles in order, what each added, which incident or root cause motivated it, including instructive failures). Output goes to `docs/explain/<feature-slug>.html` plus a shared `docs/explain/index.html` (feature table + contributing-cycle map + the deep pipeline background, written once). Repo writes land ONLY at batch/wave-safe boundaries via the gated commit path — stage in the session scratchpad until the landing window. ## Step 1 — Gather per-lane data (this repo's sources) …
Read the whole file at its exact version.
How to install
mdr add mickeyyaya/evolve-loop/explain@sha256:ce749f5d52e25e62The line at the top of this page pins the label git:20261008.8a0662e, 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_x24yjjajnggfyy6i)
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 Oct 8, 2026, about one every 87 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261008.8a0662e latest | 2026-10-08 | 8a0662e | 8,029 B | A | view · diff |
| git:20260713.5c51bbd | 2026-07-13 | 5c51bbd | 7,870 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 (8029 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
mickeyyaya/evolve-loop · 6 stars · license Apache-2.0 · pushed 2026-11-07 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_x24yjjajnggfyy6i GET https://markdownregistry.com/api/v1/resolve?ref=mickeyyaya/evolve-loop/explain GET https://markdownregistry.com/api/v1/blob/ce749f5d52e25e6201b6310523f38804251113995f9b228d3abf7a9fa620ace0
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.
More from mickeyyaya/evolve-loop
Every file in mickeyyaya/evolve-loop