research-survey-loop
Skill54 starsChanged 5 months agoMITView on GitHub
Long-running survey workflow for robotics, embodied AI, computer vision, world models, navigation, manipulation, 3D scene understanding, and adjacent research. Use when Codex needs to create or continue a multi-round literature review task, maintain stable task documents (`task.md`, `round_log.md`, `current_task.md`, `survey.md`), search Nature/Science plus top CV and robotics venues before arXiv, migrate relevant local PDFs from `papers/` into task-local `sources/`, read PDFs in chunks of at most 10 pages, and incrementally write a Chinese Markdown survey with relative local citations or web links.
In this repository27 other files it gives its agents.
- alphaxivSkill
- arxivSkill
- doc-coauthoringSkill
- docxSkill
- drawio-diagramSkill
- figure-descriptionSkill
- formula-derivationSkill
- grant-proposalSkill
- mmx-cliSkill
- mock-reviewSkill
- novelty-checkSkill
- paper-readingSkill
- pdfSkill
- phd-benchmark-paper-templateSkill
- phd-figure-designerSkill
- phd-idea-evaluatorSkill
- phd-intro-drafterSkill
- phd-pre-submission-reviewerSkill
- phd-tech-paper-templateSkill
- phd-vibe-research-workflowSkill
- pptxSkill
- proof-writerSkill
- research-litSkill
- research-wikiSkill
- theme-factorySkill
- update-source-mapSkill
- xlsxSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
36 rules. About 0 are common, 24 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈24
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use this skill for long-running survey work with a primary focus on robotics, embodied AI, computer vision, world models, spatial …
- Very specific: line 18
Create or resume one task directory under survey_tasks/<topic-slug>/
- Very specific: line 19
Keep task.md stable unless the user explicitly changes the task itself
- Distinctive: line 29
Every survey task lives under:
- Very specific: line 44
Treat the root papers/ directory as an unsorted staging pool, not as the long-term citation location.
- Very specific: line 46
If another task later needs the same paper, copy it from the first task's sources/papers/ into the new task instead of pointing back to the …
- Very specific: line 47
Use relative local links from survey.md, such as ./sources/papers/example.pdf.
- Distinctive: line 48
If a source cannot be downloaded locally, cite the canonical web URL instead.
- Distinctive: line 52
Read these bundled files before acting:
- Distinctive: line 57
Use these bundled templates and scripts instead of improvising new file layouts:
- Distinctive: line 71
If the task directory does not exist, run:
- Distinctive: line 77
If the task already exists, read in this order before doing any new work:
- Very specific: line 84
Do not rewrite task.md unless the user explicitly changes the task definition.
- Distinctive: line 88
Default search order is fixed:
- Very specific: line 96
Use the current agent's web search / fetch capabilities for publisher-first searching.
- Distinctive: line 107
Prefer official publisher or venue pages over tertiary summaries.
- Distinctive: line 108
Prefer formal published versions over arXiv when both exist.
- Distinctive: line 109
Keep arXiv as a rapid frontier source and fallback download source.
- Distinctive: line 111
If one source is unavailable, continue with the others rather than blocking.
- Distinctive: line 115
Only migrate local PDFs that the current task actually absorbs.
- Very specific: line 133
Remove migrated items from the current_task.md pending migration list.
- Very specific: line 134
Never keep citing the old root papers/ path in survey.md.
- Distinctive: line 138
Never read more than 10 PDF pages at once.
- Very specific: line 149
Do not write firm conclusions into survey.md before understanding:
- Distinctive: line 155
Use survey papers to build taxonomy and terminology first.
- Distinctive: line 156
Use original papers to strengthen category paragraphs and comparisons.
- Very specific: line 166
If a paper is not yet fully understood, keep it in current_task.md or note it in round_log.md as pending.
- Distinctive: line 168
Keep every claim traceable to a relative local path or canonical web link.
- Distinctive: line 176
Leave the next round with:
- Distinctive: line 182
Do not finish a round with only a vague note like "continue later."
- Distinctive: line 193
Default language is Chinese, while preserving English titles, venues, and technical terms where useful.
- Distinctive: line 197
If a source cannot be downloaded, keep the best canonical URL and continue.
- Distinctive: line 198
If Semantic Scholar or arXiv access is temporarily unavailable, keep working with the remaining sources.
- Distinctive: line 199
If a PDF is longer than expected, continue chunked reading rather than skipping it.
- Distinctive: line 200
If a paper is relevant but still unclear, mark it as pending instead of writing a fake summary.
- Very specific: line 201
If a task directory already exists, preserve task.md by default and only recreate missing files.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Research Survey Loop
Survey topic: $ARGUMENTS
Overview
Use this skill for long-running survey work with a primary focus on robotics, embodied AI, computer vision, world models, spatial intelligence, navigation, manipulation, and 3D perception.
The workflow can extend to adjacent computer science topics, but the bundled search priorities, venue choices, and writing templates are optimized for robotics and embodied AI communities rather than for all research domains equally.
The default working style is:
- Create or resume one task directory under
survey_tasks/<topic-slug>/ - Keep
task.mdstable unless the user explicitly changes the task itself - Append
round_log.mdevery round - Rewrite
current_task.mdevery round so the next unattended run has a precise entry point - Grow one long
survey.mdby category paragraphs rather than per-paper cards - Move task-absorbed local PDFs out of the root
papers/pool into the task's ownsources/papers/
This skill is academic-first. Only include industry_report/ when the user explicitly wants industry or market material mixed into the survey.
Directory Contract
Every survey task lives under:
survey_tasks/<topic-slug>/
task.md
round_log.md
current_task.md
survey.md
sources/
papers/
supplementary/Rules:
- Treat the root
papers/directory as an unsorted staging pool, not as the long-term citation location. - Once a local PDF is truly used by a task, move it into that task's
sources/papers/. - If another task later needs the same paper, copy it from the first task's
sources/papers/into the new task instead of pointing back to the old path. - Use relative local links from
survey.md, such as./sources/papers/example.pdf. - If a source cannot be downloaded locally, cite the canonical web URL instead.
Required Resources
Read these bundled files before acting:
references/source-priority.mdfor the fixed search order and venue prioritiesreferences/writing-rules.mdfor reading depth, citation format, migration rules, and round-closing discipline
Use these bundled templates and scripts instead of improvising new file layouts:
assets/task-template.mdassets/round-log-template.mdassets/current-task-template.mdassets/survey-template.mdscripts/init_task.pyscripts/fetch_sources.pyscripts/extract_pdf_chunk.py
Workflow
1. Bootstrap or Resume
If the task directory does not exist, run:
python3 scripts/init_task.py "TOPIC" --workspace-root "$PWD"If the task already exists, read in this order before doing any new work:
task.mdcurrent_task.md- The latest round in
round_log.md survey.md
Do not rewrite task.md unless the user explicitly changes the task definition.
2. Search Web First
Default search order is fixed:
- Nature / Science and related journals
- Top CV venues
- Top robotics venues
- arXiv
- Local
papers/pool as supplement, de-dup, or migration source
Use the current agent's web search / fetch capabilities for publisher-first searching. Use scripts/fetch_sources.py to normalize downloads and imports into the task directory.
Typical commands:
python3 scripts/fetch_sources.py search "TOPIC" --task-dir "survey_tasks/TOPIC-SLUG" --max-per-source 5
python3 scripts/fetch_sources.py download --task-dir "survey_tasks/TOPIC-SLUG" --arxiv-id 2402.07556Search rules:
- Prefer official publisher or venue pages over tertiary summaries.
- Prefer formal published versions over arXiv when both exist.
- Keep arXiv as a rapid frontier source and fallback download source.
- The bundled
fetch_sources.py searchcommand uses public Semantic Scholar and arXiv APIs for normalized results. - If one source is unavailable, continue with the others rather than blocking.
3. Import and Migrate Local Papers
Only migrate local PDFs that the current task actually absorbs.
To move a root-level paper into the task:
python3 scripts/fetch_sources.py import-local --task-dir "survey_tasks/TOPIC-SLUG" "papers/file.pdf"To reuse a paper from another survey task:
python3 scripts/fetch_sources.py reuse-task-paper --task-dir "survey_tasks/TOPIC-SLUG" --from-task "survey_tasks/OTHER-TASK" "sources/papers/file.pdf"Migration rules:
- Move from root
papers/into the task when the paper becomes part of the task's reading queue or survey evidence. - Record the original and destination paths in
round_log.md. - Remove migrated items from the
current_task.mdpending migration list. - Never keep citing the old root
papers/path insurvey.md.
4. Read PDFs in Chunks
Never read more than 10 PDF pages at once.
Use:
python3 scripts/extract_pdf_chunk.py "survey_tasks/TOPIC-SLUG/sources/papers/file.pdf" --start-page 1 --end-page 10 --jsonRules:
- Long papers must be read in consecutive windows such as
1-10,11-20,21-30. - Do not write firm conclusions into
survey.mdbefore understanding:- the research problem
- the core method
- the claimed contribution
- the evidence supporting the claim
- the main limitation
- Use survey papers to build taxonomy and terminology first.
- Use original papers to strengthen category paragraphs and comparisons.
5. Write the Survey Incrementally
survey.md is one long Markdown document, not a pile of independent paper cards.
Writing rules:
- First round: build rough categories and coarse survey paragraphs.
- Later rounds: deepen one category at a time by integrating newly understood papers into the relevant paragraph.
- If a paper is not yet fully understood, keep it in
current_task.mdor note it inround_log.mdas pending. - Preserve terminology consistency across rounds.
- Keep every claim traceable to a relative local path or canonical web link.
6. Close the Round
At the end of every round:
- Append a new round block to
round_log.md - Rewrite
current_task.md - Leave the next round with:
- explicit search queue
- explicit reading queue
- explicit pending migrations
- explicit next paragraph targets in
survey.md
Do not finish a round with only a vague note like "continue later."
Output Shape
The four main files have fixed roles:
task.md: stable task contractround_log.md: append-only historycurrent_task.md: editable current execution plansurvey.md: long-form Chinese survey with category paragraphs
Default language is Chinese, while preserving English titles, venues, and technical terms where useful.
Failure Handling
- If a source cannot be downloaded, keep the best canonical URL and continue.
- If Semantic Scholar or arXiv access is temporarily unavailable, keep working with the remaining sources.
- If a PDF is longer than expected, continue chunked reading rather than skipping it.
- If a paper is relevant but still unclear, mark it as pending instead of writing a fake summary.
- If a task directory already exists, preserve
task.mdby default and only recreate missing files.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

