overleaf-comments skill
✓ VerifiedManage Overleaf review-panel comments by listing, adding, replying to, and resolving discussion threads.
- GitHub stars
- 14
- Files
- 1
- Last commit
- Sep 20, 2026
- License
- AGPL-3.0
- Allowed tools
- —
What does the overleaf-comments skill do?
overleaf-comments manages Overleaf review-panel comments by listing, adding, replying to, and resolving discussion threads.
Summary generated from the skill's SKILL.md.
About the overleaf-comments skill
Managing LaTeX document discussions through the Overleaf review panel is what this skill enables for researchers and academic writers. An agent uses these tools to list existing discussion threads, add new feedback, reply to collaborators, or resolve completed conversations. It is designed for situations where an agent needs to ask questions about claims, suggest tone changes, or explain edits without directly altering the author's text.
Developers use the overleaf_list_comments tool to inspect thread history and anchor text before making revisions. When providing feedback, the overleaf_add_comment tool requires an exact anchor text match to place the comment correctly. To maintain transparency, the skill automatically appends a mandatory signature identifying the agent as a co-author unless the user explicitly requests to omit it. Note that these tools require an Overleaf account with access to the review panel, as the Community Edition does not support these features.
What an agent can do with it
- 1Reviewing academic manuscriptsAsk the agent to review a document and leave feedback on specific claims or phrasing.
- 2Responding to collaborator feedbackInstruct the agent to answer questions or address concerns raised by a co-author in a discussion thread.
- 3Tracking discussion historyRequest a list of all current and previously resolved comments on a specific project file.
- 4Cleaning up resolved threadsTell the agent to tidy up the review panel by resolving threads that have been addressed.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the overleaf-comments skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the overleaf-comments skill in Plugin
/plugin marketplace add DanielHou315/overleaf-mcp-rt /plugin install overleaf-mcp-rt@overleaf-mcp-rt
Install the overleaf-comments skill in Claude Code
~/.claude/skills/overleaf-comments/SKILL.md
$ npx degit DanielHou315/overleaf-mcp-rt/skills/overleaf-comments ~/.claude/skills/overleaf-commentsInstall the overleaf-comments skill in Claude Code (project)
.claude/skills/overleaf-comments/SKILL.md
$ npx degit DanielHou315/overleaf-mcp-rt/skills/overleaf-comments .claude/skills/overleaf-commentsInstall the overleaf-comments skill in Codex
~/.agents/skills/overleaf-comments/SKILL.md
$ npx degit DanielHou315/overleaf-mcp-rt/skills/overleaf-comments ~/.agents/skills/overleaf-commentsInstall the overleaf-comments skill in Gemini CLI
~/.gemini/skills/overleaf-comments/SKILL.md
$ npx degit DanielHou315/overleaf-mcp-rt/skills/overleaf-comments ~/.gemini/skills/overleaf-commentsInstall the overleaf-comments skill in Claude.ai
npx degit DanielHou315/overleaf-mcp-rt/skills/overleaf-comments overleaf-comments && zip -r overleaf-comments.zip overleaf-comments # claude.ai → Customize → Skills → + → Create skill → Upload a skill → overleaf-comments.zip
Automated checks
Ran Nov 16, 2026Full report →Passed our automated checks. That is not a security audit: read the scripts before you let an agent run them. How checks work
- Source repository linked and reachabledanielhou315/overleaf-mcp-rt/skills/overleaf-comments is public and reachablegithub.com/danielhou315/overleaf-mcp-rt/tree/HEAD/skills/ove ↗Pass
- Open source license (OSI)AGPL-3.0spdx.org/licenses/AGPL-3.0.html ↗Pass
- Commit or release in the last yearLast commit 2026-09-20github.com/danielhou315/overleaf-mcp-rt/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/danielhou315/overleaf-mcp-rt/blob/HEAD/skills/ove ↗Pass
- Pre-approved tools are scopedNo pre-approved tools; the agent asks before using onegithub.com/danielhou315/overleaf-mcp-rt/blob/HEAD/skills/ove ↗Pass
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 36 linesgithub.com/danielhou315/overleaf-mcp-rt/blob/HEAD/skills/ove ↗Pass
SKILL.md
View on GitHubOverleaf comments
A comment attaches a discussion thread to a span of text without changing the text.
Comment or edit?
- Edit when the user asked for the change, or it is mechanical (typo, broken reference, compile error).
- Comment when it is the author's decision: claims, numbers, framing, tone, cuts, anything in a co-author's section. Also for questions ("which dataset is this?") and for explaining a non-obvious edit you made.
- When reviewing a document, default to comments, and say in your reply how many you left and where.
Signature — required
Comments are posted through the logged-in Overleaf account, which is usually the user's own, so Overleaf shows them as the author. To keep it honest, every comment you write must end with:
Co-authored by <your agent name>
Pass agentName — the name you, the assistant, go by — to overleaf_add_comment / overleaf_reply_comment and the server appends that line for you — do not also write it in content. Set omitSignature: true only if the user has explicitly told you not to sign comments; if they did, that instruction holds for the rest of the session.
Using the tools
overleaf_list_comments { projectId, path }— threads on a doc:threadId,line,anchorText,resolved, and each message with its author. AddincludeResolved: truefor history. Check this before revising a file someone has reviewed.overleaf_add_comment { projectId, path, anchorText, content, agentName }—anchorTextmust match exactly one place, likeold_string. Anchor to the specific phrase you mean, not a whole paragraph. One point per comment; be concrete and propose wording where you can.overleaf_reply_comment { projectId, threadId, content, agentName }— answer in the thread that raised the point rather than opening a new one. When a comment asked for a change and you made it, reply saying what you changed.overleaf_resolve_comment { projectId, path, threadId }— resolve a thread you opened once it is dealt with. Leave threads opened by people for them to resolve, unless the user asked you to tidy up.resolved: falsereopens.
Where comments don't exist
Comments need Overleaf's review panel: overleaf.com and Server Pro have it, stock Community Edition does not. There the tools return COMMENTS_UNSUPPORTED and change nothing. Fall back to a LaTeX comment next to the passage — % NOTE(<your agent name>): … — and list those notes for the user, since nothing in the UI will surface them.
Files in this skill
1overleaf-comments skill questions
How do I install the overleaf-comments skill in Claude Code?
Run npx degit DanielHou315/overleaf-mcp-rt/skills/overleaf-comments ~/.claude/skills/overleaf-comments. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the overleaf-comments skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
When should I use a comment instead of an edit?
Use a comment when a decision belongs to the author, such as claims, numbers, framing, tone, or cuts. Use an edit for mechanical changes like typos or compile errors.
How do I ensure my agent identity is visible in Overleaf comments?
You must pass your agent name to the comment tools so the system can append a mandatory 'Co-authored by' signature.
What happens if the Overleaf version does not support the review panel?
If using the Community Edition, the tools will return a COMMENTS_UNSUPPORTED error; in this case, fall back to using LaTeX comments starting with % NOTE.