Skip to content

fabioc-aloha/Alex_Skill_Mall / plugins/academic-research/latex-paper-conversion/skills/latex-paper-conversion

latex-paper-conversion

Verified

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.

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 Regular Expressions to extract core text blocks. 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.
  • Convert \begin{tabular} to \begin{tabularx}{\textwidth} or use \resizebox if moving to a double-column layout.

Step 4: Compilation & Debugging

Run a build cycle (pdflatex -> bibtex -> pdflatex). 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 table float parameters [h!] to [H].
  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.
  • ✅ Always run pdflatex and verify the .log to ensure the final output compiles.
  • ✅ 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

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.
reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis.Stars: 471kUpdated Claude CodeCodexVerifiedInstall
diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness.Stars: 322kUpdated Claude CodeCodexVerifiedInstall
dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependenciesStars: 322kUpdated Claude CodeCodexVerifiedInstall
executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is availableStars: 322kUpdated Claude CodeCodexVerifiedInstall