teach SKILL.md skillA

teach from shiwenbin1617/pstack is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.

Install it, pinned

mdr add shiwenbin1617/pstack/teach@git:20260827.f7b391a

Pins git:20260827.f7b391a in mdr.lock. Pin the fingerprint instead.

Audit grade: A, 17 of 17 checks passed
Kind: SKILL.md skill
Repository: shiwenbin1617/pstack
Path: skills/teach/SKILL.md
Versions recorded: 1
Latest version: git:20260827.f7b391a, committed Aug 27, 2026
Size: 6,253 bytes
Repository stars: 4
License: a license file GitHub does not identify

Explain a body of work plainly so a person actually understands it. Runs the `how` and `why` skills and weaves what they find into one clear explanation. Use for 'teach me this', 'help me really understand X', 'explain this change or subsystem to me'.

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

# Teach

**You explain what a thing is, how it works, and why it's built that way, in one plain account at the person's pace. The goal is that they understand it, not that you change anything.** For "teach me this", "help me really understand X", or "explain this change or subsystem to me".

Teach sits on top of `how` and `why`. Get your bearings on what the work is and what it touches, then run `how` for how it works and `why` for why it's that way. Those are real skill invocations that do their own digging. Blend what they find into one plain explanation, lead with what matters to the person, and go deeper when they ask. Reword freely for teaching, with one exception: keep `why`'s confidence language intact (its hedges are findings, not style). Let those skills do the investigation. Don't redo it by hand.

1. Decide the few things they should walk away understanding. Choose them from why they're asking (about to change it, reviewing it, debugging it, new to it) and what they already know, both read from the conversation, not quizzed out of them. Skip what they plainly already know. Put the depth where their question is.
…

Read the whole file at its exact version.

How to install

The exact contents, by fingerprint

mdr add shiwenbin1617/pstack/teach@sha256:0a5987b0588dc56e

The line at the top of this page pins the label git:20260827.f7b391a, 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](https://markdownregistry.com/badge/art_ytqrvqxi4h4rwyyg.svg)](https://markdownregistry.com/a/art_ytqrvqxi4h4rwyyg)

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

Versions

The registry has recorded 1 version of this file, committed on Aug 27, 2026.

version	committed	commit	size	audit
git:20260827.f7b391a latest	2026-08-27	f7b391a	6,253 B	A	view

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 (6253 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

shiwenbin1617/pstack · 4 stars · license a license file GitHub does not identify · pushed 2026-09-07 · branch main

API

GET https://markdownregistry.com/api/v1/artifacts/art_ytqrvqxi4h4rwyyg
GET https://markdownregistry.com/api/v1/resolve?ref=shiwenbin1617/pstack/teach
GET https://markdownregistry.com/api/v1/blob/0a5987b0588dc56e14bfd84d0300e2ab405abc7c5c2aa81e0d3d7c6b243db7a7

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 shiwenbin1617/pstack

AGENTS.md AGENTS.md file

shiwenbin1617/pstack · AGENTS.md

git:20260907.b1269d9 · audit A · 4 stars

setup-pstack SKILL.md skill

shiwenbin1617/pstack · adapters/claude-code/overrides/setup-pstack/SKILL.md · Configure which Claude Code models pstack uses per role. Use for /setup-pstack or requests to change pstack model…