当用户纠结要不要学某个东西、学到什么程度,或在做时间/精力/项目取舍时使用。用「简易策略」先逼问要解决的既定问题,检验现有知识能否搞定,评估知识贬值速度与 ROI,用「探索 vs 应用」判断该学新的还是用现有的,给出「学 / 不学 / 只学最小够用」的结论,避免囤积会贬值的知识。触发场景:要不要学 X、值不值得深入、学到什么程度够、时间不够该学啥、该深挖还是够用就行。
npx skills add https://github.com/Li-Evan/Bloom --skill learn-occam
> 核心信条:这世界最有价值的不是知识,是你的时间。 能用现有知识解决的就别学新的;以后要用的,以后再学。
用户在纠结"要不要学 X / 学到什么程度 / 精力往哪放"。这是"广度优先、兴趣队列过长"倾向的刹车。
逼问一句:你要解决的具体问题是什么? 没有具体问题、纯"感觉该学 / 别人都在学"→ 直接进"以后再学"队列,不占当下精力。理解知识的作用,重于知识本身。
问清用户已经会什么——能解决就别学新的。拿不准"是不是其实已经会了"就配合 learn-crossover。
这知识多久会贬值?(技术栈 / 工具往往 6–12 个月就明显更新)相对有限的时间值不值?贬值快 + 可外包给 AI / 随时查 → 只需"知道它存在、管什么",不必真学。
现在该"探索"(学新)还是"应用"(用现有)?探索成本越高 → 越该偏应用。只有目标够难、现有知识确实够不着时,简易策略才督促你学。
明确三选一:① 学(值得且现有搞不定)/ ② 不学(入"以后再学"队列)/ ③ 只学最小够用的那一块(点明是哪一小块)。要深挖就转 learn-graph 建路径。
> ⚠️ 铁律·只用确证的已会知识:判断用户「已经会什么」只能用他确证学过的知识(亲口确认或可靠背景);严禁把「正在讲的材料 / 文章作者背景 / 对话里别人的知识」当成用户会的。拿不准 → 直接问「⚠️ 你学过 ___ 吗?」,绝不替他假设。
learn-graph。learn-crossover(已会什么) learn-graph(系统建图) learn-prototype(动手迭代) learn-feynman(自查)。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/learn-occam 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.