overleaf-sync

Synchronize local ARIS LaTeX directories with Overleaf via Git bridge.

Updated May 29, 2026
One-click install
npx skills add https://github.com/Mang30/myskills --skill overleaf-sync-mang30
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: overleaf-sync
Source: https://github.com/Mang30/myskills/tree/main/skills/overleaf-sync
Command: npx skills add https://github.com/Mang30/myskills --skill overleaf-sync-mang30

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill solves the problem of keeping a local ARIS paper workflow in sync with a collaborative Overleaf editing workspace, so changes made in either place can be safely reflected in the other without exposing Overleaf authentication tokens to the agent.

Core Features & Use Cases

  • Two-way synchronization with safety guards: Pull Overleaf changes into the local paper/ working copy, or push local ARIS edits back to the Overleaf Git bridge clone in paper-overleaf/.
  • Diff-aware update workflow: In pull, the Skill guides you to treat numeric/citation changes differently from prose edits and to stop for structural divergences.
  • Token security via one-time user auth: Setup uses the official Overleaf Git bridge with OS keychain storage, and includes a pre-commit hook to block commits containing token patterns.

Quick Start

Run setup in your own terminal by executing: bash <ARIS_REPO>/tools/overleaf_setup.sh <project-id-or-url>.

Frequently Asked Questions about overleaf-sync

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I sync a local LaTeX repository with Overleaf without exposing my Git token?

To sync local LaTeX directories with Overleaf safely, use the Overleaf Git bridge with OS keychain storage for one-time authentication. This approach prevents split-brain edits and keeps your Overleaf token secret via a pre-commit hook that blocks token patterns.

What is the best way to handle git divergence when pulling Overleaf edits into a local paper directory?

Handling git divergence when pulling Overleaf edits requires git-based divergence checks with explicit conflict escalation. The workflow guides you to treat numeric and citation changes differently from prose edits, stopping to resolve structural divergences manually before continuing.

Can I push local ARIS paper audit results back to a shared Overleaf project?

Yes, you can push local ARIS paper audit and improvement results back to Overleaf by syncing your local working copy to the Overleaf Git bridge clone. This two-way synchronization ensures collaborators stay aligned across shared LaTeX sources.

Does Overleaf collaboration support two-way sync for local sec/ LaTeX sources?

Overleaf collaboration supports two-way sync for local LaTeX sources by using the official Overleaf Git bridge. You can pull Overleaf changes into your local working copy and push local edits back, keeping shared sec/ directories aligned without exposing tokens.

Why do I need to run a setup script before using the Overleaf Git bridge for LaTeX collaboration?

You need to run the setup script to configure the Overleaf Git bridge connection and securely store your authentication token in the OS keychain. This one-time user authentication step establishes the secure channel required for subsequent pull, push, and status commands.

What are the limitations of using an Overleaf Git bridge for local LaTeX synchronization?

The limitation of using an Overleaf Git bridge for LaTeX synchronization is that it requires explicit conflict escalation for structural divergences. You must manually stop to resolve git divergence, meaning fully automated split-brain edit prevention is not supported for conflicting structural changes.