What problem does it solve? Writing ML and scientific papers involves fragile coordination between LaTeX source, generated figures and tables, citation tooling, and external hosts like Overleaf. This Skill sets the safety and portability boundaries for that work: it prevents agents from editing human-owned .tex files, keeps synced manuscript directories compile-standalone, and provides the exact git subtree procedures for Overleaf bridges that reject force-pushes and non-fast-forward updates. ## Core Features & Use Cases - Human-owned .tex guardrail: Agents read, compile, and review LaTeX but never edit .tex directly; edits are delivered as proposals in planning notes or scaffold scripts the human runs. - Overleaf git bridge sync: One-time subtree re-seed for pre-existing subdirectories, recurring push-then-pull rules, conflict diagnosis, and post-push scope checks confirming no parent-repo paths leak to the host. - Portable manuscript boundary: Rules for compile-standalone directories, committed generated figures/tables as the pipeline interface, byte-deterministic artifacts, and reference self-containment for arXiv and coauthor handoff. - Use Case: A researcher's git subtree push to Overleaf is rejected as non-fast-forward. The Skill walks through the one-time re-seed (git rm, subtree add, restore, push), then wires make overleaf-push to push-then-pull so shared ancestry advances and future syncs stay clean. ## Quick Start Ask the agent to set up a synced manuscript directory for your research project, including the claims ledger, build targets, and Overleaf subtree sync procedure.
