Work With Overleaf

Community

ShaishavMaisuria

work-with-overleaf

Bridges an Overleaf project to the local skills so a paper kept on Overleaf can be checked, polished, and reviewed, then synced back. Use when a researcher says "my paper is on Overleaf", "sync my Overleaf project", "pull my paper from Overleaf", "run preflight on my Overleaf paper", "edit my Overleaf project locally", or "push my changes back to Overleaf". Walks the three real paths — Overleaf Git integration (clone as a local repo), GitHub synchronization, or download-as-ZIP for free accounts — gets the .tex into a local working copy the other skills operate on, and guides syncing changes back. Treats the Overleaf access token as a secret, never auto-pushes without confirmation, and re-verifies the current Overleaf method live since premium availability and steps change. Trigger words - overleaf, my paper is on overleaf, sync overleaf, pull from overleaf, push to overleaf, edit overleaf locally.

Overview

Publisher	ShaishavMaisuria
Repository	`research-paper-lifecycle-skills`
Skill name	`work-with-overleaf`
Stars	59
Forks	22
Bundled files	1
License	Apache-2.0
Links	Skill source Repository Homepage

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
1 bundled files
Scripts, templates, and references the model can read while it works. Files are read-only and never executed.
Open source
Published by ShaishavMaisuria on GitHub. Read the source before you install it.

Installation

Install the Work With Overleaf AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/ShaishavMaisuria/research-paper-lifecycle-skills/tree/main/skills/work-with-overleaf
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/ShaishavMaisuria/research-paper-lifecycle-skills/tree/main/skills/work-with-overleaf

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/ShaishavMaisuria/research-paper-lifecycle-skills.git /tmp/research-paper-lifecycle-skills
mkdir -p .claude/skills
cp -r /tmp/research-paper-lifecycle-skills/skills/work-with-overleaf .claude/skills/work-with-overleaf

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Work With Overleaf in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Work With Overleaf on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Work With Overleaf is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Work With Overleaf

Most academics keep their .tex in Overleaf, not on disk — so this skill gets an Overleaf project into a local working copy the rest of the toolkit can act on (preflight-check, polish-prose, verify-citations, match-style, …), then helps sync the changes back. It's the on-ramp; the other skills do the work.

Pick the path that matches the account

Overleaf exposes three ways to move a project in and out. Re-verify the current method and whether it's premium before relying on it against Overleaf's live documentation, because account features and menu names can change. As of the last check:

Path	Who	How
Git integration (recommended)	Premium / Server Pro 4.0+	Project → Menu → Git; copy the `git clone https://git.overleaf.com/<id>` command. Authenticate with an Overleaf token (token-based auth). Work locally, then `git pull` / `git push`. Branch is `main` (older clones may be `master`).
GitHub synchronization	Premium	Link the project to a GitHub repo (Menu → GitHub); sync both ways. Run the skills on the GitHub clone you already have locally.
Download ZIP	Free (everyone)	Menu → Download → Source. Work locally; there is no auto-merge — re-upload changed files in the Overleaf editor, or paste edits back. Best for a one-shot check.

If the user isn't sure which they have, ask; don't assume premium.

Process

Establish the local copy. Determine the path above and get the project local (clone, use the existing GitHub clone, or unzip the download). Confirm the main .tex and .bib are present.
Run the requested skills on the local files exactly as normal — preflight-check for desk-reject risk, polish-prose/match-style for the writing, verify-citations for the .bib, assess-paper for the full read. Write outputs to paper-workspace/.
Review changes before syncing. Show the author a diff of what changed. Never push automatically — academic drafts are shared/co-authored and an unreviewed push can clobber a collaborator's edits.
Sync back by the same path: git push (Git integration), commit+push to the linked GitHub repo (sync), or tell the author exactly which files to re-upload (ZIP). For Git/GitHub, confirm first and surface any merge conflicts rather than forcing.
Compile sanity. Note that Overleaf compiles server-side; if the local edits use a package/option Overleaf's TeX Live version may differ on, flag it so the author recompiles on Overleaf before relying on the PDF.

Guardrails

The Overleaf token is a secret. Never print it, log it, write it to a file, or commit it. If a clone URL contains a token, redact it in any output.
Never auto-push or auto-upload without explicit confirmation — and never rewrite the Overleaf project history. Co-authors may be editing concurrently.
Don't assume premium. Git/GitHub paths are premium; if the user is on free Overleaf, use the ZIP path and say so.
Re-verify the live method (premium status, menu steps, clone host, branch name) against Overleaf's current docs before instructing — do not rely on cached steps.
Copilot, not pilot: propose the sync, show the diff, let the author run it.

Memory

Uses the shared .paper-memory/ convention (paper-memory-convention.md).

At start: read profile.yml/lessons.md for the author's usual Overleaf path so you don't re-ask each time.
At end: append date · work-with-overleaf · path used · note after deduping (e.g. "author uses Git integration, token in keychain").
Create .paper-memory/ on demand; local-only, never uploaded; never store the token there.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

scripts/overleaf_status.py3 KB

Frequently asked questions

What does the Work With Overleaf AI skill do?

Why use Work With Overleaf on TypingMind?

Because you install it once and use it with any model. Work With Overleaf is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Work With Overleaf in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/ShaishavMaisuria/research-paper-lifecycle-skills/tree/main/skills/work-with-overleaf. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Work With Overleaf?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Work With Overleaf?

As many as you like. As long as a model supports skills, you can use Work With Overleaf with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Work With Overleaf AI skill free?

Yes. It is published on GitHub by ShaishavMaisuria under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Openai Docs

openai

OrganizationPopular

Use for Codex models/pricing, scheduled tasks, skills, settings, setup, troubleshooting, customization, automations, and self-knowledge—including 'you,' 'your,' 'this app,' or 'this coding agent' when…

Caveman Explore

Read-only repository explorer for cold-start orientation, broad cross-file localization, or when a direct search failed. Skip it when the exact file or symbol is already named. Returns path:line…

Delegate Work

Delegate user-requested work to an existing Paperclip agent, with a durable task reference and clear execution expectations.

Html Ppt Zhangzara Vellum

nexu-io

OrganizationPopular

A humanities lecture: how Renaissance linear perspective reshaped early cartography — sources, argument, and evidence. Built as a decision-grade academic research deck for faculty, graduate seminar.

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

Work With Overleaf

Pick the path that matches the account

Process

Guardrails

Memory

Bundled files

Frequently asked questions

Related AI Skills

Set up your own AI workspace now