skills/29-quarcs-lab-project20XXy/dot-claude/skills/sync-tex/SKILL.md
Transfers prose edits from latex/index.tex (Overleaf) back into index.qmd. Use after pulling LaTeX edits from a collaborator.
npx skillsauth add brycewang-stanford/Awesome-Agent-Skills-for-Empirical-Research sync-texInstall this skill globally with one command. Works with Claude Code, Cursor, and Windsurf.
3 of 9 scanners reported clean
Some scanners were skipped, did not run, or reported a non-clean status. Review each row below.
Transfer prose changes made by collaborators in latex/index.tex (e.g., via Overleaf) back into index.qmd.
latex/.baseline.tex must exist (auto-created by bash scripts/render.sh)latex/index.tex must contain collaborator edits (pulled from Overleaf / GitHub)Read these three files:
latex/.baseline.tex — the LaTeX snapshot from the last render (before edits)latex/index.tex — the LaTeX after collaborator editsindex.qmd — the current QMD manuscript sourceCompare 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.
For each section (identified by \section{...}\label{...} and \subsection{...}\label{...} markers), check if the prose text changed between baseline and modified.
For each changed section, apply the edits to the corresponding section in index.qmd:
\textbf{...} → **...**\textit{...} or \emph{...} → *...*\href{url}{text} → [text](url)Section~\ref{sec-id} → @sec-idFigure~\ref{fig-id} → @fig-idTable~\ref{tbl-id} → @tbl-id\cite{key} or \citep{key} → [@key]\citet{key} → @key\footnote{...} → ^[...]{{< 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.\caption{...}), note the change in the summary report but do NOT modify the embed shortcodes — captions are defined in the notebook source cells.After applying all changes, show a summary:
Render the manuscript with bash scripts/render.sh to verify the round-trip is clean (no warnings, no errors).
latex/.baseline.tex does not exist, tell the user to run /project:render first.latex/.baseline.tex and latex/index.tex are identical, report "No changes detected" and stop.index.qmd, flag it and skip.tools
Show mcp-stata identity, connected tools, and status. Use when the user asks if mcp-stata is available, asks about access to the toolkit, or asks what Stata tools are connected.
tools
Activate when users mention Stata commands, .do files, regressions, econometrics, stored results, graphs, dataset inspection, replication, or Stata errors. Route the task through mcp-stata tools and the specialized research skills instead of treating it as plain text coding.
development
Build and review paper-ready regression, balance, and summary tables from Stata outputs. Use when the user needs a clean table for a draft, appendix, or coauthor share-out.
tools
Install, configure, update, or verify mcp-stata across Claude Code, Codex, Gemini CLI, Cursor, Windsurf, and VS Code. Activate when users ask to set up the Stata toolkit or troubleshoot the installation.