What problem does it solve?
This Skill solves the pain point of resubmitting a polished, already-reviewed academic paper to a different venue under extremely tight time and compute constraints, where new experiments, bibliography edits, or framework changes are not allowed, and prior submission directories must remain completely untouched.
Core Features & Use Cases
- Non-destructive directory isolation: Creates a new sibling directory for the target venue submission, never modifying prior submission files to preserve existing work.
- 5-layer double-blind anonymity scanning: Automatically detects and flags surface identifiers, self-citation phrasing, acknowledgments, cross-rebuttal references, and internal codenames that would violate double-blind submission rules.
- Constrained text microedit orchestration: Coordinates parallel proof, claim, and citation audits, atomizes prior reviewer concerns into addressable text fixes, and enforces a strict edit whitelist to prevent unintended changes to the paper's structure or bibliography.
- Use Case: A researcher whose paper was rejected at a workshop has 10 days to resubmit to a top-tier conference like ICLR, with no compute budget for new experiments, and needs to address all reviewer feedback via only text edits while meeting the new venue's page limit.
Quick Start
Use the resubmit-pipeline skill to resubmit your polished paper stored at /path/to/your/prior-submission to ICLR using the reviewer reports saved in /path/to/review-folder.
