Agent skill

Overleaf CLI Guide

by wentorai in wentorai/research-plugins

Sync and manage Overleaf LaTeX projects from the command line

MITAuto-check passedDocuments & Office

Install Overleaf CLI Guide

skills CLI
$ npx skills add wentorai/research-plugins --skill overleaf-cli-guide -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install wentorai/research-plugins overleaf-cli-guide --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .claude/skills && cp -r skills-src/skills/tools/code-exec/overleaf-cli-guide .claude/skills/overleaf-cli-guide && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
overleaf-cli-guide
GitHub stars
298
Used in
1 other repo
Token cost
~1.9k tokens
SKILL.md length
340 words
Files
1
Skills in repo
428
Repo updated
First seen
Licence
MIT

At a glance

Sync and manage Overleaf LaTeX projects from the command line

  • Tasks that involve LaTeX
  • SKILL.md covers Overview, Overleaf Git Bridge, Open-Source Sync Tools and Automation Workflows, plus 4 more sections
  • Calls git and pip; reaches git.overleaf.com

What it does

Overleaf CLI Guide is an agent skill from wentorai/research-plugins. Sync and manage Overleaf LaTeX projects from the command line

Its SKILL.md is about 1.9k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering LaTeX. It works with LaTeX and Git. The repository describes itself as: 350+ academic research skills, MCP configs, and plugins for Research-Claw and AI agents. The licence is MIT.

When your agent uses it

  • Tasks that involve LaTeX

Example prompts

  • “/overleaf-cli-guide”

Requirements

  • Python 3

What it can do on your machine

Read from SKILL.md and the folder at commit bf44b3c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • git
    • pip

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    Hosts in commands or code, which the agent is likely to contact:

    • git.overleaf.com

    Also links to:

    • github.com
    • overleaf.com
    • mg.readthedocs.io

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Overleaf CLI Guide loads about 1.9k tokens when it runs. Until then it costs about 20 tokens; SKILL.md has 340 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~20
When it runs · the whole SKILL.md, loaded when a task matches
~1.9k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from wentorai/research-plugins at commit bf44b3c, republished under its MIT licence (© wentorai). 340 words, ~1,852 tokens.

Download SKILL.mdSave it as .claude/skills/overleaf-cli-guide/SKILL.md (or your agent's skills folder).
name
overleaf-cli-guide
description
Sync and manage Overleaf LaTeX projects from the command line

Overleaf CLI Guide

Sync, manage, and automate Overleaf LaTeX projects from the command line. Work in your preferred local editor while keeping Overleaf as the collaboration and compilation hub for your research team.

Overview

Overleaf is the dominant online LaTeX editor in academia, used by millions of researchers for collaborative paper writing. However, many researchers prefer local editors (VS Code, Neovim, Emacs) for their superior editing capabilities, version control integration, and ability to run custom scripts. The Overleaf CLI bridge enables a hybrid workflow: edit locally with full tooling, then sync changes to Overleaf for collaboration and compilation.

This skill covers three approaches to Overleaf CLI integration: Overleaf's built-in Git bridge (available on paid plans), the open-source overleaf-sync tool (works with free plans), and direct API interaction. Each approach has different trade-offs in terms of cost, features, and reliability.

Beyond simple sync, this guide covers automation workflows that are particularly valuable for research: automated bibliography updates from reference managers, figure regeneration from data analysis scripts, CI-based PDF compilation, and multi-author merge conflict resolution.

Overleaf Git Bridge

Overleaf Server Pro and paid plans include a Git bridge that exposes each project as a Git repository.

Setup
bash
# Clone your Overleaf project (requires paid plan)
git clone https://git.overleaf.com/YOUR_PROJECT_ID my-paper
cd my-paper

# The remote is already configured
git remote -v
# origin  https://git.overleaf.com/YOUR_PROJECT_ID (fetch)
# origin  https://git.overleaf.com/YOUR_PROJECT_ID (push)
Daily Workflow
bash
# Pull latest changes from collaborators
git pull origin master

# Edit locally in your preferred editor
vim main.tex

# Push changes back to Overleaf
git add -A
git commit -m "Revise methodology section"
git push origin master
Conflict Resolution

When collaborators edit the same section simultaneously:

bash
git pull origin master
# If conflicts occur:
# 1. Open conflicted files
# 2. Resolve LaTeX merge conflicts (look for <<<<<<< markers)
# 3. Verify the document compiles
git add -A
git commit -m "Resolve merge conflict in results section"
git push origin master

Open-Source Sync Tools

overleaf-sync (Python)

For free Overleaf accounts without Git bridge access:

bash
# Install
pip install overleaf-sync

# Login (stores credentials securely)
ols login

# List your projects
ols list

# Download a project
ols download "My Research Paper" --path ./my-paper

# Upload local changes
ols upload ./my-paper --project "My Research Paper"

# Two-way sync (pull then push)
ols sync ./my-paper --project "My Research Paper"
Automated Sync Script
bash
#!/bin/bash
# sync-overleaf.sh - Run periodically or before/after editing sessions

PROJECT_DIR="$1"
PROJECT_NAME="$2"

echo "Pulling latest from Overleaf..."
ols download "$PROJECT_NAME" --path "$PROJECT_DIR" --skip-existing

echo "Compiling locally to verify..."
cd "$PROJECT_DIR"
latexmk -pdf -interaction=nonstopmode main.tex

if [ $? -eq 0 ]; then
    echo "Compilation successful. Pushing to Overleaf..."
    ols upload "$PROJECT_DIR" --project "$PROJECT_NAME"
else
    echo "Compilation failed. Fix errors before syncing."
    exit 1
fi

Automation Workflows

Auto-Update Bibliography from Zotero
python
import subprocess
from pathlib import Path

def sync_bibliography(zotero_lib_id, bib_file, project_dir):
    """Export Zotero library and sync to Overleaf project."""
    # Export from Zotero using Better BibTeX
    subprocess.run([
        "curl", "-s",
        f"http://localhost:23119/better-bibtex/export/library?/"
        f"{zotero_lib_id}/library.biblatex",
        "-o", str(Path(project_dir) / bib_file)
    ])
    print(f"Updated {bib_file} from Zotero library {zotero_lib_id}")
Auto-Regenerate Figures from Data
python
import subprocess
from pathlib import Path

def regenerate_figures(scripts_dir, figures_dir):
    """Run all figure generation scripts and update outputs."""
    scripts = sorted(Path(scripts_dir).glob("fig_*.py"))
    for script in scripts:
        print(f"Running {script.name}...")
        subprocess.run(["python", str(script)], cwd=figures_dir)

    print(f"Regenerated {len(scripts)} figures in {figures_dir}")
CI/CD PDF Compilation
yaml
# .github/workflows/compile-paper.yml
name: Compile LaTeX Paper
on:
  push:
    branches: [main]
    paths: ['**.tex', '**.bib', '**.sty']

jobs:
  compile:
    runs-on: ubuntu-latest
    container:
      image: texlive/texlive:latest
    steps:
      - uses: actions/checkout@v4
      - name: Compile PDF
        run: |
          latexmk -pdf -interaction=nonstopmode main.tex
      - name: Upload PDF
        uses: actions/upload-artifact@v4
        with:
          name: paper-pdf
          path: main.pdf
      - name: Check for warnings
        run: |
          grep -i "warning" main.log | grep -v "Font" || true

Project Organization

Recommended directory structure for CLI-managed Overleaf projects:

my-paper/
  main.tex              # Main document
  sections/
    01-introduction.tex
    02-related-work.tex
    03-methodology.tex
    04-results.tex
    05-discussion.tex
    06-conclusion.tex
  figures/
    fig1-architecture.pdf
    fig2-results.pdf
  tables/
    tab1-comparison.tex
  references.bib
  custom.sty            # Custom LaTeX macros
  scripts/              # Not synced to Overleaf
    fig_architecture.py
    fig_results.py
    sync.sh
  .gitignore
.gitignore for LaTeX Projects
gitignore
# LaTeX build artifacts
*.aux
*.bbl
*.blg
*.fdb_latexmk
*.fls
*.log
*.out
*.synctex.gz
*.toc

# Local scripts (don't sync to Overleaf)
scripts/

# OS files
.DS_Store

Editor Integration

VS Code

Install the "LaTeX Workshop" extension and configure local compilation:

json
{
  "latex-workshop.latex.tools": [
    {
      "name": "latexmk",
      "command": "latexmk",
      "args": ["-pdf", "-interaction=nonstopmode", "%DOC%"]
    }
  ]
}
Neovim with VimTeX
lua
-- init.lua
vim.g.vimtex_compiler_method = 'latexmk'
vim.g.vimtex_view_method = 'skim'  -- macOS

Troubleshooting

IssueSolution
Git push rejectedPull first, resolve conflicts, then push
Sync tool authentication errorRe-run login, check 2FA settings
Compilation differs locally vs OverleafMatch TeX Live versions; Overleaf uses TeX Live 2024
Binary files (images) cause large diffsUse .gitattributes to mark as binary
Overleaf rate limitingAdd delays between API calls, use Git bridge if available

References

© wentorai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in skills/tools/code-exec/overleaf-cli-guide of wentorai/research-plugins.

Open the folder on GitHubat commit bf44b3c

Used in 1 other repository

We found 1 copy of this SKILL.md (exact, near-identical or edited) in other folders, from 1 other GitHub owner. This page covers the copy in wentorai/research-plugins, which our catalogue first saw on October 7, 2026.

Compare with similar skills

Overleaf CLI Guide next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Overleaf CLI Guide compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Overleaf CLI Guide this skillwentorai/research-plugins2981 repos~1.9kAutomated safety check: PassMIT
Oleafly Response LetterOleafly/Oleafly205—~2.3kAutomated safety check: PassMIT
Write Paperfrenzymath/Danus471—~18kAutomated safety check: PassApache-2.0
ProjectHurricaHjz/second-yourself113—~3.1kAutomated safety check: PassMIT
Review Overleaffcakyon/claude-codex-settings1.2k—~940Automated safety check: PassApache-2.0
Latex Diffflonat/flonat-research145—~1.9kAutomated safety check: PassMIT

Similar skills

  • Turn reviewer comments and the changes already made into a point-by-point response letter, in LaTeX or Typst and in plain text.

    205 GitHub stars~2.3k tokensUpdated today
    Documents & OfficeAuto-check passed
  • Write Paper

    frenzymath/Danus

    Turn a project's verified fact graph into a publishable LaTeX paper in a configurable house style — a standalone amsart .tex with a real bibliography, compiled to PDF.

    471 GitHub stars~18k tokensUpdated 1 mo ago
    Documents & OfficeAuto-check passed
  • Project

    HurricaHjz/second-yourself

    Manage the owner's OWN working repositories (Overleaf LaTeX projects, code repositories) from the vault, on an explicit instruction only: /project link | open | sync | brief | snapshot | status |…

    113 GitHub stars~3.1k tokensUpdated 5 days ago
    Documents & OfficeAuto-check passed
  • Review Overleaf

    fcakyon/claude-codex-settings

    This skill should be used when user asks to "fetch overleaf review comments", "address overleaf reviews", "apply overleaf comments", "review my overleaf paper", "sync overleaf feedback to local"…

    1.2k GitHub stars~940 tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Latex Diff

    flonat/flonat-research

    Compare two LaTeX files, project directories, or Git revisions and produce human-readable plus machine-readable severity-graded semantic changes.

    145 GitHub stars~1.9k tokensUpdated 8 days ago
    Documents & OfficeAuto-check passed
  • Research Writing

    alfonso0512/research-writing-skill

    科研论文写作助手,提供 30 个 Prompt 模板覆盖论文写作全流程. An agent skill from alfonso0512/research-writing-skill.

    486 GitHub starsUsed in 1 repo~818 tokens
    Documents & OfficeAuto-check passed

More from wentorai/research-plugins

All 428 skills in this repo
  • Abstract Writing Guide

    wentorai/research-plugins

    Craft structured research abstracts that maximize clarity and journal acceptance

    298 GitHub starsUsed in 1 repo~1.7k tokens
    Auto-check passed
  • Academic Citation Manager

    wentorai/research-plugins

    Manage academic citations across BibTeX, APA, MLA, and Chicago formats

    298 GitHub starsUsed in 1 repo~2.7k tokens
    Auto-check passed
  • Academic Paper Summarizer

    wentorai/research-plugins

    Summarize academic papers with structured extraction of key elements

    298 GitHub starsUsed in 1 repo~1.4k tokens
    Auto-check passed
  • Academic Study Methods

    wentorai/research-plugins

    Evidence-based study techniques for academic learning and retention

    298 GitHub starsUsed in 1 repo~1.8k tokens
    Auto-check passed
  • Academic Tone Guide

    wentorai/research-plugins

    Adjust writing tone and register for academic audiences and venues

    298 GitHub starsUsed in 1 repo~1.9k tokens
    Auto-check passed
  • Academic Translation Guide

    wentorai/research-plugins

    Academic translation, post-editing, and Chinglish correction guide

    298 GitHub starsUsed in 1 repo~1.6k tokens
    Auto-check passed

Works with

Questions about Overleaf CLI Guide

What does Overleaf CLI Guide do?

Sync and manage Overleaf LaTeX projects from the command line. Overleaf CLI Guide is an agent skill from wentorai/research-plugins.

When should I use Overleaf CLI Guide?

Overleaf CLI Guide fits situations like: tasks that involve LaTeX.

How do I install Overleaf CLI Guide in Claude Code?

Run `npx skills add wentorai/research-plugins --skill overleaf-cli-guide -a claude-code`. Or copy the skill folder (skills/tools/code-exec/overleaf-cli-guide in wentorai/research-plugins) into .claude/skills/overleaf-cli-guide in your project. Claude Code loads it when a task matches its description.

How do I install Overleaf CLI Guide in Codex?

Run `npx skills add wentorai/research-plugins --skill overleaf-cli-guide -a codex`. Or copy the skill folder (skills/tools/code-exec/overleaf-cli-guide in wentorai/research-plugins) into .agents/skills/overleaf-cli-guide in your project. Codex loads it when a task matches its description.

Can I use Overleaf CLI Guide in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add wentorai/research-plugins --skill overleaf-cli-guide -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/overleaf-cli-guide, .gemini/skills/overleaf-cli-guide, .github/skills/overleaf-cli-guide and .opencode/skills/overleaf-cli-guide in your project.

What does Overleaf CLI Guide need to run?

Going by SKILL.md and its folder, Overleaf CLI Guide needs the command-line tools its instructions call (git and pip). Our summary lists: Python 3.

Does Overleaf CLI Guide access the network?

SKILL.md names 4 domains. In commands or code: git.overleaf.com; the agent is likely to contact it when it follows the instructions. As links in the text: github.com, overleaf.com and mg.readthedocs.io. This is read from the text; nothing was executed.

Is Overleaf CLI Guide safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Overleaf CLI Guide use?

Overleaf CLI Guide is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Overleaf CLI Guide use?

About 1.9k tokens (SKILL.md is roughly 7.4k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Overleaf CLI Guide?

Skills that share tags, products or a category with Overleaf CLI Guide: Oleafly Response Letter (Oleafly/Oleafly, 205 stars), Write Paper (frenzymath/Danus, 471 stars), Project (HurricaHjz/second-yourself, 113 stars) and Review Overleaf (fcakyon/claude-codex-settings, 1.2k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Overleaf CLI Guide?

wentorai (a GitHub user) maintains it in wentorai/research-plugins, which has 298 GitHub stars. The repository holds 428 skills in this directory. The repository was last updated on June 19, 2026.

Source: wentorai/research-plugins on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.