--- name: latex-paper-conversion description: "This skill should be used when the user asks to convert an academic paper in LaTeX from one format (e.g., Springer, IPOL) to another format (e.g., MDPI, IEEE, Nature). It automates extraction, injection, fixing formatting, and compiling." risk: safe source: community date_added: "2026-03-14" --- # LaTeX Paper Conversion ## Overview This skill automates the tedious and recurring process of converting an academic paper written in LaTeX from one publisher's template to another. Different journals (e.g., Springer, MDPI, IEEE) have vastly different structural requirements, document classes, margin settings, and bibliography styles. This skill streamlines these conversions by executing a structured multi-stage workflow, extracting content, mapping it to a new template, and resolving common compilation errors. ## When to Use This Skill - Use when the user requests to port an existing LaTeX paper to a new journal's format. - Use when the user provides an existing `.tex` file and a new template directory. - Use when the user mentions converting from format A (e.g., IPOL/Neural Processing) to format B (e.g., MDPI). ## How It Works ### Step 1: Pre-requisites & Assessment Identify the **Source LaTeX file** and asking the user for the **Target Template Directory**. Understand the core layout mapping (single-column vs. double-column, bibliography style). ### Step 2: Extraction & Injection Script Generation Create a Python script (e.g., `convert_format.py`) to parse the source LaTeX file. Use reviewed boundary-aware extraction; regular expressions alone do not safely parse arbitrary nested TeX. Preserve comments, macros, included files, labels, citations and author metadata, then compare the extracted body with the source. Merge the new template's `preamble`, the extracted `body`, and the `backmatter`. Write this to a new file in an output directory. ### Step 3: Systematic Fixing Perform generic fixes on the extracted body text before writing the final file, or in subsequent calls: - Convert math environment cases (e.g., `\begin{theorem}` to `\begin{Theorem}`). - Adjust aggressive float placements (e.g., `[!t]` or `[h!]`) to template-supported options. Avoid forcing `[H]` unless the `float` package is explicitly loaded. - Ensure `\includegraphics` paths are relative to the new `.tex` file location. - Adapt tables individually to `\columnwidth` or `\textwidth` as appropriate. `tabularx` needs its package, a column specification and a matching end environment; do not replace only the begin command. ### Step 4: Compilation & Debugging Use the template-required engine and bibliography backend (BibTeX or Biber), with enough reruns to resolve references. Compile reviewed sources in an isolated output directory without shell escape; untrusted TeX and build scripts can read files or execute commands. Check the `.log` file using `grep` or `rg` to systematically fix any packages conflicts, undefined commands, or compilation halts. ## Examples ### Example 1: Converting IPOL to MDPI ``` USER: "I need to convert my paper 'SAHQR_Paper.tex' to the MDPI format located in the 'MDPI_template_ACS' folder." AGENT: *Triggers latex-paper-conversion skill* 1. Analyzes source `.tex` and target `template.tex`. 2. Creates Python script to extract Introduction through Conclusion. 3. Injects content into MDPI template. 4. Updates image paths and selects supported float options; uses `[H]` only if required and supported. 5. Compiles via pdflatex and bibtex to confirm zero errors. ``` ## Best Practices - ✅ Always write a Python extraction script; DO NOT manually copy-paste thousands of lines of LaTeX. - ✅ Run the template-required compiler when available and verify logs plus visual output; report compilation as unverified when unavailable. - ✅ Explicitly ask the user for the structural mapping if the source and target differ drastically (e.g., merging abstract and keywords). - ❌ Don't assume all math packages automatically exist in the new template (e.g., add `\usepackage{amsmath}` if missing). ## Common Pitfalls - **Problem:** Overfull hboxes in tables when moving from single to double column. **Solution:** Detect `\begin{tabular}` and automatically wrap in `\resizebox{\columnwidth}{!}{...}` or suggest a format change. - **Problem:** Undefined control sequence errors during compilation. **Solution:** Search the `Paper.log` and include the missing `\usepackage{}` in the converted template. ## Additional Resources - [Overleaf LaTeX Documentation](https://www.overleaf.com/learn) ## Limitations - Use this skill only when the task clearly matches the scope described above. - Do not treat the output as a substitute for environment-specific validation, testing, or expert review. - Stop and ask for clarification if required inputs, permissions, safety boundaries, or success criteria are missing. --- Source attribution: MArbeeGit Original project: https://github.com/sickn33/agentic-awesome-skills/blob/94d66a204c8903f14165b04921f9e4ec196ab58f/skills/latex-paper-conversion/SKILL.md License: CC-BY-4.0 License information: https://creativecommons.org/licenses/by/4.0/ Original upstream instructions; downloaded from Dave AI. # Dave AI resource metadata Creator / publisher: MArbeeGit Original project: https://github.com/sickn33/agentic-awesome-skills/blob/94d66a204c8903f14165b04921f9e4ec196ab58f/skills/latex-paper-conversion/SKILL.md Attribution basis: Original package contribution recorded in publisher Git history Fields of work: Education & Research Roles: Academic Writer Specialties: Specialty not specified Tools: Tool not specified Country applicability: Country not specified Classification basis: Dave AI task classification from package title, description, and declared metadata Instruction SHA-256: 8cee3bad978b8d5aa0bf383719adccdab7c5936f7da0fa2593c6e9e0eec2fb1d Metadata reviewed: 2026-10-27 This metadata supersedes earlier Dave AI catalog attribution. Original instruction and supporting files are preserved.