Skip to content
cccskills
FreePublished on GitHub

latex-compile-qa

Compile a LaTeX project and run basic QA (missing refs, bib errors, broken citations), producing `latex/main.pdf` and a build report.

The English summary is being prepared. Showing the original description.

Run score Not tested

See how to install

Files included (2)

  • SKILL.md2.8 KB
  • scripts/run.py9.4 KB

SKILL.md (original)

Review the instructions the agent will receive before you install.

LaTeX Compile + QA

Triggers & routing

  • Trigger: latex compile, build PDF, LaTeX errors, missing refs, 编译PDF, 引用错误.
  • Use when: 已有 latex/main.tex(通常来自 latex-scaffold),需要确认可编译并输出失败原因报告。

Compile the LaTeX project and produce a PDF (when the toolchain is available), plus a short build report.

This step is deterministic; if compilation fails, record actionable diagnostics rather than guessing.

Inputs

  • latex/main.tex
  • citations/ref.bib

Outputs

  • latex/main.pdf (if compilation succeeds)
  • output/LATEX_BUILD_REPORT.md (recommended)

Workflow

  1. Run a LaTeX build (e.g., latexmk) if available.
  2. Fix missing packages, missing bib entries, and unresolved references.
  3. Record remaining issues in a build report.

Quality checklist

  • latex/main.pdf exists only when compilation succeeds; failed builds must remove stale PDFs and explain the failure in output/LATEX_BUILD_REPORT.md.
  • For arxiv-survey-latex deliverables: latex/main.pdf is >= 8 pages and has no undefined citations/references (strict gate).

Script

Quick Start

  • uv run python .codex/skills/latex-compile-qa/scripts/run.py --help
  • uv run python .codex/skills/latex-compile-qa/scripts/run.py --workspace <workspace>

All Options

  • See --help (inputs/outputs are taken from the unit runner when used via pipeline)

Examples

  • Compile + produce report:
    • uv run python .codex/skills/latex-compile-qa/scripts/run.py --workspace <workspace>

Notes

  • Uses latexmk -xelatex -bibtex when available.
  • Always writes output/LATEX_BUILD_REPORT.md (success or failure).
  • Report includes page count + warning summary when available.

Troubleshooting

Common Issues

Issue: latexmk not found

Symptom:

  • Build report says “latexmk not found in PATH”.

Causes:

  • LaTeX toolchain is not installed.

Solutions:

  • Install a TeX distribution that includes latexmk.
  • If you can’t install tools, still use latex-scaffold to generate latex/main.tex and compile elsewhere.

Issue: Build fails with bib/ref errors

Symptom:

  • Report shows missing citations/refs or BibTeX errors.

Causes:

  • citations/ref.bib missing/miswired, or draft contains invalid cite keys.

Solutions:

  • Ensure latex/main.tex points to ../citations/ref.bib (or the correct relative path).
  • Ensure all citation keys exist in citations/ref.bib.

Recovery Checklist

  • Read output/LATEX_BUILD_REPORT.md tail for the first actionable error.
  • Confirm latex/main.tex exists and bibliography path is correct.

Reviews

No reviews yet. Tell others what you thought.

Comments

No login needed. Share how it worked for you, ask a question, or note where it did not run.

No comments yet. Be the first to write one.

Comments are published right away. Do not include personal information such as email addresses or phone numbers. Up to 2 URLs.

0 / 1,000 characters

This form is protected by reCAPTCHA, and the Google Privacy Policy and Terms of Service apply.

More skills from this repository

Internal template for creating or refactoring a skill into the repository's reference-first shape. **Trigger**: reference-first template, blueprint skill, create a reusable skill, refactor a script-heavy skill. **Use when**: you need a lean `SKILL.md`, explicit `references/`, machine-readable `assets/`, and a minimal deterministic `run.py`.

The English summary is being prepared. Showing the original description.

WILLOSCAR/research-units-pipeline-skills515Updated Oct 5, 2026

Download a small corpus of open-access arXiv survey/review PDFs about agentic systems and extract text for style learning.

The English summary is being prepared. Showing the original description.

WILLOSCAR/research-units-pipeline-skills515Updated Oct 5, 2026

Extract per-subsection “anchor facts” (NO PROSE) from evidence packs so the writer is forced to include concrete numbers/benchmarks/limitations instead of generic summaries.

The English summary is being prepared. Showing the original description.

WILLOSCAR/research-units-pipeline-skills515Updated Oct 5, 2026

Curate reader-facing survey tables for the Appendix (clean layout + high information density), using only in-scope evidence and existing citation keys.

The English summary is being prepared. Showing the original description.

WILLOSCAR/research-units-pipeline-skills515Updated Oct 5, 2026

Build a final, machine-readable argument snapshot from current H3 sections and refresh section fingerprints before merge.

The English summary is being prepared. Showing the original description.

WILLOSCAR/research-units-pipeline-skills515Updated Oct 5, 2026

Audit one research Workspace for declared Unit outputs and Pipeline target Artifacts, writing `output/CONTRACT_REPORT.md`; use for mid-Run coverage snapshots or final delivery completeness, not deep provenance integrity.

The English summary is being prepared. Showing the original description.

WILLOSCAR/research-units-pipeline-skills515Updated Oct 5, 2026

See all skills by WILLOSCAR

Report a problem with this skill