latex-paper-writer

LaTeX Paper Writer Skill

Use this skill when the user wants a scientific paper, survey, technical report, research-derived PDF summary, LaTeX experiment table, or edits to an existing LaTeX document.

This is the canonical OpenColab path for paper production. Research, grounding, figure extraction, and architecture diagrams stay delegated to the existing shared skills; this skill owns the LaTeX workspace, document structure, template selection, scoped Git version control, PDF compilation, validation, and final delivery packaging.

Mission

Given source material for a scientific document:

1. Select or preserve the right LaTeX template.
2. Create or reuse a Git-controlled paper workspace.
3. Draft or edit the LaTeX sources with grounded claims and citations.
4. Generate experiment tables when useful.
5. Add user-supplied, extracted, or generated figures when they clarify the paper.
6. Build and validate the PDF.
7. Create scoped Git checkpoints when the paper has meaningful changes.
8. Return the final PDF path, and emit a raw Telegram file directive when needed.

Prerequisites

• git is installed and available in PATH.
• python3 is installed and available in PATH.
• latexmk is preferred for PDF builds:

latexmk -v

If latexmk is missing, read references/document-types.md for install guidance and do not claim that compilation succeeded. Only run install commands after the user explicitly approves installing system packages.

Hard Requirements

• Read references/conference-map.md before choosing a venue template.
• Read references/citation-policy.md before writing claims from papers.
• Read references/deep-research-integration.md when converting research outputs into a PDF summary or survey.
• Read references/experiment-tables.md before generating result tables.
• Use the existing paper's template and macros when editing an existing paper.
• Treat ICLR as the canonical venue name; infer it from near misses such as ICRL only when context makes that clear, and mention the correction briefly.
• Do not claim official venue-template compliance unless the official template is bundled, user-supplied, or otherwise verified.
• Keep every generated or managed paper workspace under Git version control.
• Never stage or commit unrelated files outside the paper workspace.
• Inspect git status before editing an existing paper repository.
• Use pdf-figure-extract for figures from already-downloaded local PDFs.
• Use block-diagram for synthesized architecture, taxonomy, pipeline, or literature-map diagrams.
• Use pageindex-grounded for exact local evidence checks over downloaded papers when a technical claim needs verification.
• Do not fabricate citations, metadata, benchmark values, or architecture details.
• When sending a PDF through Telegram, emit a raw @telegram-file {"kind":"document","file":"<path>","caption":"optional"} line on its own line with no code fence. Keep the JSON on one line, keep kind as document, and on Windows write the path with forward slashes.