diff --git a/SOURCES.md b/SOURCES.md
index 626694c..0f8eaa6 100644
--- a/SOURCES.md
+++ b/SOURCES.md
@@ -379,16 +379,17 @@ and sequential numbering. Discovery and invocation settings remain unchanged.
   [bro](https://github.com/cursor/plugins/blob/main/pstack/skills/bro/SKILL.md),
   [teach](https://github.com/cursor/plugins/blob/main/pstack/skills/teach/SKILL.md),
   and [in-your-own-words](https://github.com/cursor/plugins/blob/main/pstack/skills/in-your-own-words/SKILL.md),
-  checked 2026-11-01. Independently written, user-invoked only in both hosts. Technical
-  explanations using "explain it to a PM or junior engineer" as the instruction.
-  Adds brief teaching guidance. No upstream prose copied.
+  checked 2026-11-01. Independently written, user-invoked only in both hosts. No
+  upstream prose copied.
 
 ## eli5
 
 - [anthropics/claude-plugins-community / eli5/skills/eli5](https://github.com/anthropics/claude-plugins-community/tree/f4c9452f5ca091f1be7064d9faab1b001ea21645/eli5/skills/eli5) — commit `f4c9452f5ca091f1be7064d9faab1b001ea21645`.
 
-Aims at a smart adult new to the topic and keeps the logic while simplifying the
-vocabulary. The description lists triggers only.
+Keeps the HTML page of big pictures and few words, and the topic argument. Takes
+its audience and depth from `explain` instead of "someone who knows nothing", and
+shows the page through `show-me` instead of naming an HTML artifact. The
+description lists triggers only.
 
 ## gauntlet-loop
 
diff --git a/skills/eli5/SKILL.md b/skills/eli5/SKILL.md
index 37cc4cc..dea9123 100644
--- a/skills/eli5/SKILL.md
+++ b/skills/eli5/SKILL.md
@@ -7,8 +7,9 @@ description: Use when the user types /eli5 <topic>, asks to explain something li
 
 <!-- Modified by SreeStack. -->
 
-Explain this topic to a smart adult who is new to it, using an HTML artifact that leads with big pictures and uses few words.
+Do [Explain](../explain/SKILL.md) as an HTML page that leads with big pictures and
+few words. Make the pictures teach the mechanism. Keep Explain's depth.
 
-Show how it actually works. Simplify the vocabulary, not the logic. Give the real term for each idea once.
+Put the page in front of the user with [Show Me](../show-me/SKILL.md).
 
 Topic: $ARGUMENTS
diff --git a/skills/explain/SKILL.md b/skills/explain/SKILL.md
index a43fb4a..5c2f652 100644
--- a/skills/explain/SKILL.md
+++ b/skills/explain/SKILL.md
@@ -6,7 +6,15 @@ disable-model-invocation: true
 
 # Explain
 
-Explain the requested topic, or your last answer, as if explaining it to a PM
-or junior engineer. Explain what it is and how it works.
-Use a concrete example when helpful. Keep it short, plain, and accurate about
-what's known.
+Explain the requested topic, your last answer, or the item the user points to,
+for a capable person who lacks this context, like a PM or junior engineer. Keep
+the technical substance. Use everyday words, and give each real term once.
+
+Say what it is and how it actually works. When they apply, include how it runs or
+gets triggered, where it lives, and what happens when something fails. Connect it
+to what the user already knows from the conversation. When an idea is abstract,
+give one concrete example from their case. When there is a choice, give the
+tradeoff.
+
+Keep it short. Separate what you know from what you infer. When you don't know how
+two things connect, say so instead of inventing a link to make it simpler.