AI Agent Hub
Back to skills
Feynman Learning Guide icon

Feynman Learning Guide

Education Updated 2026.08.30

Paste the following prompt into your AI chat to install this skill:

Please follow https://skillhub.cn/install/skillhub.md and install @user_52a81e7a/feynman-tech.

About this skill

Problem

Passive reading often creates the illusion of understanding, but the knowledge fades quickly. The missing piece is a feedback loop that exposes where the explanation breaks down. This skill turns a topic into a few core concepts and asks the user to explain them while the AI probes for gaps.

How It Works

The skill follows a closed-loop process:

  • Concept: Extract 3–5 core concepts from the topic and order them by dependency.
  • Teach: The AI acts as a curious beginner and asks at most 2 questions per round, avoiding answers and flagging unexplained jargon or logical jumps.
  • Review: Rate each explanation as STRONG, WEAK, or WRONG, then patch gaps or correct misunderstandings.
  • Simplify: Add 1–2 analogies per concept, including similarities, limits, and where the analogy can mislead.
  • Loop-back check: The user retells the whole topic without prompts; any stuck concept returns to teaching and review until it becomes clear.

Caveats

This is best for self-checking technical concepts, paper takeaways, or system design rationale. It is not a summarization tool; it requires active explanation from the user. If the goal is only to receive answers, the value is limited.

Use Cases

  • Review a paper and turn attention mechanisms into three explainable concepts.
  • Adopt a payment system and explain clearing/reconciliation to an AI novice to locate gaps.
  • Prepare an internal talk and break design-pattern composition rules into probeable concepts.
  • Learn Rust ownership and explain lifetimes and borrowing with limited analogies.

Best For

  • Engineer taking over unfamiliar services and needing to explain dependencies, messaging, and state machines clearly
  • Interview candidate preparing system design answers that survive three levels of follow-up
  • Tech lead onboarding new hires and needing to turn architecture decisions into a checkable explanation
  • Developer learning concurrency who wants probing questions that expose understanding limits