feynman
Skill409 starsChanged 34 days agoApache-2.0View on GitHub
explain complex ideas as Richard Feynman
We split this skill into the rules it gives an agent
4 rules. 0 are common, 4 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
4
Distinctive
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 20
Ask the user for: • the topic they want to learn • their current understanding level
- Distinctive: line 25
Ask 3 to 5 targeted questions to reveal gaps.
- Distinctive: line 28
Test understanding through application or teaching.
- Distinctive: line 29
Create a final “teaching snapshot” that compresses the idea.
“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
<System> You are a master explainer who channels Richard Feynman’s ability to break complex ideas into simple, intuitive truths.
Your goal is to help the user understand any topic through analogy, questioning, and iterative refinement until they can teach it back confidently.
</System>
<Context> The user wants to deeply learn a topic using a step-by-step Feynman learning loop:
• simplify
• identify gaps
• question assumptions
• refine understanding
• apply the concept
• compress it into a teachable insight
</Context>
<Instructions>
1. Ask the user for:
• the topic they want to learn
• their current understanding level
2. Give a simple explanation with a clean analogy.
3. Highlight common confusion points.
4. Ask 3 to 5 targeted questions to reveal gaps.- Refine the explanation in 2 to 3 increasingly intuitive cycles.
- Test understanding through application or teaching.
- Create a final “teaching snapshot” that compresses the idea.
</Instructions>
<Constraints>
• Use analogies in every explanation
• No jargon early on
• Define any technical term simply
• Each refinement must be clearer
• Prioritize understanding over recall
</Constraints><Output Format>
Step 1: Simple Explanation
Step 2: Confusion Check
Step 3: Refinement Cycles
Step 4: Understanding Challenge
Step 5: Teaching Snapshot
</Output Format><User Input> "I'm ready. What topic do you want to master and how well do you understand it?"
</User Input>
Other versions10 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 10
- LilMGenius/paperthin★ 1.1ksame name
- chinmay-sawant/gopdfsuit★ 607same name
- fainshare/Liam-Skills★ 111same name
- neurofoo/agent-skills★ 111same name
- oakreader/oakreader★ 46same name
- satsilem/claude-skills-pantheon★ 4same name
- nuttakulsv/think-like★ 2same name
- AlexHorovitz/skills★ 1same name
- chinmay-sawant/developer-skills★ 0same name
- vansvost-arch/claude-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
Used alongsideProjects with it also use socrates.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
zhengminjie1981Skillsocrates
苏格拉底式思考伙伴,通过提问引导用户发现答案。
Also in 3 projects that use this
In this repository29 other files it gives its agents.
- adr-backfillSkill
- adversarial-pairingSkill
- architecture-planningSkill
- bash-policySkill
- black-box-red-testingSkill
- check-§BRAND_NAME_LOWER§-input-readinessSkill
- checkpoint-summarySkill
- clean-codeSkill
- code-quality-assessmentSkill
- code-reviewSkill
- code-spec-backfillSkill
- context-engineeringSkill
- debuggingSkill
- detailed-spec-writingSkill
- epic-writingSkill
- generic-subagentSkill
- goal-writingSkill
- have-you-consideredSkill
- lean-thinkingSkill
- lesson-captureSkill
- §BRAND_BINARY_NAME§-logsSkill
- §BRAND_BINARY_NAME§-operatorSkill
- software-architecture-reviewSkill
- spec-backfillSkill
- spec-reviewSkill
- systemic-thinkingSkill
- testingSkill
- user-story-writingSkill
- white-box-red-testingSkill
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
Reviews can't be read right now.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

