Skip to content

ljx-chase/research-field-onboarding / field-onboarding

field-onboarding

Verified

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. 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 入门, 一步一步讲, 看不懂, 这篇论文讲什么, 帮我理解这个领域.

references/checkpoints.md

View on GitHub
# Checkpoints

Loaded before the first checkpoint of a session.

## Checkpoints

**Scope the check to what you just taught.** The question must be answerable
from the rung the user has just read, plus the anchors they explicitly marked.
If answering requires a quantitative relationship, a scaling law, or a
sub-skill you have not stated, it is not a diagnostic, it is a trap. Teach the
scaling first, or ask a different question. A wrong answer should reveal a hole
in your explanation, not a hole in their background.

Two tests before you ask it. Can you point to the sentence in the rung that
contains the answer? Would someone who marked exactly the prerequisites this
user marked, and nothing more, be able to answer? If either is no, rewrite the
question.

At the end of each rung and each node turn, do not just ask "make sense?" That
always gets a yes.
Instead pick one:

- Ask them to predict something: "what happens to the signal if X doubles?"
- Ask them to restate the core idea in their own words.
- Give a two-question multiple-choice check on the rung just covered. Render it
  by actually calling a structured quiz or user-input tool when one is callable;
  otherwise accept a single letter or number.
- Ask them to spot which of two statements is the field's actual claim.

Make the session's last checkpoint test structure rather than recall: which
node depends on which, or why one node had to come before another. See
`field-map.md`.

Then branch:

- **Solid** -> mark the node `checked` and advance.
- **Shaky** -> mark it `shaky` and re-explain from a different angle, not
  louder. Change the analogy, drop a level of abstraction, or work a concrete
  number. It stays `shaky` until a later check passes, and its dependents wait.
- **Bored / already knew it** -> skip ahead. Ask which node or rung they want.

If the user skips the check and just says "continue", do not re-ask. Mark the
node `taught` and advance, but fold the diagnostic into the opening of the next
turn and lower your assumed level by one notch.

The user can always say "skip to rung N" or "just give me the whole ladder".
Honor that immediately.

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: 115kUpdated Claude CodeCodexVerifiedInstall
add-runner-evalpaperclipai/paperclipAdd or extend a Paperclip Runner protocol evaluation definition, roster, assertion, or report fixture with provenance and narrow validation.Stars: 115kUpdated Claude CodeCodexVerifiedInstall
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: 115kUpdated Claude CodeCodexVerifiedInstall
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: 115kUpdated Claude CodeCodexVerifiedInstall