overleaf skill
✓ VerifiedSync and manage Overleaf LaTeX projects from the command line using the olcli tool.
- GitHub stars
- 25
- Files
- 5
- Last commit
- Nov 7, 2026
- License
- MIT
- Allowed tools
- —
What does the overleaf skill do?
overleaf syncs and manage Overleaf LaTeX projects from the command line using the olcli tool.
Summary generated from the skill's SKILL.md.
About the overleaf skill
Managing LaTeX projects from a local terminal is what researchers and academics achieve using this skill. It provides an interface to the olcli tool, allowing users to pull Overleaf projects to their local machines, push local edits back to the cloud, or perform bidirectional synchronization. This is particularly useful for those who prefer local text editors or need to manage complex academic papers and arXiv submissions.
An agent should load this skill when a user needs to synchronize LaTeX files, compare local versions against the cloud using unified diffs, or generate marked-up latexdiff PDFs. The skill relies on the olcli command-line interface and can be authenticated via a browser or a session cookie. It enables advanced workflows such as using Overleaf as a git remote, compiling projects remotely, and downloading specific compiled outputs like .bbl files required for journal submissions.
What an agent can do with it
- 1Synchronize local LaTeX editsPull a project from Overleaf to a local directory to edit files in a preferred local editor.
- 2Prepare arXiv submissionsDownload the compiled .bbl file and other necessary outputs to package a complete submission for arXiv.
- 3Compare document revisionsGenerate a marked-up PDF that highlights the differences between local files and the current Overleaf version.
- 4Manage projects with GitConfigure Overleaf as a git remote to pull coauthors' edits and commit changes using standard git commands.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the overleaf skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the overleaf skill in Claude Code
~/.claude/skills/overleaf/SKILL.md
$ npx degit aloth/overleaf-skill ~/.claude/skills/overleafInstall the overleaf skill in Claude Code (project)
.claude/skills/overleaf/SKILL.md
$ npx degit aloth/overleaf-skill .claude/skills/overleafInstall the overleaf skill in Codex
~/.agents/skills/overleaf/SKILL.md
$ npx degit aloth/overleaf-skill ~/.agents/skills/overleafInstall the overleaf skill in Gemini CLI
~/.gemini/skills/overleaf/SKILL.md
$ npx degit aloth/overleaf-skill ~/.gemini/skills/overleafInstall the overleaf skill in Claude.ai
npx degit aloth/overleaf-skill overleaf && zip -r overleaf.zip overleaf # claude.ai → Customize → Skills → + → Create skill → Upload a skill → overleaf.zip
Automated checks
Ran Nov 14, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work · What to fix for more points
- Source repository linked and reachablealoth/overleaf-skill is public and reachablegithub.com/aloth/overleaf-skill/tree/HEAD ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-07github.com/aloth/overleaf-skill/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/aloth/overleaf-skill/blob/HEAD/SKILL.md ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/aloth/overleaf-skill/blob/HEAD/SKILL.md ↗Pass
- SKILL.md follows the Agent Skills formatname "overleaf" differs from the folder "overleaf-skill"github.com/aloth/overleaf-skill/blob/HEAD/SKILL.md ↗Finding
SKILL.md
View on GitHubOverleaf Skill
Manage Overleaf LaTeX projects via the olcli CLI.
Installation
# Homebrew (recommended)
brew tap aloth/tap && brew install olcli
# npm
npm install -g @aloth/olcli
Authentication
Sign in once through a browser window (needs olcli 0.16 or newer and Node 22 or newer). Works with SSO and two-factor logins; olcli keeps only the session cookie:
olcli auth --browser
Without a display (a server, a container), paste the session cookie instead: log into overleaf.com, open DevTools (F12), Application, Cookies, and copy the value of overleaf_session2:
olcli auth --cookie "YOUR_SESSION_COOKIE"
Check the setup (exits 1 when not signed in, so olcli auth status || olcli auth --browser signs in only when needed):
olcli auth status
Clear stored credentials:
olcli logout
Common Workflows
Pull a project to work locally
olcli pull "My Paper"
cd My_Paper/
Edit and sync changes
# After editing files locally
olcli push # Upload changes only
olcli sync # Bidirectional sync (pull + push)
See what a push would change
olcli diff # unified diff against Overleaf as it is right now
olcli diff --name-only # just the changed paths
olcli diff --latexdiff --pdf # marked-up PDF of the revision, compiled on Overleaf
olcli push replaces whole files on Overleaf. Run olcli diff first when coauthors edit the same project.
Use Overleaf as a git remote
git clone overleaf::https://www.overleaf.com/project/<id> paper
cd paper
git pull # bring in coauthors' edits
git commit -am "Rewrite results"
git push # refused while Overleaf has edits you have not pulled
Needs olcli 0.16.1 or newer. If a push is refused, run git pull, resolve any conflict, commit and push again. git push --force overwrites Overleaf on purpose.
Compile and download PDF
olcli pdf # Compile and download
olcli pdf -o paper.pdf # Custom output name
olcli compile # Just compile (no download)
Download .bbl for arXiv submission
olcli output bbl # Download compiled .bbl
olcli output bbl -o main.bbl # Custom filename
olcli output --list # List all available outputs
Upload figures or assets
olcli upload figure1.png "My Paper" # Upload to project root
olcli upload diagram.pdf # Auto-detect project from .olcli.json
Download specific files
olcli download main.tex "My Paper" # Download single file
olcli zip "My Paper" # Download entire project as zip
arXiv Submission Workflow
Complete workflow for preparing an arXiv submission:
# 1. Pull your project
olcli pull "Research Paper"
cd Research_Paper
# 2. Compile to ensure everything builds
olcli compile
# 3. Download the .bbl file (arXiv requires .bbl, not .bib)
olcli output bbl -o main.bbl
# 4. Download any other needed outputs
olcli output aux -o main.aux # If needed
# 5. Package for submission
zip arxiv.zip *.tex main.bbl figures/*.pdf
# 6. Verify the package compiles locally (optional)
# Then upload arxiv.zip to arxiv.org
Commands Reference
| Command | Description |
|---|---|
olcli auth --browser |
Sign in through a browser window |
olcli auth --cookie <value> |
Authenticate with session cookie |
olcli auth status |
Check authentication status and credential source |
olcli logout |
Clear stored credentials |
olcli list |
List all projects |
olcli info [project] |
Show project details |
olcli pull [project] [dir] |
Download project files |
olcli push [dir] |
Upload local changes |
olcli sync [dir] |
Bidirectional sync |
olcli diff [project] [dir] |
Diff local files against Overleaf (--latexdiff --pdf for a marked-up PDF) |
olcli upload <file> [project] |
Upload a single file |
olcli download <file> [project] |
Download a single file |
olcli zip [project] |
Download as zip archive |
olcli compile [project] |
Trigger compilation |
olcli pdf [project] |
Compile and download PDF |
olcli output [type] |
Download compile outputs |
Tips
- Auto-detect project: Run commands from a synced directory (contains
.olcli.json) to skip the project argument - Dry run: Use
olcli push --dry-runto preview changes before uploading - Force overwrite: Use
olcli pull --forceto overwrite local changes - Project ID: You can use project ID instead of name (24-char hex from URL)
- Debug auth: Run
olcli auth statusto see the account and where credentials are loaded from - Before a push: Run
olcli diffto see what the push would overwrite
Files in this skill
5overleaf skill questions
How do I install the overleaf skill in Claude Code?
Run npx degit aloth/overleaf-skill ~/.claude/skills/overleaf. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the overleaf skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
How do I authenticate with olcli on a server without a browser?
You can authenticate by pasting your session cookie from Overleaf. Log into overleaf.com, copy the 'overleaf_session2' cookie from DevTools, and use the command: olcli auth --cookie "YOUR_SESSION_COOKIE".
How can I prepare files for an arXiv submission?
You can pull your project, compile it, and then use the command 'olcli output bbl' to download the required .bbl file.