auto-paper-improvement-loop

Automate two-round paper review, fix, and recompile loops with state recovery.

1|Updated Mar 26, 2026
One-click install
npx skills add https://github.com/Lingrongye/federated-learning --skill auto-paper-improvement-loop-lingrongye
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: auto-paper-improvement-loop
Source: https://github.com/Lingrongye/federated-learning/tree/main/Auto-claude-code-research-in-sleep/skills/auto-paper-improvement-loop
Command: npx skills add https://github.com/Lingrongye/federated-learning --skill auto-paper-improvement-loop-lingrongye

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Autonomously improve a generated paper via a two-round review → implement fixes → recompile, enabling iterative enhancement of writing quality and presentation.

Core Features & Use Cases

  • Two-round improvement loop: review, fix, and recompile to enhance rigor and clarity.
  • State persistence and logging: saves progress to PAPER_IMPROVEMENT_STATE.json and PAPER_IMPROVEMENT_LOG.md for recovery and auditing.
  • End-to-end LaTeX workflow: handles paper/main.pdf and compiled artifacts, with deterministic recompile steps.

Quick Start

Provide the path to the compiled paper directory to start the two-round improvement loop.

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 automate paper improvement and polish a research paper autonomously?

Automate paper improvement by running a two-round review-fix-recompile loop that assesses theoretical rigor, writing clarity, and presentation to autonomously polish your research paper.

How does the LaTeX workflow recompile loop handle state persistence for iterative paper enhancement?

The LaTeX workflow handles state persistence by saving progress to PAPER_IMPROVEMENT_STATE.json and logging iterations in PAPER_IMPROVEMENT_LOG.md, enabling recovery and auditing across the review-fix-recompile loop.

Do I need GPT-5.4 xhigh via Codex MCP to run the autonomous paper improvement loop?

Yes, the autonomous paper improvement loop requires GPT-5.4 xhigh via Codex MCP to perform the two-round review and implement fixes across iterations.

Can I enable a human checkpoint during the two-round review-fix-recompile loop for research writing?

Yes, the two-round review-fix-recompile loop optionally enables a human checkpoint, allowing manual review during the iterative enhancement of writing quality and presentation.

What is the best way to start the two-round paper improvement loop for a compiled LaTeX document?

The best way to start the two-round paper improvement loop is to provide the path to the compiled paper directory containing paper/main.pdf and compiled artifacts.

What limitations exist when using autonomous paper improvement for generated research documents?

Limitations include its dependency on GPT-5.4 xhigh via Codex MCP and its design as a post-compilation tool, meaning it applies only after the initial paper is generated and compiled.