pdf-compiler

Compile LaTeX projects to PDF with structured error reporting.

7|Updated Mar 16, 2026
One-click install
npx skills add https://github.com/tangshunpu/paper_granny --skill pdf-compiler
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: pdf-compiler
Source: https://github.com/tangshunpu/paper_granny/tree/main/skill/pdf_compiler
Command: npx skills add https://github.com/tangshunpu/paper_granny --skill pdf-compiler

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill automates the process of compiling LaTeX reports into polished PDFs, handling compilation errors, and cleaning intermediate files to streamline publishing workflows.

Core Features & Use Cases

  • Automatic template-aware LaTeX compilation: copies templates from latex_template/* and logos as needed, then builds the final document.
  • Structured error reporting: parses .log output to present actionable errors and warnings.
  • End-to-end build cleanup: removes intermediate files after a successful compile to keep projects tidy.
  • Use Case: In a research workflow, generate a ready-to-submit PDF from a single report.tex with branding assets.

Quick Start

Run the compile_pdf tool on your report.tex to produce the final PDF and automatically clean intermediate files.

Frequently Asked Questions about pdf-compiler

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

FAQPage Schema
How do I automate LaTeX to PDF compilation in a CI pipeline?

Automated LaTeX to PDF compilation uses a tool to run xelatex in nonstopmode with a two-pass build, copying templates and logos before generating the final document. This streamlines automated builds in authoring, review, and CI pipelines.

What's the best way to handle LaTeX compilation errors automatically?

Handling LaTeX compilation errors automatically involves parsing the .log output file after running xelatex to generate a structured error report. This extracts actionable errors and warnings instead of failing silently during the build process.

How do I compile a template-aware LaTeX project into a branded PDF?

Compiling a template-aware LaTeX project requires a build tool to copy templates from latex_template/* and logo assets, then run xelatex to produce a polished PDF. This ensures consistent branding across automated document generation workflows.

Why does my automated LaTeX build leave behind intermediate files?

Automated LaTeX builds leave intermediate files when the process lacks an end-to-end cleanup step. A structured compilation tool removes these auxiliary files after a successful compile to keep your project directory tidy.

Can I use xelatex with nonstopmode for automated report generation?

Yes, using xelatex with nonstopmode is standard for automated report generation because it prevents the compiler from pausing on errors. The build system executes a two-pass compilation to resolve references before parsing the log.

Do I need a specific LaTeX template structure for automated PDF compilation?

Automated PDF compilation expects your LaTeX templates and branding assets to reside in the latex_template/* directory. The build tool copies these files automatically before running xelatex to ensure proper document structure.