Source profileQuality 84/100

Galaxy-Dawn/claude-scholar/skills/latex-conference-template-organizer/SKILL.md

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".

Source repository stars
4,981
Declared platforms
0
Static risk flags
1
Last source update
2026-07-17
Source checked
2026-08-04

Decision brief

What it does—and where it fits

Organize messy conference LaTeX template . zip files into clean Overleaf-ready structure.

Best for

  • Use when the user asks to "organize LaTeX template", "clean up .

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/Galaxy-Dawn/claude-scholar --skill "skills/latex-conference-template-organizer"
Safe inspection promptEditorial

Inspect the Agent Skill "latex-conference-template-organizer" from https://github.com/Galaxy-Dawn/claude-scholar/blob/2f7766fd541a723d4ddc6230b3277f948d61b093/skills/latex-conference-template-organizer/SKILL.md at commit 2f7766fd541a723d4ddc6230b3277f948d61b093. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Complete Workflow

    Review the “Complete Workflow” section in the pinned source before continuing.

    Review and apply the “Complete Workflow” source section.
  2. 02

    Step 1: Extract and Analyze

    Extract .zip to a temporary directory:

    main.texpaper.texdocument.tex
  3. 03

    Step 2: Diagnose Issues

    Present discovered issues to the user:

    Multi-level directory nesting.tex files scattered across directoriesUnclear which file is the main file
  4. 04

    Step 3: Ask for Conference Information

    Ask the user for the following information:

    Ask the user for the following information:
  5. 05

    Step 4: Present Cleanup Plan

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

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

Permission review

Static risk signals and limitations

Writes files

medium · line 27

The documentation asks the agent to create, modify, or delete local files.

Execute cleanup, create output directory

Writes files

medium · line 130

The documentation asks the agent to create, modify, or delete local files.

### Create Output Directory Structure

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score84/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars4,981SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
Galaxy-Dawn/claude-scholar
Skill path
skills/latex-conference-template-organizer/SKILL.md
Commit
2f7766fd541a723d4ddc6230b3277f948d61b093
License
MIT
Collected
2026-08-04
Default branch
main
View the original 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:

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 TypePurpose
.texLaTeX source files
.sty / .clsStyle files
.bibBibliography database
.pdf / .png / .jpgImage 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)
%% ============================================================================
\settopmatter{printacmref=false}  % Disable ACM Reference Format
\setcopyright{none}               % Disable copyright notice
\acmConference[]{}{}{}            % Clear conference info (removes footnote)
\acmYear{}                        % Clear year
\acmISBN{}                        % Clear ISBN
\acmDOI{}                         % Clear DOI

%% Content to restore for camera-ready version:
%% \acmConference[KDD '26]{Proceedings of the 30th ACM SIGKDD Conference on Knowledge Discovery and Data Mining}{August 09--13, 2026}{Jeju, Korea}
%% \acmISBN{978-1-4503-XXXX-X/26/08}
%% \acmDOI{10.1145/nnnnnnn.nnnnnnn}

Create Section Files (text/)

Create independent .tex files for each section, containing only section content without \begin{document} etc.:

text/01-introduction.tex:

\section{Introduction}
% TODO: Write introduction content

text/02-related-work.tex:

\section{Related Work}
% TODO: Write related work content

text/03-method.tex:

\section{Method}
% TODO: Write method content

text/04-experiments.tex:

\section{Experiments}
% TODO: Write experiments content

text/05-conclusion.tex:

\section{Conclusion}
% TODO: Write conclusion content

Important notes:

  • Abstract should be placed in main.tex preamble (before \begin{document}), after \maketitle
  • Files in text/ contain only sections, starting with \section{...}
  • Do not include \begin{document} or other wrappers in text/ files

Copy Style Files (styles/)

Copy all .sty and .cls files from the original template to styles/:

find /tmp/latex-template-temp -type f \( -name "*.sty" -o -name "*.cls" \) -exec cp {} output/styles/ \;

Note: Maintain the original template's directory structure (e.g., acmart/), only move to styles/.

Handle Images and Tables

# Copy image files
find /tmp/latex-template-temp -type f \( -name "*.png" -o -name "*.jpg" -o -name "*.jpeg" -o -name "*.pdf" \) -exec cp {} output/figures/ \;

# Copy table files (if any)
find /tmp/latex-template-temp -type f -name "*.tex" | grep -i table | while read f; do cp "$f" output/tables/; done

Create Example Table File

Important: Overleaf automatically deletes empty directories. To prevent the tables/ directory from being deleted, create an example table file:

# Create example table file
cat > output/tables/example-table.tex << 'EOF'
% Example table file
% Can be deleted or replaced with your own tables

\begin{table}[h]
    \centering
    \caption{Example Table}
    \label{tab:example}
    \begin{tabular}{lccc}
        \toprule
        Method & Metric 1 & Metric 2 & Metric 3 \\
        \midrule
        Baseline & 85.3 & 12.4 & 0.92 \\
        Method A & 87.1 & 11.8 & 0.95 \\
        \textbf{Ours} & \textbf{89.4} & \textbf{10.2} & \textbf{0.97} \\
        \bottomrule
    \end{tabular}
\end{table}
EOF

Notes:

  • If the original template already has table files, this step can be skipped
  • The example table is only to prevent directory deletion; it can be deleted or replaced
  • Reference tables in the paper using \input{tables/example-table.tex} or copy table content directly into section files

Copy Bibliography

# Copy .bib files
find /tmp/latex-template-temp -type f -name "*.bib" -exec cp {} output/ \;

Step 6: Generate README

Information Source Priority

  1. Conference link provided by user → Extract using WebFetch
  2. Template file comments → Extract from .tex files
  3. Default inference → Infer from \documentclass

README Template

# [Conference Name] Submission Template

## Template Information
- **Conference**: [Conference name]
- **Website**: [Conference link]
- **Template version**: [From template or website]
- **Document class**: [Extracted documentclass]

## Submission Requirements

### Page and Format
- **Page limit**: [From website or template]
- **Two-column/Single-column**: [Detect layout]
- **Font size**: [10pt/11pt etc.]

### Anonymity Requirements
- **Blind review required**: [Detect template mode]
- **Author information handling**: [Instructions]

### Compilation Requirements
- **Recommended compiler**: [XeLaTeX/pdfLaTeX/LuaLaTeX]
- **Special package requirements**: [If any]

## Overleaf Usage

### Upload Steps
1. Create a new project on Overleaf
2. Upload the entire `output/` directory
3. Set compiler to [specified compiler]
4. Click Recompile to test

### File Description
- `main.tex` - Main file, start here
- `text/` - Section content, edit as needed
- `figures/` - Place images here
- `tables/` - Place tables here
- `styles/` - Style files, no modification needed
- `references.bib` - Bibliography database

## Common Operations

### Adding Images
```latex
\begin{figure}[h]
    \centering
    \includegraphics[width=0.8\linewidth]{figures/your-image.pdf}
    \caption{Image caption}
    \label{fig:your-label}
\end{figure}

Adding Tables

\begin{table}[h]
    \centering
    \begin{tabular}{|c|c|}
        \hline
        Column 1 & Column 2 \\
        \hline
        Content 1 & Content 2 \\
        \hline
    \end{tabular}
    \caption{Table caption}
    \label{tab:your-label}
\end{table}

Adding References

Add entries to references.bib and cite in text using \cite{key}.

Notes

  • [Warnings extracted from template comments]
  • [Important notes extracted from website]

### Extract Information from Website (if user provided a link)

Use WebFetch to get conference submission page content and extract:
- Page limits
- Anonymity requirements
- Format requirements
- Submission deadlines

## Step 7: Cleanup and Output

```bash
# Clean up temporary files
rm -rf /tmp/latex-template-temp

# Output completion message
echo "Template cleanup complete! Output directory: output/"
echo "Please upload the output/ directory to Overleaf to test compilation."

Error Handling

Error ScenarioHandling Approach
Main file not foundList all .tex files, let user choose
Dependency file missingWarn user, attempt to locate from template directory
Cannot extract conference infoUse default info from template, mark as [To be confirmed]
Website inaccessibleFall back to template comments, prompt user to fill in manually
Extraction failedPrompt user to check .zip file integrity

Common Conference Template Types

ConferenceDocument ClassNotes
KDD (ACM SIGKDD)acmartAnonymous submission requires nonacm option to remove footnotes
ACM ConferencesacmartRequires anonymous mode \acmReview{anonymous}
CVPR/ICCVcvprTwo-column, strict page limits
NeurIPSneurips_2025Anonymous review, no page limit
ICLRiclr2025_conferenceTwo-column, requires session info
AAAIaaai25Two-column, 8 pages + references

KDD Anonymous Submission Configuration Notes

KDD 2026 uses the ACM acmart template and requires special configuration for anonymous submission:

Submission version (remove all ACM metadata footnotes):

\documentclass[sigconf,anonymous,review,nonacm]{acmart}
\settopmatter{printacmref=false}
\setcopyright{none}
\acmConference[]{}{}{}
\acmYear{}
\acmISBN{}
\acmDOI{}

Camera-ready version (restore ACM metadata):

\documentclass[sigconf]{acmart}
\settopmatter{printacmref=true}
\setcopyright{acmcopyright}
\acmConference[KDD '26]{...}{...}{...}
\acmYear{2026}
\acmISBN{978-1-4503-XXXX-X/26/08}
\acmDOI{10.1145/nnnnnnn.nnnnnnn}

Quick Reference

Detect Document Type

# Detect document class
grep "\\documentclass" main.tex

# Detect anonymous mode
grep -i "anonymous\|review\|blind" main.tex

# Detect page settings
grep "pagelimit\|pageLimit\|page_limit" main.tex

Common Cleanup Patterns

# Remove example files
rm -f sample-* example-* demo-* test-*

# Remove temporary files
rm -f *.aux *.log *.out *.bbl *.blg

Alternatives

Compare before choosing

Computed 9732,606

K-Dense-AI/scientific-agent-skills

biopython

Comprehensive molecular biology toolkit. Use for sequence manipulation, file parsing (FASTA/GenBank/PDB), phylogenetics, and programmatic NCBI/PubMed access (Bio.Entrez). Best for batch processing, custom bioinformatics pipelines, BLAST automation. For quick lookups use gget; for multi-service integration use bioservices.

Computed 976

mgiovani/cc-arsenal

team-review

Multi-agent review team: architecture, security, performance, testing, style, docs/UX, plus an adversary that cross-examines the other 6, for security-sensitive, architectural, or large PRs (15+ files) where a single-agent pass risks missing cross-cutting issues. Use for auth/payments/PII changes, schema/pattern changes, compliance sign-off, or when asked to 'get the review team on this' / 'multi-agent review' / 'thorough review before merge'. For a standard PR or a quick pre-merge check, use /r

Computed 9532,606

K-Dense-AI/scientific-agent-skills

markdown-mermaid-writing

Comprehensive markdown and Mermaid diagram writing skill. Use when creating any scientific document, report, analysis, or visualization. Establishes text-based diagrams as the default documentation standard with full style guides (markdown + mermaid), 24 diagram type references, and 9 document templates.

Computed 956

mgiovani/cc-arsenal

create-skill

Create a new agent skill (or Claude Code slash command) from a plain-language description, using live spec fetching, pattern research, and an approval-gated blueprint before any files are written. Use whenever the user wants to build, scaffold, or author a new skill, subagent capability, or slash command, including phrasings like 'make a command for X', 'create a slash command', 'turn this into a reusable skill', or 'package this workflow as a skill'. Not for editing CLAUDE.md/AGENTS.md memory r