跳至正文
OpenAgentSkill
浏览已开放 · 目录记录日期 2026-11-21 · 自动更新和账户服务暂时关闭。
搜索与研究

field-onboarding

Guide a researcher step by step into an unfamiliar research field, or decode a paper, abstract, figure caption, or referee comment they cannot parse. Builds understanding in rungs (motivation, vocabulary, core framework, methods, frontier), anchored to what the user already knows, with a checkpoint before each advance. Use when the user says they are new to a field, asks what a research area or method is, says an explanation was too technical, asks to be walked through something step by step, asks for a reading path, or supplies dense research text. Trigger even when the user only names an unfamiliar field or pastes an abstract without asking to be taught. Also trigger in other languages, including Chinese such as 入门, 一步一步讲, 看不懂, 这篇论文讲什么, 帮我理解这个领域. Do not use for narrow factual questions, for a specialist asking inside their own field, when the user asked for a short answer, or when the task is translation, editing, search, or debugging.

ljx-chase · 已有静态检查记录

安装与使用

运行命令前先阅读来源与依赖说明。复制命令不会自动安装或执行。

npx skills add ljx-chase/research-field-onboarding --skill field-onboarding

技能说明


name: field-onboarding description: Guide a researcher step by step into an unfamiliar research field, or decode a paper, abstract, figure caption, or referee comment they cannot parse. Builds understanding in rungs (motivation, vocabulary, core framework, methods, frontier), anchored to what the user already knows, with a checkpoint before each advance. Use when the user says they are new to a field, asks what a research area or method is, says an explanation was too technical, asks to be walked through something step by step, asks for a reading path, or supplies dense research text. Trigger even when the user only names an unfamiliar field or pastes an abstract without asking to be taught. Also trigger in other languages, including Chinese such as 入门, 一步一步讲, 看不懂, 这篇论文讲什么, 帮我理解这个领域. Do not use for narrow factual questions, for a specialist asking inside their own field, when the user asked for a short answer, or when the task is translation, editing, search, or debugging.

Field Onboarding

Get someone productively oriented in an unfamiliar research field, fast, without losing them.

The failure this skill exists to prevent: answering a beginner's question at the level of a specialist, so the answer is technically correct and completely useless.## When not to use this skill

This is a teaching mode, not a default. Running the full ladder on someone who wanted one sentence is its own failure, and a more irritating one than pitching too high. Do not run Step 0 or the ladder when:

  • The question is narrow and factual. "What does PL stand for?" "What wavelength do people usually pump at?" Answer it. Do not calibrate.
  • The user is already a specialist in this exact area and is asking a specific technical question inside it.
  • The user asked for it short. "quickly", "one line", "just tell me", "TL;DR", "简单说", "赶时间".
  • The task is not understanding. Translation, proofreading, formatting, debugging, writing, or a literature search with a known target.
  • The user is mid-task and blocked. Someone whose fit is failing at 2am needs the fix, not motivation and vocabulary.
  • The user already declined the ladder this session. Offer once. Never twice.

The one-turn test. Before starting Step 0, ask whether the question can be answered well in a single turn. If it can, answer it, then offer the ladder in one line: "that is the short answer; if you want to actually work in this area, I can walk you up from the motivation." Offer once, drop it if unclaimed.

When in doubt, answer first and offer second. A good answer followed by an offer costs the user nothing. An intake questionnaire in front of a one-line question costs them a turn and their patience.

Core rules

  1. One rung per turn. Never deliver the whole ladder at once. Stop, check, advance. If the user asks for the whole ladder, a compact overview, or a specific rung, honor that immediately.
  2. No unexplained jargon. Every term gets defined on first use, in one clause, inline. If a sentence needs three undefined terms, it is the wrong sentence.
  3. Anchor to what they know. Explain the new field in terms of the user's existing expertise. Map new concept onto familiar concept, then immediately say where the mapping breaks.
  4. Be explicit about confidence. Mark what is settled, what is contested, and what you are unsure of. Do not flatten real disagreement in the literature, and do not dress a strong consensus up as an open question. "Some argue X, others Y" with no indication of where the weight of evidence sits is not balance, it is abdication.
  5. Search before teaching. If the field is fast-moving, or the user names a specific paper, method, material, dataset, or software package, search first. Do not teach a five-year-old snapshot as current.
  6. State your conventions. Where a field uses competing sign, phase, unit, or normalization conventions, say which one you are using and name the alternative the literature also uses. A reader who cannot map your equation onto the paper's equation has not been onboarded. This costs one clause and prevents the single most common silent failure in physical-science reading.
  7. Never invent a reference. Every named work is either verified in this session or explicitly marked unverified. See "Naming literature".
  8. Match the user's language. Reply in whatever language they wrote in.
  9. Preserve the source when decoding. Keep what the source claims separate from background, inference, and your own critique.

Step 0 — Locate them (one short turn)

Do not start teaching until this is done. Answering before you know what they already have is the failure this skill exists to prevent.

First, name the prerequisites yourself. Work out which 3–5 upstream frameworks the topic actually rests on, and list them explicitly. Do not ask a vague "what's your background" — the user cannot answer that usefully, and it puts the work of scoping on the person who by definition does not know the scope yet.

Then ask them to mark each one:

  • used it — has applied it in their own work
  • learned it — saw it in a course, could follow a derivation, has not used it
  • new — no real contact

Present this as a short checklist, one line per prerequisite, with a one-clause gloss so they can tell what each item means. Render it with an interactive checklist or multi-select control whenever the interface has one. Fall back to a plain table only when it does not. Printing marks the user has to type back when they could have tapped them is a cost you imposed for nothing, and it is the most common way this step gets half-done.

Second, check how settled the field is. Do this before you teach, because it decides which mode you are in. Search if you can. If you cannot search, say so and reason from what you have, out loud.

  • Settled. Textbooks and review articles exist, the vocabul
阅读完整来源 ↗