explain-systems-visually SKILL.md skillA
explain-systems-visually from shubham0704/claude-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add shubham0704/claude-skills/explain-systems-visually@git:20261001.b885f69Pins git:20261001.b885f69 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- shubham0704/claude-skills
- Path
explain-systems-visually/SKILL.md- Versions recorded
- 1
- Latest version
- git:20261001.b885f69, committed Oct 1, 2026
- Size
- 8,969 bytes
- Repository stars
- 2
- License
- MIT
Create or revise technical teaching slides and visual walkthroughs with prerequisite-aware progression, explicit inputs and outputs, stable color-linked equations and algorithm steps, and checks for understanding and recall. Use when readers must connect a system's purpose, components, mathematics, and execution.
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 Systems Visually Teach why each object is needed, what it means, and how it advances the opening question. A readable diagram and a defined symbol do not establish understanding. Preserve the overall map while revealing each operation and its consequences. Respect the requested medium, audience, and duration. A teaching walkthrough and a short research talk need different depth; do not turn every request into a deck or add slides automatically. Retain an equation-and-text format when requested. ## Establish the teaching contract Read the current source and implementation before explaining them. Retain their notation and abstraction boundaries; identify source disagreements instead of silently combining versions. Separate supplied method, implementation choices, proposed extensions, and demonstrated results. State the audience's starting knowledge and one question the explanation should enable them to answer. Put the intended output or decision near the beginning, before its machinery. If audience or duration is missing, state a reasonable assumption; ask only when the answer would materially change the artifact. …
Read the whole file at its exact version.
How to install
mdr add shubham0704/claude-skills/explain-systems-visually@sha256:e07768e7ed411419The line at the top of this page pins the label git:20261001.b885f69, 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_zb3azbnhi4j6wf2x)
4 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 1 version of this file, committed on Oct 1, 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 (8969 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
shubham0704/claude-skills · 2 stars · license MIT · pushed 2026-10-08 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_zb3azbnhi4j6wf2x GET https://markdownregistry.com/api/v1/resolve?ref=shubham0704/claude-skills/explain-systems-visually GET https://markdownregistry.com/api/v1/blob/e07768e7ed4114196b3215413e071801a840405eaebc96fe697964e0c4ea8c43
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.