agentsclimarketplace

Learn deep

Skill Li-Evan/Bloom/skills/learn-deep

用户学任何新概念/新技术/新理论的默认深度入口——一次性用五个视角把概念讲透并帮他选深入方向:crossover 用已会的撬动、occam 框定该学多深、graph 建知识地图、prototype 最小原型迭代、feynman 拷问检验。触发场景:我想学 X、理解 X、X 是什么、讲讲 X、搞懂 X、学一下 X、深入 X、给我讲讲 X。除非用户明确只要某一个视角(那时改用对应的单个 learn-* skill)。From its SKILL.md

Install
npx -y skills add Li-Evan/Bloom --skill learn-deep

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

SKILL.md

3.6 KB, ~1.3k tokens by cl100k_base, as published. Nobody here has run it

深度学习一个概念(learn-deep)

learn-crossover / learn-occam / learn-graph / learn-prototype / learn-feynman 五个视角编排成一遍全景,给用户学任何概念的"一次扫透 + 选方向"。

何时用

用户说"想学 / 理解 / 搞懂 / 讲讲一个概念 X"时——这是默认入口,一次跑完五视角,用户再选深入哪个。 例外:用户明确只要某一个角度("用跨界讲""帮我建图谱""考考我")→ 直接用对应的单个 learn-* skill,别全跑。

开跑前

先问清用户的背景:学过哪些相关领域、做过什么、熟悉哪些工具 / 理论。后面 crossover / occam / graph 都要用到。只采纳用户亲口确认学过的。

五视角执行顺序(这个弧线最顺:先降门槛 → 定深度 → 给地图 → 动手 → 验收)

1️⃣ crossover — 先用"你已经会一半"降门槛

抓住 X 的本质结构(剥术语),按三猜想给 🎁其实已学过 / 🔗结构同构(字段级对应表)/ 🧩可用已有知识解释,点出元知识。先激发信心,再谈深入。

2️⃣ occam — 框定"该学多深"

定位"既定问题"(学 X 解决什么)、现有知识够不够、X 的贬值速度与 ROI,给"够用就停 / 只学最小那块 / 值得深挖"的深度边界。不是劝退,是防止一上来过度钻。

3️⃣ graph — 给一张地图,知道 X 在哪、学到哪算够

X 在所属领域的知识图谱骨架(概念/用途/父子节点),标复用价值最高的节点 + 从常识能入门的点,给学习路径。引导用户补节点(自己建图才学得到)。

4️⃣ prototype — 给最小原型起点,把动手的球递给用户

给"最垃圾但能跑的原型"起点 + 引导式提问(让用户自己洞察缺陷),预告会撞到的坑。不替他做。

5️⃣ feynman — 抛 2–4 个直击盲点的问题验收

让用户用自己的话答,答不顺处 = 没真懂的洞。最后一个问题尽量打在 X 的根本局限上(真懂的试金石)。

6️⃣ 收尾:选方向

明确推荐往哪 1–2 个方向深入(综合 occam 的 ROI 判断 + 用户的目标 + 哪个视角最戳中他),并指出对应该接哪个单 skill(要动手→learn-prototype,要验收→learn-feynman)。

注意

⚠️ 铁律·只用确证的已会知识:判断用户「已经会什么」只能用他确证学过的知识(亲口确认或可靠背景);严禁把「正在讲的材料 / 文章作者背景 / 对话里别人的知识」当成用户会的。拿不准 → 直接问「⚠️ 你学过 ___ 吗?」,绝不替他假设。

  • 五视角各有侧重、严禁重复:crossover 撬动 / occam 只谈该学多深 / graph 只给地图 / prototype 只给动手路径 / feynman 只拷问。同一段内容不要讲五遍。
  • 每个视角精炼——这是"全景扫一遍",深入留给用户选完之后。宁短勿灌。
  • 单视角细分入口(用户只要一个时用):learn-crossover learn-occam learn-graph learn-prototype learn-feynman

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most learn study skills give in ~1.3k tokens

Counted across 545 of the 593 authors here whose files we hold, read 2026-09-06

  • Treat the current directory as a teaching workspacein 20 of 545, across 17 files
  • Teach knowledge first then practice skillsin 19 of 545, across 16 files
  • Design lessons which build long-term retentionin 15 of 545, across 12 files
  • Save each lesson as a self-contained HTML filein 15 of 545, across 12 files
  • Question the user on why they want to learn thisin 15 of 545, across 12 files
  • Reuse components from the assets directoryin 14 of 545, across 11 files
  • Never trust your parametric knowledgein 13 of 545, across 10 files
  • Record user preferences in NOTES.mdin 11 of 545, across 8 files
  • Ground all teaching in the MISSION.md documentin 11 of 545, across 8 files
  • Save each lesson to the lessons directoryin 8 of 545
  • Question the user if the mission is unclearin 7 of 545
  • Gather primary sources onlyin 7 of 545, across 4 files

Said here and by no other author read

  • ask the user what background knowledge they have
  • Run all five perspectives in order
  • Use only confirmed known knowledge
  • Keep each perspective concise
  • Recommend one to two deep directions at the end

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.