Skip to main content
ClaudeWave
Skill4.3k repo starsupdated 7d ago

latex-conference-template-organizer

# LaTeX Conference Template Organizer This Claude Code skill transforms disorganized conference LaTeX template .zip files into clean, Overleaf-ready submission structures. Use it when you need to organize messy official conference templates by extracting files, identifying the main document, removing redundant sample content and comments, restructuring directories, and generating a README with submission guidelines. The skill operates in analyze-then-confirm mode, first diagnosing issues before executing cleanup after your approval.

Install in Claude Code
Copy
git clone --depth 1 https://github.com/Galaxy-Dawn/claude-scholar /tmp/latex-conference-template-organizer && cp -r /tmp/latex-conference-template-organizer/skills/latex-conference-template-organizer ~/.claude/skills/latex-conference-template-organizer
Then start a new Claude Code session; the skill loads automatically.

SKILL.md

# 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:

```bash
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

```bash
# 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:

```markdown
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:

```markdown
## 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

```bash
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):
```latex
\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:

```latex
%% ============================================================================
%% 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)
%% ============================================================================
\settopmatter{printacmref=false}  % Disable ACM Reference Format
\setcopyright{none}               % Disable copyright notice
\acmConference[]{}{}{}            % Clear conference info (removes footnote)
\acmYear{}
code-reviewerSubagent

Expert code review specialist. Proactively reviews code for quality, security, and maintainability. Use immediately after writing or modifying code. MUST BE USED for all code changes.

kaggle-minerSubagent

Use this agent when the user provides a Kaggle competition URL or asks to learn from Kaggle winning solutions. Examples:

literature-reviewerSubagent

Use this agent when the user asks to "conduct literature review", "search for papers", "analyze research papers", "identify research gaps", "review related work", or mentions starting a research project. This agent integrates with Zotero for automated paper collection, organization, and full-text analysis. Examples:

paper-minerSubagent

Use this agent when the user provides a research paper (PDF/DOCX/arXiv link) or asks to learn writing patterns from papers, extract venue-specific writing signals, study paper structure, or mine rebuttal strategies. The agent writes extracted knowledge into the active installed paper-miner writing memory for ml-paper-writing. It does not maintain project-specific writing memory.

rebuttal-writerSubagent

Use this agent when the user asks to "write rebuttal", "respond to reviewers", "analyze review comments", or needs help with academic paper review response. This agent specializes in systematic rebuttal writing with professional tone and structured responses.

tdd-guideSubagent

Test-driven development guide for writing tests first, implementing the smallest passing change, and keeping verification tight. Use when the user explicitly wants TDD or when a task should be driven by failing tests before code.

analyze-resultsSlash Command

Run a blocker-first post-experiment workflow: validate evidence, produce strict statistical analysis when possible, and generate a decision-oriented results report only when the analysis bundle is sufficient. Uses results-analysis + results-report as a gated two-stage workflow.

commitSlash Command

Commit changes following Conventional Commits format (local only, no push).