Atlas / Skills / galaxy-dawn / Latex Conference Template Organizer

Latex Conference Template OrganizerSAFE

skills/galaxy-dawn/latex-conference-template-organizer

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.

Verdict
SAFE
Grade
B
Trust score
89 /100
Version
0.1.0
Hosts
—
License
MIT
Stars
5,693
01

Overview

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.

Read from source at commit 29ad4d4206fbOBSERVED · 2026-10-07
02

What it tells the agent

The instruction file, verbatim from the audited commit — this is the text the model reads, and the surface the audit's instruction layer examines. Quoted here so you can judge it without cloning anything.

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

```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)
%% ====================
03

Trust audit

SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.

LayerWhat it checksResult
L0Provenance & inventoryPASS
L1Static analysis of the codeNA
L2Instruction surface (what it tells the agent)PASS
L3Class-specific surfacePASS
L4Behavioural (sandbox)SKIPPED

What the source does

Filesystem
none-observed
Network
none-observed
Shell
none-observed
Dependencies
pinned
Secrets in source
none-found

Findings (0)

No findings outside the package's declared scope.

Gates applied: no_behavioural_pass.

Audited 2026-10-07 · audit v0.4.1 · source sha 29ad4d4206fbfull audit observations/trust-audit/skill/galaxy-dawn__latex-conference-template-organizer.json · Report an issue / request a re-scan
04

Audit history

Every audit this skill has had.

DateSourceVerdictGradeScoreChange
2026-10-0729ad4d4206fbSAFEB89first audit
05

Questions

What does the Latex Conference Template Organizer skill do?

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.

Is Latex Conference Template Organizer safe to install?

The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean skill reads B.

What can Latex Conference Template Organizer access on my machine?

The audit observed no filesystem, network or shell use at all in its source.

How current is this page?

The grade is for one exact copy of the source (29ad4d4206fb), read on 2026-10-07. The repository is watched, and a new audit runs when it changes — this is the first audit.

Advertisement