القائمة
Use when checking LaTeX paper projects for compilation, latexmk logs, undefined references, citation issues, duplicate labels, macro/package hygiene, layout warnings, floats, arXiv, or venue compatibility.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | latex-build-and-layout-audit |
| description | Use when checking LaTeX paper projects for compilation, latexmk logs, undefined references, citation issues, duplicate labels, macro/package hygiene, layout warnings, floats, arXiv, or venue compatibility. |
Audit whether a mathematical paper can be built and submitted reliably. This skill handles mechanical LaTeX quality, not proof correctness.
.log, .blg, .bbl, or build command.Return:
.tex file.latexmk -pdf -interaction=nonstopmode -halt-on-error <root>.tex
when running a build is allowed..bbl,
figure format/engine mismatches, \include paths that write aux files below
the top directory, and policy-forbidden watermarks, referee notes, or margin
comments..sty/.cls/.bst files, figures,
supplements, code/data links, and unresolved risks..blg errors..bbl consistency, figure
format/engine fit, noninteractive build requirements, and source package
completeness.proof-obligation-and-assumption-audit or claim-evidence-ledger.Route AI4Math mathematical paper-writing tasks to the bundled paper-writing skill package.
Use when drafting, revising, or auditing source-grounded mathematical paper text, including abstracts, introductions, related work, theorem exposition, experiment narratives, revision plans, and response letters.
Use when auditing mathematical paper drafts for supported claims, missing citations, overclaims, proof status, experiment support, or source-to-text traceability.
Use when improving mathematical formulas, displayed derivations, theorem/proof environments, equation alignment, cases blocks, long displays, or formula-to-prose readability in paper drafts.
Use when checking mathematical paper drafts for notation drift, variable reuse, undefined symbols, inconsistent domains, index conventions, or scalar/vector/matrix ambiguity.
Use when turning mathematical notes, theorem statements, proof sketches, experiments, or reading outputs into a paper skeleton, section plan, result dependency map, or contribution architecture before prose drafting.