Feynman explain
Break down any concept, system, code, or decision using the Feynman-technical hybrid formula — plain-language mechanism → evidence/numbers → actionable implication. Use whenever the user asks to explain, break down, simplify, or understand something. Trigger on "feynman this", "ELI5", "break this down", "help me understand", "explain like I'm five", "walk me through", "what does X actually mean", "why does X work", or any request to make something clearer. Also use proactively when explaining architecture decisions, engineering trade-offs, research findings, or anything where both accessibility and rigor matter. When in doubt, use this skill — clarity is never wrong.From its SKILL.md
npx -y skills add ming1in/skills --skill feynman-explainAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, as published. Nobody here has run it
Explain using the Feynman-technical hybrid formula:
- Mechanism — what physically or logically happens and why it matters, in plain language with analogy. Test: could someone outside the domain explain it back?
- Evidence — specific numbers, metrics, benchmarks, or sources. Skip this step honestly if nothing to quantify; don't manufacture precision.
- Implication — conclude with the decision, action, or next step this enables. Analysis without action is incomplete.
For multi-part subjects, run the formula per component rather than mixing them together.