overleaf-skill

To securely sync Overleaf projects for LaTeX manuscripts, you can use a pull-first workflow that requires explicit per-operation authorization. This approach prevents unauthorized writes by listing and reading projects before executing any download or file modification actions.

Yes, you can access Overleaf project files headlessly by providing your Overleaf browser cookie string. This supports safe, headless server authentication, allowing you to list projects and read file contents without manual browser interaction or entering login credentials directly.

A pull-first Overleaf collaboration workflow reviews project changes locally via diffs and reports before applying any modifications. You need this process to preserve full version history and maintain a strict per-operation audit trail when working on NeuroClaw manuscripts.

You can download Overleaf project ZIPs and read LaTeX file contents by initiating a read-only project discovery phase. This safety guard ensures all file reading and downloading operations are audited and require explicit user authorization before execution.

Yes, Overleaf synchronization maintains full version history when creating, renaming, or archiving projects. These write operations are only executed with explicit confirmation, ensuring all manuscript modifications are tracked in a strict per-operation audit trail.

The main limitation of a pull-first Overleaf synchronization approach is that write operations are strictly blocked until explicit user authorization is granted. Additionally, you must supply valid browser cookie strings for authentication, which may expire and require manual refreshing.