Autonomously improve a generated paper via Gemini review through gemini-review MCP → implement fixes → recompile, for 2 rounds. Use when user says "改论文", "improve paper", "论文润色循环", "auto improve", or wants to iteratively polish a generated paper.
692e9faOverride for Codex users who want Gemini , not a second Codex agent, to act as the reviewer. Install this package after . Auto Paper Improvement Loop: Review → Fix → Recompile Autonomously improve the paper at: $ARGUMENTS Context This skill is designed to run after Workflow 3 ( → → → ). It takes a compiled paper and iteratively improves it through external LLM review. Unlike (which iterates on research — running experiments, collecting data, rewriting narrative), this skill iterates on paper…
Full body not shown for this license – view the source on GitHub →Copy a source-pinned command for your client. You run it yourself.
Destination: .claude/skills/auto-paper-improvement-loop · pinned to the source commit
# Run from your project root
git clone https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 692e9fa3fea40bbdf614584d461851f8fb968ac2
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/42-wanshuiyin-ARIS/skills/skills-codex-gemini-review/auto-paper-improvement-loop" ".claude/skills/"
rm -rf .skillboard-tmpReview the source before running. This copies files into your project; it is not a one-click install and does not verify runtime safety.
sudo apt update && sudo apt install -y gitnpm install -g @anthropic-ai/claude-code# Run from your project root
git clone https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills.git .skillboard-tmp
git -C .skillboard-tmp checkout 692e9fa3fea40bbdf614584d461851f8fb968ac2
mkdir -p ".claude/skills"
cp -r ".skillboard-tmp/skills/42-wanshuiyin-ARIS/skills/skills-codex-gemini-review/auto-paper-improvement-loop" ".claude/skills/"
rm -rf .skillboard-tmpDestination: .claude/skills/auto-paper-improvement-loop
Scanner static-checks@0.1.0 · commit 692e9fa3fea4. Static checks cannot prove runtime safety – review the source and the exact diff before installing. How checks work.
No static rules matched. This is not a safety guarantee.