Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Sync and manage Overleaf LaTeX projects from the command line. Pull projects locally, push changes back, compile PDFs, and download compile outputs like .bbl files for arXiv submissions. Use when working with LaTeX, Overleaf, academic papers, or arXiv.
Sync and manage Overleaf LaTeX projects from the command line. Pull projects locally, push changes back, compile PDFs, and download compile outputs like .bbl files for arXiv submissions. Use when working with LaTeX, Overleaf, academic papers, or arXiv.
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Then review README.md for any prerequisites, environment setup, or post-install checks. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Then review README.md for any prerequisites, environment setup, or post-install checks. Summarize what changed and any follow-up checks I should run.
Manage Overleaf LaTeX projects via the olcli CLI.
# Homebrew (recommended) brew tap aloth/tap && brew install olcli # npm npm install -g @aloth/olcli
Get your session cookie from Overleaf: Log into overleaf.com Open DevTools (F12) โ Application โ Cookies Copy the value of overleaf_session2 olcli auth --cookie "YOUR_SESSION_COOKIE" Verify with: olcli whoami Debug authentication issues: olcli check Clear stored credentials: olcli logout
olcli pull "My Paper" cd My_Paper/
# After editing files locally olcli push # Upload changes only olcli sync # Bidirectional sync (pull + push)
olcli pdf # Compile and download olcli pdf -o paper.pdf # Custom output name olcli compile # Just compile (no download)
olcli output bbl # Download compiled .bbl olcli output bbl -o main.bbl # Custom filename olcli output --list # List all available outputs
olcli upload figure1.png "My Paper" # Upload to project root olcli upload diagram.pdf # Auto-detect project from .olcli.json
olcli download main.tex "My Paper" # Download single file olcli zip "My Paper" # Download entire project as zip
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
CommandDescriptionolcli auth --cookie <value>Authenticate with session cookieolcli whoamiCheck authentication statusolcli logoutClear stored credentialsolcli checkShow config paths and credential sourcesolcli listList all projectsolcli info [project]Show project detailsolcli pull [project] [dir]Download project filesolcli push [dir]Upload local changesolcli sync [dir]Bidirectional syncolcli upload <file> [project]Upload a single fileolcli download <file> [project]Download a single fileolcli zip [project]Download as zip archiveolcli compile [project]Trigger compilationolcli pdf [project]Compile and download PDFolcli output [type]Download compile outputs
Auto-detect project: Run commands from a synced directory (contains .olcli.json) to skip the project argument Dry run: Use olcli push --dry-run to preview changes before uploading Force overwrite: Use olcli pull --force to overwrite local changes Project ID: You can use project ID instead of name (24-char hex from URL) Debug auth: Run olcli check to see where credentials are loaded from
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.