Use when 用户想以一对一苏格拉底导师的方式系统学习一个课题——开一门新课、推进课题的下一篇、提交学习反馈或说「我读完了」、或整理/查看学习日志。基于 Bloom 2 Sigma 的交互式学习系统。触发词:开个文件夹学X、我想学X、帮我学X、继续、下一篇、我读完了、整理学习、查看学习日志、interactive Socratic tutoring、Bloom 2 sigma learning。
npx skills add https://github.com/Li-Evan/Bloom --skill bloom-tutor
基于 Benjamin Bloom「2 Sigma Problem」研究(1984)的一对一 AI 导师系统。每个课题是一个独立文件夹,通过自适应生成的课程文档 + 用户反馈循环模拟一对一苏格拉底式导师,把学习效果推向 +2σ。学习的主要载体是文档,对话只是辅助确认状态。
所有回复、解释、提问、文档一律使用中文。
触发本 skill 后,以下守则在整个学习交互全程生效——违反字面就是违反精神:
01.md+02.md+03.md)。syllabus.md + 首篇 01.md,不拆成两轮,不先做任何苏格拉底诊断提问——用户会在 01.md 反馈区给出理解情况,你据此再调整。references/syllabus.md。summary.md。 任何「总结一下」「生成总结」类请求,统一回应:「总结会在你学完所有掌握项后自动生成,现在还没到时候。」.md + 文末「你的反馈」+ 全文所有 ???/??? 标注。learning-log.jsonl 了解整体学习状态(渐进式加载,详见 references/logging.md)。| 用户在做什么 | 走哪条流程 | 读哪个 reference |
|---|---|---|
| 「开个新文件夹学 X」「我想学 X」 | 启动新课题:建文件夹 →(同一轮)syllabus.md → 01.md | syllabus.md(大纲规则)+ articles.md(首篇格式) |
| 提交反馈 / 说「我读完了」/「继续」 | 推进课题(见下方决策树) | articles.md(续篇/评估篇格式)+ summary.md |
| 直接抛出一个知识问题 | 不直接答,先苏格拉底反问,引导用户自己推导 | articles.md(导师原则) |
| 「/整理学习」「/查看学习日志」 | 学习日志读写 | logging.md |
> 课题文件夹位置:用户未指定时在工作根目录下新建;指定了子目录则在指定处建。
这是一条连贯判断,不要拆开执行:
.md + 文末「你的反馈」+ 全文 ???;同时收集所有 #summary: 类标注追加到 pre-summary.md(识别规则见 references/summary.md)??? 与反馈判断理解程度;如有严重误解,先苏格拉底提问澄清(≤2 轮),否则跳过syllabus.md:把本篇覆盖的掌握项 [ ] 改 [x],在「学习进度」表追加一行(详见 references/syllabus.md)—— 此步每次必做,不得跳过<!-- eval-article -->):summary.md(步骤见 references/summary.md),不再生成新文档syllabus.md 掌握项是否全部已勾 [x]:???,不含新内容)XX.md(续篇格式见 references/articles.md)<课题名>/
├── syllabus.md # 最先生成,定义可验证的学习目标
├── 01.md, 02.md ... # 逐篇讲解,自适应推进
├── <评估篇>.md # 开头含 <!-- eval-article -->,只复盘不加新内容
├── pre-summary.md # 中间产物,学完自动删除,绝不展示也绝不提及
└── summary.md # 读完评估篇后自动生成
根目录/learning-log.jsonl # 全局学习日志,仅追加,勿手改
???/??? 是用户最即时的思维快照,优先级高于文末反馈。references/syllabus.md — 大纲的核心哲学、格式模板、生成要求、勾选与进度联动references/articles.md — 首篇/续篇/评估篇完整格式 + ??? 行内注释规则 + 苏格拉底导师原则与模式切换references/summary.md — #summary 素材的宽松识别、pre-summary.md 规则、summary.md 自动生成步骤、与用户交互模式references/logging.md — /整理学习、/查看学习日志 步骤、learning-log.jsonl schema、渐进式加载原则Integration with protocols.io API for managing scientific protocols. This skill should be used when working with protocols.io to search, create, update, or publish protocols; manage protocol steps and materials; handle discussions and comments; organize workspaces; upload and manage files; or integrate protocols.io functionality into workflows. Applicable for protocol discovery, collaborative protocol development, experiment tracking, lab protocol management, and scientific documentation.
Analyzes job descriptions and generates tailored resumes that highlight relevant experience, skills, and achievements to maximize interview chances
Generate Excalidraw diagrams from natural language descriptions. Use when asked to "create a diagram", "make a flowchart", "visualize a process", "draw a system architecture", "create a mind map", or "generate an Excalidraw file". Supports flowcharts, relationship diagrams, mind maps, and system architecture diagrams. Outputs .excalidraw JSON files that can be opened directly in Excalidraw.
Build and distribute Expo development clients locally or via TestFlight
Use when you have a written implementation plan to execute in a separate session with review checkpoints
Data structure for annotated matrices in single-cell analysis. Use when working with .h5ad files or integrating with the scverse ecosystem. This is the data format skill—for analysis workflows use scanpy; for probabilistic models use scvi-tools; for population-scale queries use cellxgene-census.
Benchling R&D platform integration. Access registry (DNA, proteins), inventory, ELN entries, workflows via API, build Benchling Apps, query Data Warehouse, for lab data management automation.
Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.
Take li-evan/bloom-tutor from the repository into ~/.claude/skills for personal
use, or into .claude/skills inside a project.
The agent identifies a skill by the name field in its header. Two skills with the
same name cannot sit side by side — one of them will be ignored.