explain SKILL.md skillA
explain from gufranco/claude-engineering-rules is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add gufranco/claude-engineering-rules/explain@git:20261012.84ebb18Pins git:20261012.84ebb18 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- gufranco/claude-engineering-rules
- Path
skills/explain/SKILL.md- Versions recorded
- 5
- Latest version
- git:20261012.84ebb18, committed Oct 12, 2026
- First version recorded
- Apr 4, 2026
- Size
- 7,399 bytes
- Repository stars
- 3
- License
- MIT
Explain code with educational depth. Generates Mermaid diagrams for architecture and data flow, traces data through the codebase, explains design decisions with rationale, identifies patterns, and suggests improvements. Use when user says "explain", "explain this code", "how does this work", "walk me through", "what does this do", "trace the data flow", or wants to understand a file, directory, or system with educational depth. For code review, use /review; for debugging, use /investigate; for…
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
## Overview Code explanation skill with educational depth. Analyzes code structure, traces data flow, identifies patterns, and produces Mermaid diagrams to make complex systems understandable. ## When to Use Run when the goal is understanding a file, directory, or flow. Pick `--depth shallow` for a quick orientation and the default `deep` when the reader will change the code next. ### Invocation | Invocation | Action | |-----------|--------| | `/explain` | Explain the current file or most recently discussed code | | `/explain <path>` | Explain a specific file or directory | | `/explain --depth shallow` | High-level overview only | | `/explain --depth deep` | Full analysis with data flow tracing and pattern identification | If no `--depth` is specified, default to `deep`. --- ## Steps 1. **Identify the target.** Determine what to explain: - If no argument: use the most recently discussed file or ask for clarification. - If a file path: read the file. - If a directory path: read the directory listing, then read key files to understand the module. 2. **High-level overview.** Start with what the code does in plain language: …
Read the whole file at its exact version.
How to install
mdr add gufranco/claude-engineering-rules/explain@sha256:95db6ae786697413The line at the top of this page pins the label git:20261012.84ebb18, 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_ulzhctwdbqvjtodu)
1 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 5 versions of this file, between Apr 4, 2026 and Oct 12, 2026, about one every 48 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20261012.84ebb18 latest | 2026-10-12 | 84ebb18 | 7,399 B | A | view · diff |
| git:20260522.30b2aa6 | 2026-05-22 | 30b2aa6 | 5,543 B | A | view · diff |
| git:20260521.5220622 | 2026-05-21 | 5220622 | 5,537 B | A | view · diff |
| git:20260404.0b77659 | 2026-04-04 | 0b77659 | 5,528 B | A | view · diff |
| git:20260404.039ea3a | 2026-04-04 | 039ea3a | 5,525 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 (7399 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
gufranco/claude-engineering-rules · 3 stars · license MIT · pushed 2026-10-30 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ulzhctwdbqvjtodu GET https://markdownregistry.com/api/v1/resolve?ref=gufranco/claude-engineering-rules/explain GET https://markdownregistry.com/api/v1/blob/95db6ae786697413571917df7b9fbc68038cfa73e587a0b1ff6b377a1c2544f2
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 gufranco/claude-engineering-rules
Every file in gufranco/claude-engineering-rules