Teach the user a new skill or concept, within this workspace.
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
The user has asked you to teach them something. This is a stateful request - they intend to learn the topic over multiple sessions.
## Teaching Workspace
Treat the current directory as a teaching workspace. Workspace paths (`./lessons/` and the rest) resolve from the directory `/teach` was run in; only the `*-FORMAT.md` links resolve from this skill's folder. The state of their learning is captured in this directory in several files:
- `MISSION.md`: A document capturing the _reason_ the user is interested in the topic. This should be used to ground all teaching. Use the format in [MISSION-FORMAT.md](./MISSION-FORMAT.md).
- `./reference/*.html`: A directory of reference materials. These are the compressed learnings from the lessons - cheat sheets, reference algorithms, syntax, yoga poses, glossaries. They are the raw units of learning. They should be beautiful documents which print out well, and are designed for quick reference.
- `RESOURCES.md`: A list of resources which can be explored to ground your teaching in contextual knowledge, or to acquire knowledge and wisdom. Use the format in [RESOURCES-FORMAT.md](./RESOURCES-FORMAT.md).
…
The line at the top of this page pins the label git:20261012.178eb1e, 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.
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 (9760 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
shaderera/shaderera · 7 stars · license MIT · pushed 2026-10-31 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_ex3zwezrehprkxoo
GET https://markdownregistry.com/api/v1/resolve?ref=shaderera/shaderera/teach
GET https://markdownregistry.com/api/v1/blob/4270ba7c0b785313f549c5d470145b335846d5016c5a8cf9155fcbbbf10ae532
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.
shaderera/shaderera · .claude/skills/code-review/SKILL.md · Review the changes since a fixed point (commit, branch, tag, or merge-base) along two axes: Standards (does the code…
shaderera/shaderera · .claude/skills/codebase-design/SKILL.md · Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find…
shaderera/shaderera · .claude/skills/diagnosing-bugs/SKILL.md · Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports…
shaderera/shaderera · .claude/skills/domain-modeling/SKILL.md · Build and sharpen a project's domain model. Use when discussing codebase terminology, writing or editing a GLOSSARY.md…
shaderera/shaderera · .claude/skills/grill-with-docs/SKILL.md · A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
shaderera/shaderera · .claude/skills/grilling/SKILL.md · Grill the user relentlessly about a plan, decision, or idea. Use when the user wants to stress-test their thinking, or…
shaderera/shaderera · .claude/skills/improve-codebase-architecture/SKILL.md · Scan a codebase for deepening opportunities, present them as a visual HTML report, then grill through whichever one you…
cursor/plugins · pstack/skills/teach/SKILL.md · Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what…
cursor/plugins · harness/pstack/claude-code/skills/teach/SKILL.md · Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what…
nightly-labs/openbot · marketplace/production-catalog/bundles/pstack/skills/teach/SKILL.md · Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what…
michael-denyer/pstack-claude · plugins/pstack/skills/teach/SKILL.md · Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what…
backnotprop/pstack · skills/teach/SKILL.md · Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what…
bastani-inc/atomic · packages/workflows/skills/teach/SKILL.md · Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what…
