latex-paper-conversion
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.
- License 许可
- MIT
- 最近更新
- 2026-11-10
- Stars
- ★ 1
- Forks
- 0
01 前言 Front Matter
- name
- latex-paper-conversion
- risk
- safe
- source
- community
- date_added
- 2026-03-14
- 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.
03 SKILL.md 正文
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
.texfile 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 thefloatpackage is explicitly loaded. - Ensure
\includegraphicspaths are relative to the new.texfile location. - Convert
\begin{tabular}to\begin{tabularx}{\textwidth}or use\resizeboxif 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
- Analyzes source
.texand targettemplate.tex. - Creates Python script to extract Introduction through Conclusion.
- Injects content into MDPI template.
- Updates image paths and table float parameters
[h!]to[H]. - 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
pdflatexand verify the.logto 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.logand 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.
04 同仓库更多 Skills
vercel-sandbox
Run agent-browser + Chrome inside Vercel Sandbox microVMs for browser automation from any Vercel-deployed app. Use when the user needs browser automation in a Vercel app (Next.js, SvelteKit, Nuxt, Remix, Astro, etc.), wants to run headless Chrome without binary size limits, needs persistent browser sessions across commands, or wants ephemeral isolated browser environments. Triggers include "Vercel Sandbox browser", "microVM Chrome", "agent-browser in sandbox", "browser automation on Vercel", or any task requiring Chrome in a Vercel Sandbox.
slack
Interact with Slack workspaces using browser automation. Use when the user needs to check unread channels, navigate Slack, send messages, extract data, find information, search conversations, or automate any Slack task. Triggers include "check my Slack", "what channels have unreads", "send a message to", "search Slack for", "extract from Slack", "find who said", or any task requiring programmatic Slack interaction.
electron
Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.
dogfood
Systematically explore and test a web application to find bugs, UX issues, and other problems. Use when asked to "dogfood", "QA", "exploratory test", "find issues", "bug hunt", "test this app/site/platform", or review the quality of a web application. Produces a structured report with full reproduction evidence -- step-by-step screenshots, repro videos, and detailed repro steps for every issue -- so findings can be handed directly to the responsible teams.
agent-browser
Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include requests to "open a website", "fill out a form", "click a button", "take a screenshot", "scrape data from a page", "test this web app", "login to a site", "automate browser actions", or any task requiring programmatic web interaction.
shadcn
Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI, including chat interfaces. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", "switch to --preset", and for building a design system or applying a DESIGN.md or brand spec to shadcn/ui.