Oleafly Response Letter
Oleafly/Oleafly
Turn reviewer comments and the changes already made into a point-by-point response letter, in LaTeX or Typst and in plain text.
Sync and manage Overleaf LaTeX projects from the command line
$ npx skills add wentorai/research-plugins --skill overleaf-cli-guide -a claude-codeProject install by default; add -g for ~/.claude/skills/.
$ gh skill install wentorai/research-plugins overleaf-cli-guide --agent claude-codeProject scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).
$ 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-srcUse ~/.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/
Install the "overleaf-cli-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/tools/code-exec/overleaf-cli-guide into .claude/skills/overleaf-cli-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "overleaf-cli-guide", then confirm the skill loads.Claude Code copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$skill-installer install https://github.com/wentorai/research-plugins/tree/main/skills/tools/code-exec/overleaf-cli-guideType this inside Codex. $skill-installer <name> installs a curated skill from openai/skills. The installer writes to $CODEX_HOME/skills (default ~/.codex/skills). Restart Codex if the skill does not show up.
$ npx skills add wentorai/research-plugins --skill overleaf-cli-guide -a codexProject install goes to .agents/skills/; add -g for ~/.codex/skills/.
$ gh skill install wentorai/research-plugins overleaf-cli-guide --agent codexProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .agents/skills && cp -r skills-src/skills/tools/code-exec/overleaf-cli-guide .agents/skills/overleaf-cli-guide && rm -rf skills-srcUse ~/.agents/skills/ instead of .agents/skills for a personal install.
Codex skills documentation · loads skills from .agents/skills/
Install the "overleaf-cli-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/tools/code-exec/overleaf-cli-guide into .agents/skills/overleaf-cli-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "overleaf-cli-guide", then confirm the skill loads.Codex copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wentorai/research-plugins --skill overleaf-cli-guide -a cursorProject install goes to .agents/skills/; add -g for ~/.cursor/skills/.
$ gh skill install wentorai/research-plugins overleaf-cli-guide --agent cursorProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .cursor/skills && cp -r skills-src/skills/tools/code-exec/overleaf-cli-guide .cursor/skills/overleaf-cli-guide && rm -rf skills-srcUse ~/.cursor/skills/ instead of .cursor/skills for a personal install.
Cursor skills documentation · loads skills from .cursor/skills/, .agents/skills/, .claude/skills/, .codex/skills/
Install the "overleaf-cli-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/tools/code-exec/overleaf-cli-guide into .cursor/skills/overleaf-cli-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "overleaf-cli-guide", then confirm the skill loads.Cursor copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gemini skills install https://github.com/wentorai/research-plugins.git --path skills/tools/code-exec/overleaf-cli-guide--scope user (default) or --scope workspace; --path is the subfolder of the repo that holds the skill; --consent skips the security confirmation prompt.
$ npx skills add wentorai/research-plugins --skill overleaf-cli-guide -a gemini-cliProject install goes to .agents/skills/; add -g for ~/.gemini/skills/.
$ gh skill install wentorai/research-plugins overleaf-cli-guide --agent gemini-cliProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .gemini/skills && cp -r skills-src/skills/tools/code-exec/overleaf-cli-guide .gemini/skills/overleaf-cli-guide && rm -rf skills-srcUse ~/.gemini/skills/ instead of .gemini/skills for a personal install, then run /skills reload.
Gemini CLI skills documentation · loads skills from .gemini/skills/, .agents/skills/
Install the "overleaf-cli-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/tools/code-exec/overleaf-cli-guide into .gemini/skills/overleaf-cli-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "overleaf-cli-guide", then confirm the skill loads.Gemini CLI copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ gh skill install wentorai/research-plugins overleaf-cli-guideInstalls for Copilot at project scope by default; add --scope user for a personal install. Preview a skill first with gh skill preview. Needs GitHub CLI 2.90.0 or later (public preview).
$ npx skills add wentorai/research-plugins --skill overleaf-cli-guide -a github-copilotProject install goes to .agents/skills/; add -g for ~/.copilot/skills/.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .github/skills && cp -r skills-src/skills/tools/code-exec/overleaf-cli-guide .github/skills/overleaf-cli-guide && rm -rf skills-srcUse ~/.copilot/skills/ instead of .github/skills for a personal install. Commit .github/skills so cloud agent and code review can use it.
GitHub Copilot skills documentation · loads skills from .github/skills/, .claude/skills/, .agents/skills/
Install the "overleaf-cli-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/tools/code-exec/overleaf-cli-guide into .github/skills/overleaf-cli-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "overleaf-cli-guide", then confirm the skill loads.GitHub Copilot copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
$ npx skills add wentorai/research-plugins --skill overleaf-cli-guide -a opencodeOpenCode documents no install command of its own. Project install goes to .agents/skills/; add -g for ~/.config/opencode/skills/.
$ gh skill install wentorai/research-plugins overleaf-cli-guide --agent opencodeProject scope by default (.agents/skills/); add --scope user for a personal install.
$ git clone --depth 1 https://github.com/wentorai/research-plugins.git skills-src && mkdir -p .opencode/skills && cp -r skills-src/skills/tools/code-exec/overleaf-cli-guide .opencode/skills/overleaf-cli-guide && rm -rf skills-srcUse ~/.config/opencode/skills/ instead of .opencode/skills for a personal install.
OpenCode skills documentation · loads skills from .opencode/skills/, .claude/skills/, .agents/skills/
Install the "overleaf-cli-guide" agent skill from https://github.com/wentorai/research-plugins/tree/main/skills/tools/code-exec/overleaf-cli-guide into .opencode/skills/overleaf-cli-guide/ in this project. Copy the whole folder (SKILL.md and every file beside it), keep the folder name "overleaf-cli-guide", then confirm the skill loads.OpenCode copies the folder itself, the same result as the manual copy. Check what it changed before you commit it.
overleaf-cli-guideSync and manage Overleaf LaTeX projects from the command line
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.
Read from SKILL.md and the folder at commit bf44b3c. It shows what the files ask for, not the result of running them.
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.
Shell commands in SKILL.md call:
gitpipFrom the folder's file list and the shell code blocks in SKILL.md.
Hosts in commands or code, which the agent is likely to contact:
git.overleaf.comAlso links to:
github.comoverleaf.commg.readthedocs.ioFrom URLs in SKILL.md, links to its own repository left out.
Names no API keys, tokens, secrets or passwords.
From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.
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.
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.
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.
The full file from wentorai/research-plugins at commit bf44b3c, republished under its MIT licence (© wentorai). 340 words, ~1,852 tokens.
.claude/skills/overleaf-cli-guide/SKILL.md (or your agent's skills folder).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.
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 Server Pro and paid plans include a Git bridge that exposes each project as a Git repository.
# 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)# 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 masterWhen collaborators edit the same section simultaneously:
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 masterFor free Overleaf accounts without Git bridge access:
# 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"#!/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
fiimport 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}")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}")# .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" || trueRecommended 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# 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_StoreInstall the "LaTeX Workshop" extension and configure local compilation:
{
"latex-workshop.latex.tools": [
{
"name": "latexmk",
"command": "latexmk",
"args": ["-pdf", "-interaction=nonstopmode", "%DOC%"]
}
]
}-- init.lua
vim.g.vimtex_compiler_method = 'latexmk'
vim.g.vimtex_view_method = 'skim' -- macOS| Issue | Solution |
|---|---|
| Git push rejected | Pull first, resolve conflicts, then push |
| Sync tool authentication error | Re-run login, check 2FA settings |
| Compilation differs locally vs Overleaf | Match TeX Live versions; Overleaf uses TeX Live 2024 |
| Binary files (images) cause large diffs | Use .gitattributes to mark as binary |
| Overleaf rate limiting | Add delays between API calls, use Git bridge if available |
© wentorai, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file
Just SKILL.md in skills/tools/code-exec/overleaf-cli-guide of wentorai/research-plugins.
Open the folder on GitHubat commit bf44b3c
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.
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.
| Skill | Stars | Used in | Tokens | Auto-check | Licence | Repo updated |
|---|---|---|---|---|---|---|
| Overleaf CLI Guide this skillwentorai/research-plugins | 298 | 1 repos | ~1.9k | Automated safety check: Pass | MIT | |
| Oleafly Response LetterOleafly/Oleafly | 205 | — | ~2.3k | Automated safety check: Pass | MIT | |
| Write Paperfrenzymath/Danus | 471 | — | ~18k | Automated safety check: Pass | Apache-2.0 | |
| ProjectHurricaHjz/second-yourself | 113 | — | ~3.1k | Automated safety check: Pass | MIT | |
| Review Overleaffcakyon/claude-codex-settings | 1.2k | — | ~940 | Automated safety check: Pass | Apache-2.0 | |
| Latex Diffflonat/flonat-research | 145 | — | ~1.9k | Automated safety check: Pass | MIT |
Oleafly/Oleafly
Turn reviewer comments and the changes already made into a point-by-point response letter, in LaTeX or Typst and in plain text.
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.
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 |…
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"…
flonat/flonat-research
Compare two LaTeX files, project directories, or Git revisions and produce human-readable plus machine-readable severity-graded semantic changes.
alfonso0512/research-writing-skill
科研论文写作助手,提供 30 个 Prompt 模板覆盖论文写作全流程. An agent skill from alfonso0512/research-writing-skill.
wentorai/research-plugins
Craft structured research abstracts that maximize clarity and journal acceptance
wentorai/research-plugins
Manage academic citations across BibTeX, APA, MLA, and Chicago formats
wentorai/research-plugins
Summarize academic papers with structured extraction of key elements
wentorai/research-plugins
Evidence-based study techniques for academic learning and retention
wentorai/research-plugins
Adjust writing tone and register for academic audiences and venues
wentorai/research-plugins
Academic translation, post-editing, and Chinglish correction guide
Categories
Sync and manage Overleaf LaTeX projects from the command line. Overleaf CLI Guide is an agent skill from wentorai/research-plugins.
Overleaf CLI Guide fits situations like: tasks that involve LaTeX.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.