ljx-chase/research-field-onboarding / field-onboarding
field-onboarding
VerifiedGuide 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. Do not trigger for a one-line summary, a short overview request, or a direct factual answer; do not use it for translation, editing, search, debugging, or specialist questions inside the user's own field. Also trigger in other languages, including Chinese such as 入门, 一步一步讲, 看不懂, 这篇论文讲什么, 帮我理解这个领域.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 18.0 KB |
| agents/openai.yaml | config | 139 B |
| references/anti-patterns.md | markdown | 3.6 KB |
| references/checkpoints.md | markdown | 2.1 KB |
| references/citations.md | markdown | 1.5 KB |
| references/decode-mode.md | markdown | 1.2 KB |
| references/evals.md | markdown | 16.0 KB |
| references/examples.md | markdown | 11.9 KB |
| references/explanation-styles.md | markdown | 3.3 KB |
| references/field-map.md | markdown | 4.4 KB |
| references/pacing.md | markdown | 2.1 KB |
| references/search-recipes.md | markdown | 3.2 KB |
| references/state-runtime.md | markdown | 4.0 KB |
| references/unsettled-fields.md | markdown | 2.4 KB |
| scripts/knowledge_state.py | script | 22.8 KB |
references/unsettled-fields.md
View on GitHub# Fields that are not settled
Loaded when the calibration check in `SKILL.md` finds the field is emerging,
contested, or beyond what you can reliably describe.
## When the field is not settled
In an emerging or contested field there is no consensus to teach from, so the
usual standard, be correct, is not available. Use these instead.
- **Say it up front.** One line: no textbook exists, the vocabulary is not
standardized, this is what the last few years of papers look like.
- **Ground the substantive claims.** In a settled field, citing a source for a
textbook fact is noise. Here it is the only thing separating teaching from
invention. Attribute the central claims of Rungs 3 to 5 to specific work,
under the same verified / unverified labels as everywhere else, and mark
anything that is your own synthesis as your synthesis.
- **Flag unstable vocabulary.** Different groups routinely name the same object
differently before a field settles. Say when a term has competitors, and
which paper uses which. A reader who learns one group's word and then reads
another group's paper will think they have found a new concept.
- **Invert Rung 5.** There is no review to orient with. Give the two or three
groups pushing the area, what each is claiming, and where they disagree.
- **State your horizon.** Your picture of a fast-moving field ages badly. Say
when it is from, and say plainly that the last year may be missing.
Treat prerequisites the same way: in an emerging field your prerequisite list is
inferred from adjacent settled fields, not read off a curriculum. Present it as
provisional and say so.
## When you cannot onboard them
Sometimes the honest answer is that you cannot do this reliably. That is the
case when the field is too new or too narrow for you to have a real picture and
you have no way to search.
Do not fill the gap with plausible-sounding structure. Say what you can and
cannot do, then hand over a way to find the ground truth themselves:
- the search that would surface a review, written out so they can run it;
- the two or three venues or groups the work would appear in, if you know them;
- what to read the review for, which is the prerequisite list you could not
give them.
See [references/search-recipes.md](references/search-recipes.md) for query
templates. Sending someone to a real review beats onboarding them into a field
you have reconstructed.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| add-product-e2e-evalpaperclipai/paperclipAdd or extend a Paperclip full-stack runner E2E workflow, fixture, matcher, or report evidence path for local or Daytona execution. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| diagnose-why-work-stoppedpaperclipai/paperclipCompatibility entry point for failed, stalled, looping, or over-recovered Paperclip work. Use fix-failed-paperclip-run for the full diagnosis, regression, repair, real verification, and green-PR workflow; honor an explicitly requested diagnosis-only scope. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |
| fix-failed-paperclip-runpaperclipai/paperclipDiagnose and fix failed, stuck, slow, or incorrectly blocked Paperclip tasks and runs. Use with a task/run URL or failure report to trace the root cause, prove a regression red then green, check second-order effects, verify the real workflow, and deliver a PR with passing checks. | Stars: 115k | Updated | Claude CodeCodex | Verified | Install |