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/anti-patterns.md

View on GitHub
# Anti-patterns

Read when reviewing your own output, or when unsure whether
a habit is helping. Each line is a way this skill has failed or could fail.

## Anti-patterns

- Running the intake on a question that one turn would have answered. This is
  the most common way to make the skill worse than no skill.
- Skipping Step 0 and guessing at their level when calibration would have
  changed the answer. Guessing wrong in the hard direction wastes the whole
  session; guessing wrong in the easy direction is patronizing.
- Asking "what's your background?" instead of naming the specific prerequisites.
  The user cannot audit a gap they cannot see.
- Printing the prerequisite checklist as plain text in an interface that has an
  interactive control, so the user has to type back what they could have tapped.
- Asking about explanation style or the map in the intake. Both have defaults
  the user can change at any time, and every extra question costs a turn's
  patience.
- Chaining several choice controls when one would hold the prerequisites and
  the target.
- Naming prerequisites from memory when a search for the field's structure was
  available.
- Treating “simple” as “remove the equations and use a childish analogy”, or
  treating “professional” as permission to leave field-specific notation
  unexplained.
- Dumping all five rungs in one response because the user seems smart.
- Analogies that are pleasant but wrong. If the analogy breaks, say exactly
  where. An analogy the user over-trusts is worse than no analogy.
- Skipping rung 1 because the motivation seems obvious. It is obvious to
  specialists, which is the whole problem.
- Hedging everything into mush, or the reverse: presenting a contested question
  as settled.
- Producing a reading list of plausible-sounding papers you have not checked,
  or attaching an identifier you did not retrieve.
- Asking a checkpoint question that needs a relationship the rung never stated.
  The user then fails a test of your writing and reads it as a test of their
  competence.
- Widening a marked anchor to cover an adjacent skill the user never claimed.
- Giving a hands-on learner the full origin story of the field at length when
  they asked how to build the thing.
- Teaching an unsettled field in the confident register of a settled one, so
  the reader cannot tell consensus from your reconstruction.
- Attaching a citation to every textbook sentence. Each citation slot is a
  chance to fabricate, so citations belong where they carry weight: the reading
  path, and the contested claims of an unsettled field.
- Taking a target artifact at the start and never returning to it.
- Planning rungs from nothing when the field has a textbook, a review, or a
  syllabus. The curriculum changes every session, and the reader cannot see
  what was left out.
- Building a map because a question looked large, in front of a one-turn
  answer, or in Decode mode.
- Ending as though the path were the whole field, instead of naming the nodes
  that were not taught and what each one is for.
- Printing a long map with a gloss on every node, or reprinting it every turn.
- Teaching several path nodes in one turn.
- Presenting a dependency you inferred as if the source stated it.
- Writing an equation without saying which convention it is in, so the user
  cannot match it against the paper in front of them.
- Deferring to a textbook instead of explaining. Recommend reading *after*
  teaching, not instead of it.
- Praising the question instead of answering it.
- Adding claims that are not in a supplied paper while presenting them as if
  they came from it.

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