explain SKILL.md skillA
explain from harnessprotocol/harness-kit is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add harnessprotocol/harness-kit/explain@git:20260316.44e1f9cPins git:20260316.44e1f9c in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- harnessprotocol/harness-kit
- Path
plugins/explain/skills/explain/SKILL.md- Versions recorded
- 2
- Latest version
- git:20260316.44e1f9c, committed Mar 16, 2026
- First version recorded
- Mar 10, 2026
- Size
- 9,819 bytes
- Repository stars
- 10
- License
- Apache-2.0
Use when user invokes /explain with a file path, directory path, function/class name, or natural language concept. Also triggers on "explain this", "how does X work", "walk me through". Produces a structured, layered explanation of what the code does, how it connects, and where to start if you need to change it. Do NOT use when the user wants to trace data flow through a pipeline — use /lineage instead.
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
# Structured Code Explainer ## Overview Produce layered explanations of code — files, directories, functions, classes, or cross-cutting concepts. Designed for developers working in unfamiliar parts of a codebase. **Core principles:** 1. **Adaptive depth.** A single function gets a focused deep-dive. A directory gets a map first, then the user picks where to zoom. 2. **Project-aware.** If the project has a CLAUDE.md, reference its Architecture section to ground explanations in the project's own terminology. 3. **Conversation output.** Explanations go to the conversation, not files. The user can ask to save if they want. ## When to Use User types `/explain` followed by: - **File path** → explain that file - **Directory path** → map the directory structure, then explain key components - **Function or class name** → find the definition, explain it in context - **Natural language concept** → search the codebase for relevant files and explain the concept/flow ## Invocation Examples ``` /explain src/auth/middleware.ts /explain the payment processing flow /explain src/services/ /explain OrderProcessor.process /explain how webhooks get dispatched ``` ## Workflow Order (MANDATORY) …
Read the whole file at its exact version.
How to install
mdr add harnessprotocol/harness-kit/explain@sha256:c2bf0b98b232c475The line at the top of this page pins the label git:20260316.44e1f9c, 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_7qv3idbqk7f3sv7s)
5 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 2 versions of this file, between Mar 10, 2026 and Mar 16, 2026, about one every 6 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260316.44e1f9c latest | 2026-03-16 | 44e1f9c | 9,819 B | A | view · diff |
| git:20260310.2fcaf7f | 2026-03-10 | 2fcaf7f | 9,824 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 (9819 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
harnessprotocol/harness-kit · 10 stars · license Apache-2.0 · pushed 2026-11-06 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_7qv3idbqk7f3sv7s GET https://markdownregistry.com/api/v1/resolve?ref=harnessprotocol/harness-kit/explain GET https://markdownregistry.com/api/v1/blob/c2bf0b98b232c4750f35f39cd6904326554c95068b3d6612e479cf792fe2f05e
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 harnessprotocol/harness-kit
Every file in harnessprotocol/harness-kit