Guide · Agent skill
How to use the Resubmit Pipeline agent skill for Claude Code
Updated · written with AI from the project's own documentation and checked against our catalogue data
The resubmit-pipeline skill is a set of instructions that an AI agent follows to move an already finished academic paper to a different conference or journal. It is built for researchers with a rejected or withdrawn paper who need to resubmit quickly under hard limits: no new experiments, no bibliography edits, no framework changes, and no overwriting the earlier submission. After this guide you will know what the skill does, how to install it, how to phrase a request that triggers it, and what inputs it needs before it starts.
Resubmit Pipelinewanshuiyin/Auto-claude-code-research-in-sleep · MIT Download the skill Quick start
- 1Download and install the ZIP. Download the skill ZIP from this page and unzip it into ~/.claude/skills/ for all projects, or into .claude/skills/ inside one project. Alternatively, upload it in Claude apps under Settings, Capabilities, Skills.
- 2Prepare the paper folder. Make sure the polished paper folder has main.tex, a sec/ folder, references.bib and a compiled main.pdf.
- 3Gather the target venue files. Place the target venue's LaTeX template and style files under templates/ or in a recognised template directory.
- 4Collect prior reviewer reports. Put the earlier reviewer reports in one folder as .txt or .md files. Without them the skill stops with a missing_review_corpus block.
- 5Ask for the resubmit in plain language. Tell the agent to resubmit the paper to the named venue, and point it to the paper folder and review folder.
- 6Review the new sibling folder. Check the new venue folder, the edits made and the whitelist before any upload. Confirm the original folder is unchanged.
What is an agent skill and what does this one make the agent do?
An agent skill is a folder containing a SKILL.md file. The file tells a compatible AI agent when to use the skill and how to carry out a multi-step task. This skill is the resubmit step of the wider ARIS research workflow. It is named resubmit-pipeline and is described as a text-only resubmit of a polished paper to a different venue.
The skill copies the paper into a new sibling folder rather than editing the earlier submission. It then uses the prior reviewer reports to make small text edits, and checks the result against a whitelist of allowed changes. If reviewer feedback calls for new theory or new experiments, the skill stops and asks you to decide instead of continuing.
- Creates a new venue folder next to the original paper folder and refuses to run if that folder already exists.
- Copies sections, macro files and figures into the new folder physically, without symlinks.
- Writes a new main.tex based on the target venue's style files.
- Applies reviewer-guided text edits limited to an edit whitelist.
- Emits BLOCKED with reason_code out_of_scope_microedit when feedback needs new theorems or a new framework.
How do you install the resubmit-pipeline skill?
Download the skill ZIP from this page. You can install it for all of your projects or for a single project.
For a personal install, unzip the file into ~/.claude/skills/. For a single project, unzip it into the .claude/skills/ folder inside that project. Claude apps also accept an upload: open Settings, go to Capabilities, then Skills, and upload the ZIP there.
- Personal install: the ~/.claude/skills/ folder.
- Project install: the .claude/skills/ folder inside your project.
- Claude apps: Settings → Capabilities → Skills, then upload the ZIP.
How do you trigger the skill with a natural request?
You do not need to type a command. The skill's description lists phrases that should activate it, so ordinary requests work. Good phrases include resubmit pipeline, port paper to a new venue, resubmit to a named venue, and tighten paper for resubmission. The skill also responds to the Chinese phrase 重投流程.
The skill is meant for a rejected or withdrawn paper that you want to move to a different top venue under a tight time budget. If your request is closer to writing a rebuttal or adding experiments, a different skill fits better.
- Example: resubmit this paper to ICLR, prior reviews are in reviews/
- Example: port paper to NeurIPS format and tighten it for resubmission.
- Example: run the resubmit pipeline for my withdrawn paper, target venue AAAI.
What inputs do you need before you start?
The skill needs three inputs. If the reviewer reports are missing, the skill stops with BLOCKED and reason_code missing_review_corpus, because absorbing those concerns is the purpose of a resubmit. The paper should already be finished, with proofs, experiments and bibliography in place.
The optional arguments let you change the reviewer model, the number of rounds, the effort level, or the Overleaf project used for the final push. Defaults are set in the skill file.
- The polished paper folder in the earlier venue's format, containing main.tex or an equivalent entry file, a sec/ or sections/ folder, a references.bib or equivalent, and a compiled main.pdf.
- The target venue, chosen from iclr, icml, neurips, aaai, ijcai, colm, tmlr, uai or other. For other, you give a path to the style directory.
- A review corpus: a folder of prior reviewer reports as .txt or .md files, ideally one file per reviewer.
- The target venue's LaTeX template and style files, placed at templates/<venue>.sty, .tex or .bst inside the paper folder or in a recognised template directory.
- Agent tools: Claude Code or a SKILL.md-compatible agent with Bash, file read/write and search tools, plus Codex MCP (mcp__codex) for the default reviewer route or another configured reviewer backend.
How does the isolation step protect your earlier submission?
The first phase creates the new venue folder with mkdir, which fails if the folder already exists. This means a rerun cannot overwrite an earlier submission. Files are then copied physically into the new folder. The source is explicit that symlinks and cross-directory includes are not used, because symlinks break Overleaf zip export and shared includes would change prior submissions.
Your original paper folder is treated as read-only. Everything the new submission needs is copied into the sibling folder.
- Sections are copied with a plain recursive copy, not linked.
- Macro files that sections depend on are copied into the new folder.
- main.tex is written fresh for the target venue's style file, starting from the template skeleton.
- Only the title, author block, abstract include and section input lines are carried over from the earlier main.tex.
cp -r $PAPER_BASE_DIR/sec/ $NEW_VENUE_DIR/sec/What safety points should you know before running it?
This skill runs scripts and uses the network. Its tool list includes Bash and the Codex MCP reviewer tools, so the agent can run shell commands and send material to a reviewer backend. Read the skill file and check the allowed tools before you run it on a paper you cannot afford to expose.
The skill is designed to avoid changing prior work. Its hard rules include never overwriting a previous submission directory and never editing the bibliography, but these rules are enforced by the instructions the agent follows, so review the output folder yourself before submitting.
- Runs scripts: yes. Uses network: yes.
- Reviewer calls go through the configured backend; the default route is Codex MCP.
- Check the new folder's files and the edit whitelist before any upload.
- Keep a backup of the original paper folder before starting.
What tips help a resubmit go smoothly?
Start with a complete set of reviewer reports, since the skill depends on them to decide what to change. Keep requests narrow: a text-only resubmit works best when the reviewer concerns are about wording, clarity, or length. If a reviewer asks for new proofs or experiments, plan that work with a different workflow first.
If your target venue has a shorter page limit than the original, expect the skill to tighten the text. Review each edit against the whitelist rather than accepting the output wholesale.
- Check the page limit of the target venue before you start.
- Use an anonymity check for double-blind venues. The skill's optional skip flag is only valid for non-double-blind venues.
- Use the rebuttal workflow separately if you also need a response letter.
What people use it for
- Moving a theory paper rejected from one top venue to another within a one- to two-week window, with text-only edits.
- Adapting a workshop camera-ready paper to a main conference page limit by tightening wording.
- Responding to reviewer comments about clarity or presentation without adding experiments or citations.
- Recognising, through a BLOCKED result, that reviewer feedback needs new theory and should be handled before resubmitting.
Frequently asked questions
How do I install the resubmit-pipeline skill?
Download the ZIP from this page and unzip it into ~/.claude/skills/ for a personal install, or into .claude/skills/ inside a project. You can also upload the ZIP in the Claude apps under Settings, Capabilities, Skills.
What does the resubmit-pipeline skill require?
It needs Claude Code or a SKILL.md-compatible agent with Bash, file tools and search, plus Codex MCP or another configured reviewer backend. You also supply the venue template files, a compiled main.pdf with LaTeX source, and prior reviewer reports as .txt or .md files.
Is the resubmit-pipeline skill free and what is its licence?
The skill is listed under the MIT licence. Check the licence text in the repository for the exact terms before you redistribute it.
Why does the skill stop with BLOCKED and missing_review_corpus?
The skill is designed to absorb concerns from prior reviewer reports. If you do not supply those reports, it stops rather than resubmitting without them. Add the reviewer files to a folder and pass that path as the review corpus.
Can the skill write my rebuttal letter?
No. The skill's own description points to a separate rebuttal workflow for response letters. Use that workflow for the rebuttal and this skill for the in-paper text edits.
What should I use if my paper still needs experiments or new sections?
Use the experiment workflow and the paper-writing workflow first. This skill refuses out-of-scope edits, so it is not the right tool for papers that still need new work.
New agent skills, repos and AI tools — every week
The best new skills and open-source projects, the fastest-growing repos, and one free prompt. Five minutes to read. Unsubscribe anytime.
Our verdict
Use this skill if you have a finished paper, prior reviewer reports and a tight deadline to resubmit to a different venue with text-only changes. Pick something else if your reviewers want new experiments, new theory or a structural rewrite, or if you need a rebuttal letter, since the skill is built to stop in those cases.
Download the skill