auto-paper-improvement-loop

Iteratively improves LaTeX papers via GPT-5.5 review, fix implementation, and recompilation.

Updated Jul 9, 2026
One-click install
npx skills add https://github.com/Lingjie-wang/autoRL --skill auto-paper-improvement-loop-lingjie-wang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-paper-improvement-loop
Source: https://github.com/Lingjie-wang/autoRL/tree/main/Auto-claude-code-research-in-sleep/skills/auto-paper-improvement-loop
Command: npx skills add https://github.com/Lingjie-wang/autoRL --skill auto-paper-improvement-loop-lingjie-wang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? After generating a research paper draft, authors face the tedious cycle of getting critical feedback, applying fixes, and recompiling — often missing theoretical inconsistencies, overclaims, and formatting issues that reviewers would catch. This Skill automates that polish loop with an external LLM reviewer. ## Core Features & Use Cases - Two-round review-fix-recompile loop: Sends LaTeX source and compiled PDF to GPT-5.5 (xhigh reasoning) for a structured senior-reviewer critique, implements fixes by severity (CRITICAL > MAJOR > MINOR), and recompiles with latexmk. - Reviewer independence guard: Every round uses a fresh review thread with no prior context, preventing score inflation from confirmation bias. - Edit whitelist constraints: Optionally restrict fixes to specific paths and forbid operations like new citations, theorem environments, or numerical claims — essential for resubmit and camera-ready modes. - Quality gates: Includes theorem restatement regression checks, duplicate-label detection, overfull-hbox format checks, and an optional adversarial kill-argument exercise for theory-heavy papers. - Use Case: After compiling a NeurIPS submission draft, run the loop to autonomously raise the paper from a 4/10 to a 7/10 review score across two rounds, with all changes logged in PAPER_IMPROVEMENT_LOG.md. ## Quick Start Run the auto-paper-improvement-loop on my compiled paper in the paper/ directory to review, fix, and recompile it for two rounds.

Frequently Asked Questions about auto-paper-improvement-loop

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I automatically improve a LaTeX research paper with AI review?

Run the loop on a directory containing a compiled paper (main.pdf plus section .tex files). It sends the source and PDF to GPT-5.5 for a structured review, implements fixes by severity, recompiles with latexmk, and repeats for two rounds.

How many improvement rounds does the paper review loop run?

It runs exactly two rounds by default (MAX_ROUNDS = 2). Empirically, round one catches structural issues and round two catches remaining presentation issues, with diminishing returns beyond two rounds for writing-only improvements.

Can I restrict which files the automated paper fixes can edit?

Yes, pass an edit-whitelist YAML or JSON file defining allowed_paths, forbidden_paths, and forbidden_operations such as new citations or theorem environments. Rejected edits are logged to PAPER_IMPROVEMENT_LOG.md without aborting the round.

Why does the reviewer use a fresh thread each round?

Reusing review context causes confirmation bias — observed score inflation from a real 3/10 to a fake 8/10. Fresh threads with no prior fix summaries ensure the reviewer judges only the current LaTeX source and PDF.

What happens if the improvement loop is interrupted mid-run?

The loop writes PAPER_IMPROVEMENT_STATE.json after each round with the current round, score, and status. On restart, if the state is in_progress and less than 24 hours old, it resumes from the next round using the log file.

When should I not wrap this paper improvement skill in a scheduler?

Never schedule it on a wall-clock timer. Quality changes only when the review changes, not when time passes, and a timed self-accepting rerun crosses into self-acquittal. Schedule only the external wait that precedes it.