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/search-recipes.md
View on GitHub# Search recipes
Use these when you need to verify a reference, check how settled a field is, or
hand the reader a way to find ground truth you could not give them.
Two rules govern everything here. If you can search, search, and label what you
found as verified. If you cannot, give the reader the query itself rather than a
citation you have not checked. A query they can run is worth more than a
citation they cannot trust.
## Is there a review?
This is the first question in an unfamiliar field, and the answer decides
whether you are teaching consensus or reconstructing it.
- OpenAlex, reviews only, most cited first:
`https://api.openalex.org/works?filter=title_and_abstract.search:<TOPIC>,type:review&sort=cited_by_count:desc&per-page=10`
- Plain search, for a human rather than an API:
`<TOPIC> review` or `<TOPIC> tutorial` on Google Scholar, sorted by citations
- Annual Reviews, Reviews of Modern Physics, Chemical Reviews, and Physics
Reports are worth checking by name in the physical sciences; a hit there
usually means the field is settled enough to have a canonical account
If nothing comes back, that is itself the finding: say the field has no review
yet and switch to the unsettled-field mode in `SKILL.md`.
## How current is my picture?
- Recent work only:
`https://api.openalex.org/works?filter=title_and_abstract.search:<TOPIC>,from_publication_date:<YYYY-MM-DD>&sort=publication_date:desc`
- arXiv, newest first:
`https://arxiv.org/list/<ARCHIVE>/recent`, or
`https://export.arxiv.org/api/query?search_query=all:<TOPIC>&sortBy=submittedDate&sortOrder=descending&max_results=20`
Compare what comes back against the account you were about to give. If the
recent work uses vocabulary you did not plan to teach, your picture is stale and
you should say so.
## Does this specific paper exist?
Never assert a title, author list, or year you have not checked, and never
attach a DOI or arXiv ID you did not retrieve.
- By DOI: `https://api.crossref.org/works/<DOI>`
- By title: `https://api.openalex.org/works?filter=title.search:<EXACT TITLE>`
- By arXiv ID: `https://export.arxiv.org/api/query?id_list=<ID>`
A miss means one of two things, and you should say which you believe: the work
does not exist, or it exists outside the index. Do not quietly keep the citation
either way.
## Who is working on this now?
Useful when there is no review and Rung 5 has to be built from groups rather
than from a canonical account.
- Most cited recent work in the area:
`https://api.openalex.org/works?filter=title_and_abstract.search:<TOPIC>,from_publication_date:<YYYY>-01-01&sort=cited_by_count:desc`
- Then read off the recurring last authors and affiliations rather than guessing
at them
## Handing the query to the reader
When you cannot search, write the query out in a form they can paste, and say
what to do with the result. For example: run the review query above; if it
returns something from the last five years with a few hundred citations, read
its introduction and section headings, and that will give you the prerequisite
list this session could not.
OpenAlex, Crossref, and the arXiv API are all open and need no key, so a reader
can run any of these in a browser.
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 |