explain SKILL.md skillA
This file is byte-identical to the first copy the registry indexed. Same content hash, so the same checks give both the same grade.
explain from greenfield-inc/pane is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add greenfield-inc/pane/explain@git:20260924.17234b5Pins git:20260924.17234b5 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- A, 17 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- greenfield-inc/pane
- Path
main/src/services/paneChatBundle/skills/explain/SKILL.md- Versions recorded
- 1
- Latest version
- git:20260924.17234b5, committed Sep 24, 2026
- Size
- 1,977 bytes
- Repository stars
- 644
- License
- a license file GitHub does not identify
Use when the person wants to understand a concept or how something works today. Never plans.
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 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 …
Read the whole file at its exact version.
How to install
claude plugin marketplace add https://markdownregistry.com/mp/a/art_gtbgpir5tnb6k2a4/1bd77d88b69ca0eb4c6bfbff42ab54dd3da35b3256c8e41c94c3ed6bf77fd2b6.json
Then /plugin install explain@markdownregistry-gtbgpir5tnb6k2a4 in Claude Code. It installs git:20260924.17234b5, the one graded A here, pinned to the commit it was graded at, and leaves it there.
mdr add greenfield-inc/pane/explain@sha256:1bd77d88b69ca0ebThe line at the top of this page pins the label git:20260924.17234b5, 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_gtbgpir5tnb6k2a4)
5 badge image fetches in 30 days. What the badge shows.
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it: what changed in greenfield-inc/pane/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 1 version of this file, committed on Sep 24, 2026.
Watch this file (sign in, one email per new version)
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.
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.
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.
Installed this file, say at .claude/skills/explain/SKILL.md? Drop it here to learn which saved version you have and what changed since. Your browser works out its SHA-256 fingerprint and sends only that; the file itself never leaves your computer.
Or paste its contents
Your agent can run this same check on the agent markdown files you have installed, up to 50 in one ask. Add the registry once:
claude mcp add --transport http markdownregistry https://markdownregistry.com/mcp/registry
Then ask it to check the files you have installed. No key and no account.
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
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (1977 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
greenfield-inc/pane · 644 stars · license a license file GitHub does not identify · pushed 2026-11-16 · branch main
API
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 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 greenfield-inc/pane
Every file in greenfield-inc/pane