overleaf-sync

Synchronize a local ARIS paper directory with an Overleaf project via a git bridge.

Updated Jun 10, 2026
One-click install
npx skills add https://github.com/xqinag/ARIS-new --skill overleaf-sync-xqinag
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: overleaf-sync
Source: https://github.com/xqinag/ARIS-new/tree/main/skills/overleaf-sync
Command: npx skills add https://github.com/xqinag/ARIS-new --skill overleaf-sync-xqinag

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Synchronizes a local ARIS paper directory with an Overleaf project through a git bridge so collaborators can edit in Overleaf while ARIS runs audits locally. It keeps sensitive tokens out of chat history and files by requiring a one-time auth via the macOS Keychain, and it provides a hardened setup that installs a pre-commit hook to block token leakage.

Core Features & Use Cases

  • Two-way sync: keeps paper/ and paper-overleaf/ in sync with a clear source-of-truth flow.
  • Secure auth workflow: token never leaves the user's machine, stored in the OS keychain after setup.
  • Audits and provenance: ARIS can audit papers on local disk and in Overleaf, with guided commands for diff and review.
  • Setup and automation: includes a setup script, audit script, and hooks to enforce security.

Quick Start

Run the setup script in your terminal to configure the Overleaf bridge, then follow the pull-before-edit and push-after-edit workflow.

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 paper directory with Overleaf for collaborative editing?

Two-way sync keeps your local paper directory aligned with an Overleaf project through a git bridge. You run a setup script to configure the bridge, then follow a pull-before-edit and push-after-edit workflow to keep both versions consistent.

How does secure token handling work for Overleaf git bridge authentication?

Secure token handling stores your Overleaf credentials directly in the OS keychain during a one-time setup. The token never leaves your machine or enters chat history, and a pre-commit hook blocks any accidental token exposure in files.

Can I run local audits on papers while collaborating in Overleaf?

Yes, ARIS runs audits on papers stored locally and in Overleaf. The sync bridge keeps the local directory updated with collaborator changes, enabling you to execute audit scripts and review diffs before pushing local edits back to Overleaf.

What is the best way to prevent token leakage when syncing to Overleaf via git?

The hardened setup installs a pre-commit hook that automatically blocks token leakage. Combined with storing credentials in the OS keychain, this ensures sensitive tokens remain out of your files and commit history during synchronization.

Does two-way Overleaf sync require storing credentials in the macOS Keychain?

Yes, the secure auth workflow requires a one-time setup that stores your Overleaf token in the OS keychain. This approach keeps credentials out of plain files and chat history while allowing automated synchronization scripts to authenticate securely.

Why use a git bridge for Overleaf paper management instead of direct web editing?

A git bridge enables local auditing and provenance checks while maintaining collaborative editing in Overleaf. It establishes a clear source-of-truth flow between local and remote directories, allowing controlled syncing and diff reviews before committing changes.