agentsclimarketplace

Latex camera ready

Skill StaryMoon/latex-camera-ready-skill/skills/latex-camera-ready

Agent Skill that audits LaTeX projects for camera-ready and arXiv delivery risks.

Install
npx -y skills add StaryMoon/latex-camera-ready-skill --skill latex-camera-ready

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • 23 days oldThe repository was created 23 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Audit a LaTeX paper project for unresolved references, missing graphics, duplicate labels, missing bibliography keys, TODO markers, anonymous placeholders, risky absolute paths, and compile-log warnings. Use before conference submission, arXiv upload, camera-ready delivery, or sharing a reproducible paper source package.

SKILL.md

1.7 KB, as published. Nobody here has run it

LaTeX Camera Ready

Protect the last known compiling version before editing. Run the deterministic audit first, then fix one issue class at a time and compile after each group of changes.

Workflow

  1. Locate the authoritative main .tex file and preserve the working tree state.
  2. Run the audit from the project root:
python3 scripts/audit_latex_project.py . --main main.tex --output output/camera-ready-audit
  1. Read report.md. Errors block delivery; warnings require judgment.
  2. Fix missing graphics, duplicate labels, undefined references, and missing citation keys before stylistic cleanup.
  3. Compile with the repository's existing command. Do not change engines or bibliography tools casually.
  4. Re-run the audit and compare audit.json issue counts.

Quality rules

  • Never delete a TODO merely to make the audit green; resolve or explicitly waive it.
  • Distinguish a missing citation key from a bibliography entry that is merely unused.
  • Resolve graphics relative to the file containing \includegraphics and the project root.
  • Treat absolute user paths as packaging failures.
  • Keep author/anonymity checks aligned with the target venue phase.
  • Do not claim compilation success unless a fresh compile command exits zero.

See references/release-gates.md for the recommended gate order.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.