explain is agent-read markdown (skill) from greenfield-inc/pane: Use when the person wants to understand a concept or how something works today. Never plans..
Indexed from public GitHub and served as immutable, content-addressed versions. Install it pinned to an exact SHA-256 with the mdr CLI, and every file is verified before it reaches your agent: the main file against the SHA-256 recorded here, the others against the git hashes of its source commit. The deterministic audit below grades the latest version, and the same checks always give the same file the same grade.
What the file says
# Explain
Finish when the person could teach it back. Ideas for what to build belong in [`options`](../options/SKILL.md).
## Inline first
Answer small questions in the conversation. Offer an HTML explainer only when the concept is big enough that the person would want to come back to it or share it, or when they ask for one.
## Gather facts before teaching
Read the code yourself for small questions. For a larger trace, give a fresh-context subagent one question to answer with the `gather-evidence` skill, for example "how does a message travel from the API to the provider, with file references". Give the subagent just that question, and interpret what comes back yourself.
## The explainer
Render it with the [`page`](../page/SKILL.md) house standard. Save it under `explainers/` in the work's bundle and add it to the brief's "Related" list. With no brief yet, it gets a bundle of its own.
Sections, in order:
1. Title and a one-paragraph gist
2. How it works now, told as a story
3. One concrete walkthrough: a real request or record from start to finish
4. Diagrams: data flow, states, or sequence, whichever carries the idea
5. Glossary
6. Common misconceptions
…
Pin to a label to follow the author's releases, or to a sha256 for exact bytes. Either way the resolved hash is written to mdr.lock, and mdr install fetches those bytes again and checks them, so it installs them exactly or fails.
GET https://markdownregistry.com/api/v1/artifacts/art_gtbgpir5tnb6k2a4
GET https://markdownregistry.com/api/v1/resolve?ref=greenfield-inc/pane/explain
GET https://markdownregistry.com/api/v1/blob/1bd77d88b69ca0eb4c6bfbff42ab54dd3da35b3256c8e41c94c3ed6bf77fd2b6
Your agent 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.
greenfield-inc/pane · .claude/skills/commit/SKILL.md · Selectively stages and commits only the changes related to the current session, skipping unrelated modifications.
greenfield-inc/pane · .claude/skills/create-plan/SKILL.md · Creates a reconciled implementation plan by combining a structured plan draft with a normalized intent brief and a…
greenfield-inc/pane · .claude/skills/discussion/SKILL.md · Have an interactive discussion about a topic, approach, or feature. Researches the codebase as needed, talks through…
greenfield-inc/pane · .claude/skills/implement/SKILL.md · Executes an approved plan with one primary implementation stream by default, using bounded parallel sidecars only when…
greenfield-inc/pane · .claude/skills/investigate/SKILL.md · Investigates bugs through hypothesis-driven root cause analysis. Automatically invoked when the user reports a bug…
greenfield-inc/pane · .claude/skills/prepare-pr/SKILL.md · Commits changes grouped by done-plans, rebases main, runs build and quality gates, then creates or updates a PR…
greenfield-inc/pane · .claude/skills/research-web/SKILL.md · Conducts extensive web research on technical topics with validated references and citations. Use when you need external…
greenfield-inc/pane · .claude/skills/share-fix/SKILL.md · After shipping a non-trivial fix, find related GitHub issues across the ecosystem, draft helpful human-sounding…
greenfield-inc/pane · .claude/skills/simple-plan/SKILL.md · Quick gut-check before implementing when the user directly asks you to do something (e.g. "add X", "fix Y", "change…
greenfield-inc/pane · .codex/skills/codebase-explorer/SKILL.md · Explore the notetake codebase to locate files, trace behavior, and document existing patterns with precise file…
greenfield-inc/pane · .codex/skills/commit/SKILL.md · Selectively stages and commits only the changes related to the current session, skipping unrelated modifications.
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.
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…
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…
saadshahd/moo.md · hope/skills/explain/SKILL.md · Put one settled thing in the user's head, plainly. Use when the user does not hold something already settled.
thoughtbot/rails-consultant · skills/explain/SKILL.md · Explain what a piece of code does — a specific file, class, or method in close detail, or a user-facing flow as a…
marcel-bich/marcel-bich-claude-marketplace · plugins/credo/skills/explain/SKILL.md · Explain something in depth on request. Use when the user writes "???" - alone, or placed directly after a reference…
harnessprotocol/harness-kit · plugins/explain/skills/explain/SKILL.md · Use when user invokes /explain with a file path, directory path, function/class name, or natural language concept. Also…
