用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
直接命令不会经过审查 Prompt;运行前请先检查来源。
npx skills add https://github.com/brycewang-stanford/Auto-Empirical-Research-Skills --skill overleaf-cli-guide命令会保持在同一行。复制前请横向滚动并检查完整内容。
想先保存到本地?可下载 SkillsMP 当前能够提供的文件。
正在显示 SKILL.md
Route empirical-research requests through the Auto-Empirical Research Skills catalog when this whole repository is installed as one skill in Codex, CodeBuddy, Claude Code, or another IDE. Use to choose and load the right vendored AERS skill for causal inference, econometrics, replication, data acquisition, manuscript writing, peer review and referee responses, citation checking, de-AIGC editing, or full empirical-paper workflows without reading the entire repository at once.
中英双语学术降 AIGC / bilingual academic de-AIGC skill. Removes AI-generated writing signatures from empirical papers in economics, management, and the social sciences — in both English and Chinese. Covers Turnitin AI, GPTZero, Originality.ai on the English side and 知网 AMLC, 万方, 维普 on the Chinese side. Uses a six-step loop (intake → audit → claim-evidence check → differentiated rewrite → five-dimension self-score → cold-reader recheck) with two pattern libraries (22 English + 17 Chinese patterns), section-by-section strategies for empirical papers, and hard protections that keep every number, coefficient, and citation intact.
Use when a research task needs reproducible Kaggle discovery, metadata inspection, bounded public-data downloads, competition or kernel discovery, model discovery, or an explicitly approved Kaggle write/delete operation through the official CLI.
基于 SOC 职业分类
| name | overleaf-cli-guide |
| description | Sync and manage Overleaf LaTeX projects from the command line |
| metadata | {"openclaw":{"emoji":"💻","category":"tools","subcategory":"code-exec","keywords":["Overleaf","LaTeX","CLI","sync","git","collaboration","academic writing"],"source":"https://github.com/overleaf/overleaf"}} |
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 master
When 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 master
For 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
fi
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}")
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" || true
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
# 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
Install 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 |