
Overleaf Sync
Keeps a local paper folder and an Overleaf project in two-way sync for ARIS audit workflows.
- Stars
- 18,482
- Licence
- MIT
- Files
- 1 file
What it does
It connects a local folder holding your LaTeX paper with an Overleaf project through Overleaf's official Git bridge, so you can keep editing in the Overleaf web editor while automated audit tools run on your local copy. When you pull, the agent shows what collaborators changed and asks which edits to bring in. When you push, it copies your local edits into the Overleaf clone, shows the changes, and commits and pushes them only after you confirm.
Great for
- Researchers who write papers in Overleaf with co-authors and also run ARIS audit tools locally
- Users who want to move an existing local LaTeX paper into an Overleaf project for a collaborator
- Teams that need a reviewed merge step before remote edits reach the working copy
Skip it if
- Users without an Overleaf Premium account, since the skill relies on the Premium Git bridge
- Anyone who wants fully automatic syncing with no review, because pushes to a shared project are gated on confirmation and half-finished collaborator edits are flagged rather than merged
- Users who are not on macOS or Windows or Linux with a working credential helper, since the token storage depends on those systems
Try asking
- “Set up an Overleaf sync for my paper folder using project ID abc123”
- “Pull the latest Overleaf changes and show me what my co-author edited”
- “Push my audited paper changes to Overleaf with a clear commit message”
- “Check whether my local paper and the Overleaf project have diverged”
Install in 3 steps
- 1
Download the skill
The ZIP contains the 1 original files, the MIT licence and an attribution note.
overleaf-sync.zip - 2
Add it to your agent
Claude Code (all projects)
mkdir -p ~/.claude/skills && unzip overleaf-sync.zip -d ~/.claude/skills/Claude Code / Agent SDK (this project only)
mkdir -p .claude/skills && unzip overleaf-sync.zip -d .claude/skills/Claude apps (web/desktop): Settings → Capabilities → Skills → Upload skill, and choose the ZIP.
- 3
Ask for the task
No special command needed — the agent reads the skill's description and loads it when your request matches. Try one of the prompts above.
Get better results
- Run the setup script yourself in a terminal, not through the agent, so the token never enters chat history.
- Review the git diff --stat and sample hunks before confirming any push, since pushes write to a shared project.
- Run pull before each editing session so you see collaborator changes before local edits pile up.
What's inside
- SKILL.md
Redistributed unmodified from wanshuiyin/Auto-claude-code-research-in-sleep under the MIT licence. The assessment was drafted with AI from the skill's files on 2026-10-29. Skills can instruct your agent to run code — read SKILL.md and any scripts before installing.