overleaf-skill
Use this skill whenever the user wants to synchronize NeuroClaw-generated LaTeX manuscripts with Overleaf, read/write .tex files, download/upload projects, create/rename/archive projects, compare versions, or manage project structure. Triggers include: 'sync to Overleaf', 'upload paper to Overleaf', 'Overleaf project', 'LaTeX sync', 'push draft', 'download Overleaf', 'create Overleaf project', 'tex file to Overleaf', or any request involving paper_draft.tex / collaboration. This skill is the **mandatory interface-layer LaTeX collaborator** in NeuroClaw: it strictly enforces pull-first workflow
npx skills add BioTender-max/awesome-bio-agent-skills --skill overleaf-skill --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Overleaf Skill ## Overview This skill provides secure, audited access to Overleaf projects using the pyoverleaf library (Python API + CLI), enabling full round-trip collaboration for NeuroClaw manuscripts. Role in NeuroClaw multi-agent system: - Acts as the dedicated Overleaf Collaborator. - Authentication: manual cookie string provided by the user (recommended for headless/server environments). - Default behavior: pull + diff + report changes → require user confirmation before any local overwrite or merge. - Write / create / delete / rename operations: **strictly forbidden** without explicit, single-use user authorization per operation. - Preferred method: Python API (more reliable than CLI in agent sessions). - Preserves full Overleaf version history for easy human review and revert. - Supports listing projects, file/folder management, ZIP download/upload, and limited project creation/renaming/archiving. **Research use only** — keeps manuscripts clean, typeset-ready, and suitable for co-author feedback or journal submission. ## Supported Operations | Operation | Method | CLI Example | Python API Example | Safety Requirement | |----------------------------|----------------------
- Overview
- Supported Operations
- Authentication (Important – Headless/Server Friendly)
- Quick Workflows (NeuroClaw Integrated)
- Benchmark-Facing Default Mainline
- Installation (in NeuroClaw environment)
- Operational Notes from Real Server Usage
- 1. Use the correct Python interpreter
- 3. Separate read-only checks from write actions
- 4. Project creation is not reliably supported
- 5. Upload requires a real folder id
- 6. Confirm project existence before upload
- 7. Keep credentials local and temporary
- Safety & Limitations
Install pyoverleaf in isolated environment pip install pyoverleaf Quick test (user runs once in terminal) python -c "import pyoverleaf; api=pyoverleaf.Api(); print(api.get_projects())" python3 - <<'PY'
What does the overleaf-skill skill do?
Use this skill whenever the user wants to synchronize NeuroClaw-generated LaTeX manuscripts with Overleaf, read/write .tex files, download/upload projects, create/rename/archive projects, compare versions, or manage project structure. Triggers include: 'sync to Overleaf', 'upload paper to Overleaf', 'Overleaf project', 'LaTeX sync', 'push draft', 'download Overleaf', 'create Overleaf project', 'tex file to Overleaf', or any request involving paper_draft.tex / collaboration. This skill is the **mandatory interface-layer LaTeX collaborator** in NeuroClaw: it strictly enforces pull-first workflow
How do I install it?
Run `npx skills add BioTender-max/awesome-bio-agent-skills --skill overleaf-skill --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From BioTender-max/awesome-bio-agent-skills, a repository with 135 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.