paper-compile

Compile LaTeX manuscripts, repair build failures, and verify the rendered PDF.

Updated Aug 18, 2026
One-click install
npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill paper-compile-nitrogen216
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: paper-compile
Source: https://github.com/Nitrogen216/awesome-dsh-mods/tree/main/modes/dsh-autoresearch/skills/paper-compile
Command: npx skills add https://github.com/Nitrogen216/awesome-dsh-mods --skill paper-compile-nitrogen216

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? LaTeX research manuscripts often fail to build due to source errors, bibliography issues, or missing figures, and a successful exit code alone does not guarantee the rendered PDF is correct. This Skill builds the manuscript, diagnoses failures with a bounded fix loop, and verifies the actual PDF output against venue requirements. ## Core Features & Use Cases - Bounded Build Diagnosis: Runs at most three compile-and-fix attempts per failure class, locating the first actionable source error and applying the smallest fix before rebuilding. - PDF Verification: Checks undefined citations, missing figures, embedded fonts, overfull content, and visually inspects every page for clipping, broken equations, and misplaced floats. - Venue Compliance Checks: Verifies page-limit and anonymity rules against official venue sources, or records them as not applicable for venue-neutral builds. - Use Case: After drafting a conference paper, run this Skill to build paper/main.pdf, fix a broken bibliography entry, confirm the page count fits the venue limit, and receive a COMPILE_REPORT.md documenting every check performed. ## Quick Start Use the paper-compile skill to build my LaTeX manuscript in the paper directory and verify the rendered PDF against the venue requirements.

Frequently Asked Questions about paper-compile

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I fix LaTeX compilation errors in a research paper?▼

Capture the complete build log, locate the first actionable source error, apply the smallest source fix, and rebuild from the documented entry point. Limit attempts to three per failure class; if the same failure persists after two focused fixes, report the exact source location and log excerpt instead of broad editing.

How to verify a LaTeX PDF meets conference venue requirements?▼

After a successful build, check the official venue source for current page-limit and anonymity rules and verify the PDF against them. Distinguish main text, references, and appendix when reporting page count, and record checks as not applicable for venue-neutral builds.

Does a successful latexmk build guarantee the PDF is correct?▼

No, a successful exit code does not guarantee a correct PDF. You must still check undefined citations and references, missing figures, embedded fonts, overfull content, and visually inspect every page for clipping, broken equations, and misplaced floats.

What LaTeX engine should I use to build my manuscript?▼

Prefer the repository's documented build command and existing build path first. When none exists, use latexmk with the engine required by the manuscript, and do not install a large TeX distribution or replace venue files without user approval.

When should LaTeX build troubleshooting stop and report instead?▼

Stop broad editing when the same failure remains after two focused fixes within the three-attempt bound. Report the exact source location and log excerpt rather than continuing to modify unrelated parts of the manuscript.