work-with-overleaf
Installation
SKILL.md
Work With Overleaf
Most academics keep their .tex in Overleaf, not on disk — so this skill gets an Overleaf project into a local working copy the rest of the toolkit can act on (preflight-check, polish-prose, verify-citations, match-style, …), then helps sync the changes back. It's the on-ramp; the other skills do the work.
Pick the path that matches the account
Overleaf exposes three ways to move a project in and out. Re-verify the current method and whether it's premium before relying on it against Overleaf's live documentation, because account features and menu names can change. As of the last check:
| Path | Who | How |
|---|---|---|
| Git integration (recommended) | Premium / Server Pro 4.0+ | Project → Menu → Git; copy the git clone https://git.overleaf.com/<id> command. Authenticate with an Overleaf token (token-based auth). Work locally, then git pull / git push. Branch is main (older clones may be master). |
| GitHub synchronization | Premium | Link the project to a GitHub repo (Menu → GitHub); sync both ways. Run the skills on the GitHub clone you already have locally. |
| Download ZIP | Free (everyone) | Menu → Download → Source. Work locally; there is no auto-merge — re-upload changed files in the Overleaf editor, or paste edits back. Best for a one-shot check. |
If the user isn't sure which they have, ask; don't assume premium.