Skip to content

/latex-conference-template-organizer

Organize messy conference LaTeX template .zip files into clean Overleaf-ready structure. Use when the user asks to "organize LaTeX template", "clean up .zip template", or "prepare Overleaf submission template".

From plugin
claude-scholar
5.5k45 skills6 agents65 commands5 hooks
Install
$ npx -y skills add Galaxy-Dawn/claude-scholar --skill latex-conference-template-organizer --agent claude-code

How it fires

How this skill gets triggered: by you, by Claude, or both.

  • Fires itselfAuto-invocation. Claude auto-loads it when your prompt matches the work.Auto-invocation is when the right skill fires by itself at the right moment, driven by a FLOW.md router and a hook, instead of you invoking it by name. It is the difference between a skill being installed and a skill actually getting used.Read the full definition →
  • You can call itInvoke it directly when you want it.
  • Slash command/latex-conference-template-organizer

Context preview

The summary Claude sees to decide when to auto-load this skill.

Organize messy conference LaTeX template .zip files into clean Overleaf-ready structure. Use when the user asks to "organize LaTeX template", "clean up .zip template", or "prepare Overleaf submission template".

SKILL.md

latex-conference-template-organizer.SKILL.md
name: latex-conference-template-organizer
description: Organize messy conference LaTeX template .zip files into clean Overleaf-ready structure. Use when the user asks to "organize LaTeX template", "clean up .zip template", or "prepare Overleaf submission template".
version: 0.1.0

LaTeX Conference Template Organizer

Overview

Transform messy conference LaTeX template .zip files into clean, Overleaf-ready submission templates. Official conference templates often contain excessive example content, instructional comments, and disorganized file structures. This skill converts them into templates ready for writing.

Working Mode

**Analyze-then-confirm mode**: First analyze issues and present them to the user, then execute cleanup after confirmation.

Complete Workflow

Receive .zip file
    ↓
1. Extract and analyze file structure
    ↓
2. Identify main file and dependencies
    ↓
3. Diagnose issues (present to user)
    ↓
4. Ask for conference info (link/name)
    ↓
5. Wait for user confirmation of cleanup plan
    ↓
6. Execute cleanup, create output directory
    ↓
7. Generate README (with official website info)
    ↓
8. Output complete

Step 1: Extract and Analyze

Extract Files

Extract .zip to a temporary directory:

unzip -q template.zip -d /tmp/latex-template-temp
cd /tmp/latex-template-temp
find . -type f -name "*.tex" -o -name "*.sty" -o -name "*.cls" -o -name "*.bib"

Identify File Types

| File Type | Purpose | |-----------|---------| | `.tex` | LaTeX source files | | `.sty` / `.cls` | Style files | | `.bib` | Bibliography database | | `.pdf` / `.png` / `.jpg` | Image files |

Identify Main File

**Common main file names:**

  • `main.tex`
  • `paper.tex`
  • `document.tex`
  • `sample-sigconf.tex`
  • `template.tex`

**Identification methods:** 1. Check if filename matches common patterns 2. Search for files containing `\documentclass` 3. If multiple candidates exist, ask user to confirm

# Find files containing \documentclass
grep -l "\\documentclass" *.tex

Step 2: Diagnose Issues

Present discovered issues to the user:

Disorganized File Structure

  • Multi-level directory nesting
  • .tex files scattered across directories
  • Unclear which file is the main file

Redundant Content

Detect the following patterns and flag for cleanup:

  • Filenames containing: `sample`, `example`, `demo`, `test`
  • Comments containing: `sample`, `example`, `template`, `delete this`

Dependency Issues

  • Referenced `.sty`/`.cls` files missing
  • Image/table reference paths incorrect

Step 3: Ask for Conference Information

Ask the user for the following information:

Please provide the following information (optional):

1. **Conference submission link** (recommended): Used to extract official submission requirements
2. **Conference name**: If no link available
3. **Other special requirements**: Such as page limits, anonymity requirements, etc.

Step 4: Present Cleanup Plan

Present the cleanup plan to the user and wait for confirmation:

## Cleanup Plan

### Issues Found
- [List diagnosed issues]

### Cleanup Approach
1. Main file: main.tex (clean example content)
2. Section separation: text/ directory
3. Resource directories: figures/, tables/, styles/

### Output Structure
[Show output directory structure]

Confirm execution? [Y/n]

Step 5: Execute Cleanup

Create Output Directory Structure

mkdir -p output/{text,figures,tables,styles}

Clean Up Main File (main.tex)

**Keep:**

  • `\documentclass` declaration
  • Required package imports
  • Core configuration (e.g., anonymous mode)

**Remove:**

  • Example section content
  • Verbose instructional comments
  • Example author/title information

**Add:**

  • Import sections with `\input{text/XX-section}`

**Example main.tex structure** (ACM template standard format):

\documentclass[...]{...}  % Keep original template document class

% Required packages (keep original template package declarations)

%% ============================================================================
%% Preamble: Before \begin{document}
%% ============================================================================

%% Title and author information
\title{Your Paper Title}
\author{Author Name}
\affiliation{...}

%% Abstract (in preamble, before \maketitle)
\begin{abstract}
% TODO: Write abstract content
\end{abstract}

%% CCS Concepts and Keywords (in preamble)
\begin{CCSXML}
<ccs2012>
   <concept>
       <concept_id>10010405.10010444.10010447</concept_id>
       <concept_desc>Applied computing~...</concept_desc>
       <concept_significance>500</concept_significance>
   </concept>
</ccs2012>
\end{CCSXML}

\ccsdesc[500]{Applied computing~...}
\keywords{keyword1, keyword2, keyword3}

%% ============================================================================
%% Document Body
%% ============================================================================
\begin{document}

\maketitle

%% Section content (imported from text/)
\input{text/01-introduction}
\input{text/02-related-work}
\input{text/03-method}
\input{text/04-experiments}
\input{text/05-conclusion}

\bibliographystyle{...}
\bibliography{references}

\end{document}

KDD 2026 Anonymous Submission Special Configuration

For KDD 2026 (using ACM acmart template), add the `nonacm` option to the document class to remove footnotes:

%% ============================================================================
%% Document Class - KDD 2026 Anonymous Submission Configuration
%% Submission version: \documentclass[sigconf,anonymous,review,nonacm]{acmart}
%% Camera-ready: \documentclass[sigconf]{acmart}
%% ============================================================================
\documentclass[sigconf,anonymous,review,nonacm]{acmart}

%% ============================================================================
%% Disable ACM metadata (submission version only)
%% ====================
Read more
Ships withclaude-scholar

Semi-automated research assistant for academic research and software development. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across ideation, coding, experiments, writing, and publication.

Get the whole plugin, auto-invoked

Other skills on claude-scholar.