shipshitdev/skills

teach

Explain a body of work so a person actually understands it. Runs how and why and weaves what they find into one plain explanation, built up diagram by diagram. Use for teach me this, help me really understand X, or explain this change or subsystem.

Installation

$ npx skills add shipshitdev/skills --skill teach

Similar popular skills

Related neighbors and high-traction skills in the same topics — useful to compare before installing.

Also in this package

Other skills from shipshitdev/skills · top by installs.

npx skills add shipshitdev/skills

Browse all from shipshitdev/skills

More details

Agent compatibility

Declared targets from SKILL.md / docs. Unmarked agents are not listed — the skill may still install via the CLI.

Claude Code Not declared
Cursor Not declared
Codex Not declared
GitHub Copilot Not declared
Windsurf Not declared
Gemini CLI Not declared
Cline Not declared
OpenCode Not declared

Repository health

Stars 35
License MIT
Default branch master
Open issues 1
Status Active

Skill metadata

Parsed from SKILL.md frontmatter.

Version1.2.0
LicenseMIT
More metadata
portable_source
https://github.com/ericlitman/open-pstack
portable_commit
56bfd14418fa733e34d98f714f357d28788470e3
version
1.2.0
tags
teaching, explanation, onboarding
author
Ship Shit Dev
source
https://github.com/cursor/plugins/blob/main/pstack/skills/teach/SKILL.md
upstream_repo
cursor/plugins
upstream_ref
main
upstream_commit
bdf7aa355337
last_synced
2026-09-05
license
MIT

Package contents

Files included with this skill beyond the listing page.

  • skill md SKILL.md 2,996 B
  • docs README.md 1,520 B
  • docs SUMMARY.md 261 B

History

  1. First recorded snapshot · 7 installs

SKILL.md

Teach

Explain what a thing is, how it works, and why it is built that way, in one plain account at the person's pace. Change nothing.

Authorized Scope

Apply this engine only within the user's requested task and existing explicit authorization. Loading or delegating to it grants no additional authority. Preserve report-only restrictions and the caller's target, host, provider, and cost limits. Existing approval satisfies a gate only for the same actions and scope; obtain approval before expanding them. Forward these limits to delegates.

Contract

Inputs:

  • A change, subsystem, or concept the person wants to understand

Outputs:

  • The explanation itself, never a report about what you delivered

Creates/Modifies:

  • None

External Side Effects:

  • None beyond the read-only work how and why do

Confirmation Required:

  • None

Delegates To:

  • how and why for investigation. Do not redo their digging.

Steps

  1. Decide the few things they should walk away understanding, from why

they are asking and what they already know. Do not quiz them.

  1. Let how and why do the work. Run them in parallel when both

matter. Keep why narrow by default. Keep why's confidence language intact.

  1. Start with a plain definition. Then tie it to the case in front of

you. Give the smallest complete answer first, a sentence or two, then stop. Add layers when they ask.

  1. Keep it a conversation. No quizzes. No pacing theater. No

"the key insight" labels.

  1. Show, don't only tell. For three or more moving parts, draw a short

series of diagrams that each add one part. Mermaid for flows. Skip a figure that only decorates.

Apply references/prose-slop.md from the selected deslop skill directory. Give each concept one name and keep it.

Reply: the explanation. Lead with the main point, then what it is, how it works, and why.

Teach procedure

Read [teach procedure](references/teach-procedure.md) when running this workflow. Apply the authorized scope and mode of this entry point to every step. Resolve other skills through this distribution’s active catalog; resolve resources relative to the installed skill directory.