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/pacing.md
View on GitHub# Pacing and routing
Loaded once per session, before Rung 1, after the target is known.
## Length
Length is set by the target, not by the rung. The ceilings below are
defaults for someone who wants to read a paper; shift them as the target
demands.
| Target | Rung 1 | Rungs 2, 5 | Each node turn (Rungs 3, 4) |
| --- | --- | --- | --- |
| Read one paper | 150-250 | 300-500 | 400-700 |
| Judge whether a method fits | 200-300 | 200-400 | 500-700, weighted to 4 |
| Do it hands-on | 100-200 | 200-300 | 500-700, weighted to 4 |
| Follow a talk | 100-200 | 300-400 | 200-400 |
Someone who wants to build the apparatus does not need the field's origin story
at length. Give them the one sentence that explains why the method exists, then
spend the session on the node turns. Compressing Rung 1 is not skipping it.
Do not compress a derivation into a summary to hit a number. If a rung or node
genuinely needs two turns, take two turns and say so at the break. The path's
length is part of the budget: three nodes for a talk, up to six for a paper or
a build.
### Route on the target
The target you collected in Step 0 sets the shape of every rung and every node
turn, and which nodes make the path. Use it:
- **Read one paper** -> weight notation and formalism. Keep Rung 2 dense and
symbol-heavy; the goal is to make the page parseable.
- **Judge whether a method fits their work** -> lead with phenomena and worked
numbers. Treat derivations as black boxes with stated properties, weight each
node turn toward Rung 4, what the method can and cannot deliver, and say
plainly where it is a poor fit. This target is a decision, so give them what a decision needs.
- **Do it hands-on** -> the Rung 4 half of each node turn becomes a procedure:
apparatus or pipeline, typical parameters, what breaks first. Compress Rung 5 to tooling and
communities.
- **Follow a talk** -> compress everything. Rung 2 and Rung 5 matter most;
node turns can stay at the level of what the central object means.
If the user gave no target, ask once, in the same control as the prerequisites.
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 |