explain SKILL.md skillA

explain from teambrilliant/dev-skills is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned
mdr add teambrilliant/dev-skills/explain@git:20261008.81e7416

Pins git:20261008.81e7416 in mdr.lock. Pin the fingerprint instead.

Audit grade
A, 17 of 17 checks passed
Kind
SKILL.md skill
Repository
teambrilliant/dev-skills
Path
skills/explain/SKILL.md
Versions recorded
3
Latest version
git:20261008.81e7416, committed Oct 8, 2026
First version recorded
Sep 27, 2026
Size
4,526 bytes
Repository stars
5
License
none declared

Explain a plan, a shape, a shipped change, code, or the last message so it's impossible to misunderstand — an ASCII drawing of how it works, then plain words, facts kept verbatim. Like SQL's EXPLAIN for a query plan. Use when someone says "explain simply", "use ascii to explain", "explain the plan to me", "that didn't land", "too dense", "I don't get it", "walk me through what we shipped", or needs to understand and defend a system to their team.

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

SQL's `EXPLAIN` shows how a query will actually run. This does the same for work: how the thing actually runs, drawn and said so plainly it can't be misread. The goal is that the developer can stand at a whiteboard and explain it — and defend it — without line-level knowledge.

## What to explain

- **`/explain` with no argument, or "that didn't land" / "too dense" / "I don't get it"** → your most recent assistant message. Re-explain it only: no tools, no new information, no answering a new question. If there's no previous message, say there's nothing to explain yet.
- **A file** (`thoughts/shapes/…`, `thoughts/plans/…`) → read it and explain what it will build and how.
- **A shipped change** (branch, PR, "what we just built") → read the diff, the touched code, and the git log. Plans go stale, so explain what the code does now; where it differs from the plan, say so.
- **Anything else** (a module, a flow, an error, a concept) → read what's needed and explain it the same way. The four questions below apply only if it's customer-facing.

## How
…

Read the whole file at its exact version.

How to install

No tool to install first
claude plugin marketplace add https://markdownregistry.com/mp/a/art_xbi65e5vhbxy2hwo/a21b3cd3bd2b0c24bbb43b4c35b0d1e4a650756783ed38da4c6833a3dcb11372.json

Then /plugin install explain@markdownregistry-xbi65e5vhbxy2hwo in Claude Code. It installs git:20261008.81e7416, the one graded A here, pinned to the commit it was graded at, and leaves it there.

The exact contents, by fingerprint
mdr add teambrilliant/dev-skills/explain@sha256:a21b3cd3bd2b0c24

The line at the top of this page pins the label git:20261008.81e7416, 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.

Badge

mdr badge

[![mdr](https://markdownregistry.com/badge/art_xbi65e5vhbxy2hwo.svg)](https://markdownregistry.com/a/art_xbi65e5vhbxy2hwo)

3 badge image fetches in 30 days. What the badge shows.

Ask from your agent
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry

Then ask it: what changed in teambrilliant/dev-skills/explain since the version I have? It reads every saved version here, no key and no account. Any agent that speaks MCP can add it.

Got a copy of explain from somewhere else? Ask it: where did my explain come from, and what was changed? It names the public original, the version yours is closest to and every changed line. The text is not kept.

Versions

The registry has recorded 3 versions of this file, between Sep 27, 2026 and Oct 8, 2026, about one every 5 days.

Watch this file (sign in, one email per new version)

versioncommittedcommitsizeaudit
git:20261008.81e7416 latest2026-10-08 81e7416 4,526 BA view · diff
git:20261008.8e403b12026-10-08 8e403b1 4,706 BA view · diff
git:20260927.b9558d02026-09-27 b9558d0 4,239 BA view
Keep it current by itself, install once

Committed this skill to a repository? Install the markdownregistry skill updates app on it, or on all of them. When the registry saves a newer version, a pull request brings your copy to it within minutes, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

Install on GitHub

It asks to read and write contents and pull requests, and to read metadata. No workflow file, no Actions setting, nothing runs on your runners. Uninstall it and everything the registry kept about your repository is deleted.

Keep it current by itself

Committed this skill to a repository? Add one workflow file, and when a newer version is saved, a pull request brings your copy to it, the newest version first, then what changed and any check it newly trips. A copy you edited is never touched, and nothing is deleted.

mkdir -p .github/workflows && curl -fsSL https://markdownregistry.com/ci/skill-updates.yml -o .github/workflows/skill-updates.yml

It runs daily on GitHub Actions, no key and no account. Read the workflow before you add it.

Check a whole project

From the root of your project, one line hashes each installed skill's SKILL.md, your AGENTS.md and your CLAUDE.md, and asks the registry once. Only the fingerprints and paths are sent.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --data-binary @- https://markdownregistry.com/api/v1/check-copies

In CI, add --fail-with-body: the answer is 409 when any file is behind, so the step fails and still prints which files.

sha256sum .claude/skills/*/SKILL.md AGENTS.md CLAUDE.md | curl -s --fail-with-body --data-binary @- https://markdownregistry.com/api/v1/check-copies

No sha256sum on your machine? shasum -a 256 prints the same lines.

Audit of the latest version

A  17 of 17 checks passed. Fixed automatic checks with no AI involved, so the same checks give the same answer every run.
  • pass: Frontmatter block present
  • pass: Frontmatter declares a name
  • pass: Frontmatter declares a description
  • pass: Size between 200 bytes and 200 KB (4526 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

GitHub

teambrilliant/dev-skills · 5 stars · license none declared · pushed 2026-10-26 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_xbi65e5vhbxy2hwo
GET https://markdownregistry.com/api/v1/resolve?ref=teambrilliant/dev-skills/explain
GET https://markdownregistry.com/api/v1/blob/a21b3cd3bd2b0c24bbb43b4c35b0d1e4a650756783ed38da4c6833a3dcb11372

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 teambrilliant/dev-skills

CLAUDE.md CLAUDE.md file
teambrilliant/dev-skills · CLAUDE.md
git:20261008.865c794 · audit A · 5 stars
execute-plan SKILL.md skill
teambrilliant/dev-skills · skills/execute-plan/SKILL.md · Execute an approved plan from thoughts/plans/ to completion — every phase, every check, every acceptance criterion —…
git:20261026.069feb8 · audit A · 5 stars
product-discovery SKILL.md skill
teambrilliant/dev-skills · skills/product-discovery/SKILL.md · Validate whether a product idea will actually work before committing engineering — find what you don't know, design the…
git:20260927.b9558d0 · audit A · 5 stars
product-primitives SKILL.md skill
teambrilliant/dev-skills · skills/product-primitives/SKILL.md · Break down complex products, features, or systems into fundamental primitives and building blocks from a software…
git:20260507.c5d07e6 · audit A · 5 stars
product-thinker SKILL.md skill
teambrilliant/dev-skills · skills/product-thinker/SKILL.md · Use for product decisions, user behavior analysis, and UX evaluation. Trigger when the user wants to: evaluate whether…
git:20261008.81e7416 · audit A · 5 stars
qa-test SKILL.md skill
teambrilliant/dev-skills · skills/qa-test/SKILL.md · Browser-based QA verification after any implementation. Use when someone says "QA this", "test this in browser"…
git:20260927.b9558d0 · audit A · 5 stars
shaping-work SKILL.md skill
teambrilliant/dev-skills · skills/shaping-work/SKILL.md · Shape rough ideas into clear, actionable work definitions. Use this skill whenever someone has an unstructured idea…
git:20261008.81e7416 · audit A · 5 stars
strategic-thinker SKILL.md skill
teambrilliant/dev-skills · skills/strategic-thinker/SKILL.md · Use for cross-domain strategic reasoning, approach selection, and systems-level analysis. Trigger when the user wants…
git:20261008.81e7416 · audit A · 5 stars
working-backwards SKILL.md skill
teambrilliant/dev-skills · skills/working-backwards/SKILL.md · Write an Amazon-style PR-FAQ (mock press release + FAQ) to pressure-test a product idea customer-first and kill weak…
git:20261008.81e7416 · audit A · 5 stars
write-plan SKILL.md skill
teambrilliant/dev-skills · skills/write-plan/SKILL.md · Write a technical implementation plan to thoughts/plans/ before coding starts (separate from the harness's plan mode)…
git:20261008.81e7416 · audit A · 5 stars

Every file in teambrilliant/dev-skills

Other files named explain

explain SKILL.md skill
dcouple/pane · main/src/services/paneChatBundle/skills/explain/SKILL.md · Use when the person wants to understand a concept or how something works today. Never plans.
git:20260924.17234b5 · audit A · 652 stars
explain SKILL.md skill
greenfield-inc/pane · main/src/services/paneChatBundle/skills/explain/SKILL.md · Use when the person wants to understand a concept or how something works today. Never plans.
git:20260924.17234b5 · audit A · 644 stars
explain SKILL.md skill
sysevol-ai/codenib · plugins/codenib/skills/explain/SKILL.md · Explain how something in this repository works, where it is implemented, or what calls it, with every claim tied to…
git:20261116.1ab51d6 · audit B · 95 stars
explain SKILL.md skill
0xdarkmatter/claude-mods · skills/explain/SKILL.md · Deep explanation of complex code, files, or concepts. Dispatches skill-preloaded agents, uses structural search…
git:20261005.65b367f · audit A · 81 stars
explain SKILL.md skill
gkaria/vibe-learn · adapters/cursor/skills/explain/SKILL.md · Guided code tour of a file or subsystem this session touched — entry point, the load-bearing pieces, the edges, and…
git:20261017.a8c627f · audit A · 57 stars
explain SKILL.md skill
gkaria/vibe-learn · adapters/copilot-cli/skills/explain/SKILL.md · Guided code tour of a file or subsystem this session touched — entry point, the load-bearing pieces, the edges, and…
git:20261017.a8c627f · audit A · 57 stars
explain SKILL.md skill
jantichy/claude · skills/explain/SKILL.md · Skill se použije, když uživatel zadá "/explain" (volitelně s tím, co vysvětlit), nebo napíše, že nerozumí tomu, co mu…
git:20261105.fb301d4 · audit A · 52 stars
explain SKILL.md skill
anantys-oss/koan · koan/skills/core/explain/SKILL.md · Explain a PR's intent and changes in plain language (ex: /explain https://github.com/owner/repo/pull/42)
v1.0.0 · audit A · 50 stars

Browse by kind, by grade A, or by owner.