OpenParable
Skip to content
← Back to skills

Sync Tex

Documents
sync-tex

Sync Tex is an Agent Skill for documents published in the brycewang-stanford/Auto-Empirical-Research-Skills repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Transfers prose edits from latex/index.tex (Overleaf) back into index.qmd. Use after pulling LaTeX edits from a collaborator.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills/blob/HEAD/skills/29-quarcs-lab-project20XXy/dot-claude/skills/sync-tex/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/sync-tex, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

Sync LaTeX Edits to QMD

Transfer prose changes made by collaborators in latex/index.tex (e.g., via Overleaf) back into index.qmd.

Prerequisites

  • latex/.baseline.tex must exist (auto-created by bash scripts/render.sh)
  • latex/index.tex must contain collaborator edits (pulled from Overleaf / GitHub)

Steps

  1. Read these three files:

    • latex/.baseline.tex — the LaTeX snapshot from the last render (before edits)
    • latex/index.tex — the LaTeX after collaborator edits
    • index.qmd — the current QMD manuscript source
  2. Compare latex/.baseline.tex vs latex/index.tex to identify changes. Focus on the document body only (everything between \begin{document} and \end{document}). Ignore the preamble (lines before \begin{document}) — these are auto-generated by Quarto.

  3. For each section (identified by \section{...}\label{...} and \subsection{...}\label{...} markers), check if the prose text changed between baseline and modified.

  4. For each changed section, apply the edits to the corresponding section in index.qmd:

    • Convert LaTeX formatting to QMD equivalents:
      • \textbf{...} → **...**
      • \textit{...} or \emph{...} → *...*
      • \href{url}{text} → [text](url)
      • Section~\ref{sec-id} → @sec-id
      • Figure~\ref{fig-id} → @fig-id
      • Table~\ref{tbl-id} → @tbl-id
      • \cite{key} or \citep{key} → [@key]
      • \citet{key} → @key
      • Footnotes: \footnote{...} → ^[...]
    • CRITICAL: Preserve all {{< embed >}} shortcodes exactly as they are in the QMD. Do NOT replace them with \includegraphics, \begin{figure}, \begin{longtable}, or any LaTeX equivalents. These shortcodes pull live outputs from notebooks and must remain intact.
    • If a collaborator edited a figure/table caption in LaTeX (\caption{...}), note the change in the summary report but do NOT modify the embed shortcodes — captions are defined in the notebook source cells.
  5. After applying all changes, show a summary:

    • List each section that was modified
    • For each, show a brief description of what changed (e.g., "Added two sentences to Introduction", "Rewrote paragraph 2 in Methods")
    • Note any changes that could NOT be transferred (e.g., caption edits, preamble changes, new LaTeX packages)
  6. Render the manuscript with bash scripts/render.sh to verify the round-trip is clean (no warnings, no errors).

Error handling

  • If latex/.baseline.tex does not exist, tell the user to run /project:render first.
  • If latex/.baseline.tex and latex/index.tex are identical, report "No changes detected" and stop.
  • If a section label in the LaTeX does not match any section in index.qmd, flag it and skip.