snyk-vulnbench: Skill for Codex

Benchmark LaTeX Writer

Goal

Produce a clean academic LaTeX project from a benchmark report. Preserve the report's claims and tables, reshape the prose into paper structure, compile locally when possible, show a PDF preview, and package an Overleaf-ready ZIP.

Output Directory

Create a dedicated arXiv directory inside the report or benchmark folder, usually:

<report-dir>/arxiv/

Write generated files there:

• main.tex
• references.bib
• figures/ for image assets
• main.pdf after compilation
• preview-page-1.png or another first-look preview
• <slug>-overleaf-source.zip

Do not scatter LaTeX artifacts into the original report directory.

Workflow

1. Inspect the source report before writing:

   • Find the primary markdown article, benchmark JSON/JSONL, chart manifests, generated HTML reports, and existing image assets.
   • Prefer rg --files, rg, sed, and find.
   • Extract title, author metadata, actual report date, headings, tables, code snippets, links, citation targets, figure placeholders, and chart captions.

2. Create the paper structure:

   • Use \documentclass[11pt]{article}.
   • Use graphicx, booktabs, xcolor, geometry, authblk, natbib, url, listings, and lmodern.
   • Load hyperref bare, then configure links separately:

\usepackage{hyperref}
\hypersetup{colorlinks=true, citecolor=darkblue, linkcolor=darkblue, urlcolor=darkblue}

• Hardcode the date with \date{<actual date>} and immediately add \renewcommand{\today}{<actual date>}.
• Do not place a standalone \today after \maketitle.
• Use \author[1]{Name} and \affil[1]{Affiliation} with authblk.

1. Convert content with academic discipline:
   • Use abstract, Introduction, Methodology, Results, Discussion, Conclusion, and references unless the source strongly suggests another standard structure.
   • Convert markdown tables to booktabs tables without vertical rules.
   • Use \resizebox{\textwidth}{!}{...} for wide metric tables.
   • Convert fenced code blocks to lstlisting.
   • Define JavaScript explicitly before using language=JavaScript; TeX Live's listings does not always include it: