explain SKILL.md skillA
explain from thameema/memnos is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add thameema/memnos/explain@git:20261029.fa6bed5Pins git:20261029.fa6bed5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- thameema/memnos
- Path
plugins/tommy-explain/skills/explain/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261029.fa6bed5, committed Oct 29, 2026
- Size
- 2,974 bytes
- Repository stars
- 5
- License
- Apache-2.0
Explain code, a design, a bug, an error, a review finding or a trade-off in plain English with a concrete real-world scenario. Use when the user says "explain", "why", "what does this do", "I don't get it", "walk me through", "what could go wrong", or when a finding or decision needs to be understood by someone who has not read the code.
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
# Explain it so it sticks
The reader is smart and busy and has not read the code. Your job is that they understand in one pass and can decide what to do. Read the real code or output first; explain what is actually there, not what is typical.
## Shape of every explanation
1. **One-line answer first.** What it is, or what is wrong, in a sentence a non-author could repeat. No preamble.
2. **A real scenario.** Show it happening to someone or something concrete: a user, a request, a Tuesday-night deploy, two people clicking at once. Use real values from the code ("a customer with 3 items in the cart"), not "foo" and "bar". For a bug, tell the story of how it bites: who does what, what they see, what it costs.
3. **Why it works that way.** The one reason or trade-off behind it, in plain words. Define a term the first time you use it, in a few words, or avoid it.
4. **What to do.** The decision or next step, and what happens if they ignore it. If there are options, give a recommendation, not a survey.
5. **Where to look.** `file:line` for the real thing, so they can check you.
## Choosing the scenario
…Read the whole file at its exact version.
How to install
mdr add thameema/memnos/explain@sha256:9a0a07dabdc07677The line at the top of this page pins the label git:20261029.fa6bed5, 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_jwfwmpb44dizc57z)
0 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 29, 2026.
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 (2974 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
thameema/memnos · 5 stars · license Apache-2.0 · pushed 2026-11-05 · branch master
API
GET https://markdownregistry.com/api/v1/artifacts/art_jwfwmpb44dizc57z GET https://markdownregistry.com/api/v1/resolve?ref=thameema/memnos/explain GET https://markdownregistry.com/api/v1/blob/9a0a07dabdc0767796094eab5ed5b9884f898a01586d3a8ab64172c865c55c60
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.