PaperFit plugin
A plugin that checks a LaTeX paper's layout on rendered pages, fixes the source and repeats until every page passes review
- 337 ★ on the repository
- Last commit
- MIT
Extended access
Why this level
- The agent edits LaTeX sources and runs compilation in the paper's folder
- With a DEEPSEEK_API_KEY page images are sent to the external DeepSeek API
Install
- Works in
In your terminal, with SkillFoxx CLI
npx skillfoxx add plugins/paperfitDetects the agents on your machine, shows the access level and pins the version.
Other ways to install
Access and checks
How we reviewExtended accessThe tool runs code or makes network calls and only reads external data.
- The agent edits LaTeX sources and runs compilation in the paper's folder
- With a DEEPSEEK_API_KEY page images are sent to the external DeepSeek API
This is third-party code. Review the repository files before installing.
What it does
PaperFit checks the layout of a scientific paper on finished PDF pages. The agent (Claude Code, Codex or Cursor) compiles the project, renders pages to images and looks for defects: widows and orphans, gaps in two-column layout, piled-up figures, tables and formulas that run past the column edge. Then it edits the source and looks at the result again. The loop runs until the visual review of every page passes. Each set of edits is checked after a fresh build, a failed edit is rolled back, and a log of diagnoses and decisions is kept. Separate scenarios cover moving a paper to a CVPR, ICLR, ACL or ACM template, squeezing the main body to a given page count and fixing one table without `resizebox`. Claude Code gets the commands `/paperfit`, `/fix-layout`, `/check-visual`, `/repair-table`, `/migrate-template`, `/adjust-length` and `/show-status`. In Codex you call the paperfit skill, and in Cursor a project rule drives it. With a `DEEPSEEK_API_KEY` a DeepSeek model also reads the pages, while the agent keeps the decisions about edits.
Who it is for. Authors of LaTeX papers before a conference submission: the text moves to a new template or has to fit a page limit.
Good fit when
- The paper builds without errors, but two-column layout has gaps and figures drifted to the last page
- A manuscript moves from one conference template to CVPR or ACL
- The main body has to fit 8 pages without changing the meaning
- A wide table sticks out of the column and has to be rebuilt without `resizebox`
- Before submission you want a report of visual defects without edits: the `/check-visual` command
Not a fit when
- You need to write or edit the paper's text: PaperFit fixes layout, the content stays with the author
- The project has no LaTeX, or the build depends on a closed environment the agent cannot run
- Poppler and a LaTeX compiler cannot be installed on the machine
- The document is not a scientific paper: the layout rules target conference work
Example request
Use PaperFit to squeeze the main body to 8 pages without changing the meaningLimitations
- Node.js 18 or newer, Python 3.8 or newer, Poppler for page rendering and a LaTeX compiler (tectonic, pdflatex or whatever the template requires) are needed.
- The agent's multimodal model inspects the pages, so review quality depends on it. The developer describes the project as in active development.
- Edits go straight into the paper's source, so commit before a run.
- The documentation is in Chinese, while commands and names stay in English.
How to disable. Remove the plugin in Claude Code through `/plugin`. `npm uninstall -g paperfit-cli` removes the package. Delete by hand the files `paperfit-install` placed in the Codex and Cursor directories.
FAQ
How do I install PaperFit in Claude Code?
Run `/plugin marketplace add OpenRaiser/PaperFit`, then `/plugin install paperfit@paperfit-vto`. The other path is `npm install -g paperfit-cli` and `paperfit-install --target claude`.
What does the machine need besides the agent?
Node.js 18 or newer, Python 3.8 or newer, Poppler for page rendering and a LaTeX compiler such as tectonic or pdflatex.
Does PaperFit change the paper's text?
Edits touch layout, tables, figures and the template. Changes to meaning need separate user permission, and figures, captions and references are not removed without consent.
Which templates does PaperFit support?
The README names CVPR, ICLR, ACL and ACM as examples of templates for moving a paper. In Claude Code the `/migrate-template` command starts the move.
Can I only look at defects without edits?
Yes. `/check-visual` in Claude Code runs a visual check without edits, and `paperfit fix-layout` defaults to dry-run mode and applies changes only with the `--apply` flag.
Discussion
No questions or reviews yet.
Related
PluginsChecks every reference of a paper against Crossref, dblp and arXiv before submission, with no language model in the verdicts.
Eight skills for LaTeX research papers, from topic to compiled PDF, with verified BibTeX citations and gated steps
A plugin for studying research papers: a PDF or arXiv link becomes a summary, study materials, code demos and a web viewer
The paper-spine skill takes a topic, materials and data through a scientific paper: literature, text, figures, review and Word, LaTeX and PDF files
A Claude Code skill for research papers: a five-stage pipeline, section rules, a style audit and an independent red-team review.
Takes an agent from a topic to an arXiv review paper in LaTeX IEEEtran: approved plan, every citation checked against a live source, PDF build
Comparison with similar tools
Cards that share the main search query, and how they differ.
| Tool | Official | Repository stars | Main difference |
|---|---|---|---|
| PaperFit (this card) | no | 337 | |
| LaTeX Document Skill | no | 821 | builds a new document into PDF from a description, while PaperFit fixes the layout of a finished paper |
| ChineseResearchLaTeX | no | 3,024 | a template set for Chinese scientific documents, while PaperFit moves a paper between conference templates |
README in short
The README, written in Chinese, starts from the claim that a successful build does not guarantee good layout and compares the manual route with the PaperFit loop. Next come a capability table, result examples, installation for three agents, the workflow and a classification of layout defects (VTO).