Skip to content
Skills Library
Science & research · Tool integration

overleaf-comments

/overleaf-comments

Reading, writing, answering and resolving Overleaf review-panel comments via overleaf_list_comments, overleaf_add_comment, overleaf_reply_comment and overleaf_resolve_comment, including the mandatory "Co-authored by" signature. Use when the user asks you to review a document, leave feedback or questions, respond to comments a collaborator left, or when you would otherwise change a passage whose meaning is the author's call.

Licence
AGPL-3.0
Last repository change
20.09.2026

Assessment and security

100/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content35 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 20.09.2026, without references to retired models or APIs.

Licence

AGPL-3.0, copyleft: przeróbki udostępniane innym muszą mieć tę samą licencję.

What it does and when to use it

Reading, writing, answering and resolving Overleaf review-panel comments via overleaf_list_comments, overleaf_add_comment, overleaf_reply_comment and overleaf_resolve_comment, including the mandatory "Co-authored by" signature. Use when the user asks you to review a document, leave feedback or questions, respond to comments a collaborator left, or when you would otherwise change a passage whose meaning is the author's call.

Triggers from the description

Co-authored by
Original author description

Reading, writing, answering and resolving Overleaf review-panel comments via overleaf_list_comments, overleaf_add_comment, overleaf_reply_comment and overleaf_resolve_comment, including the mandatory "Co-authored by" signature. Use when the user asks you to review a document, leave feedback or questions, respond to comments a collaborator left, or when you would otherwise change a passage whose meaning is the author's call.

How it works

  1. Comment or edit?
  2. Signature — required
  3. Using the tools
  4. Where comments don't exist
Original SKILL.md headings · 32 lines, 411 words
SKILL.md preview
---
name: overleaf-comments
description: Reading, writing, answering and resolving Overleaf review-panel comments via overleaf_list_comments, overleaf_add_comment, overleaf_reply_comment and overleaf_resolve_comment, including the mandatory "Co-authored by" signature. Use when the user asks you to review a document, leave feedback or questions, respond to comments a collaborator left, or when you would otherwise change a passage whose meaning is the author's call.
---

# Overleaf 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. Add `includeResolved: true` for history. Check this before revising a file someone has reviewed.
- `overleaf_add_comment { projectId, path, anchorText, content, agentName }` — `anchorText` must match exactly one place, like `old_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: false` reopens.

## 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.

Versions

The database has no other skills named overleaf-comments.

Database snapshot: 13.11.2026 · package version 3653174a7d27 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100review-overleaf
    This skill should be used when user asks to "fetch overleaf review comments", "address overleaf reviews", "apply overleaf comments", "review my overleaf paper", "sync overleaf feedback to local", "what comments are on my overleaf doc", or wants to act on Overleaf reviewer…
  • 100overleaf-setup
    Install, log in to, and troubleshoot the overleaf-mcp-rt MCP server. Use when Overleaf tools are missing or failing (OVERLEAF_AUTH_FAILED, INVALID_CONFIG, PROXY_AUTH_FAILED, "connection closed"), when the user wants to connect a new Overleaf instance or overleaf.com, or when a…
  • 100setup
    This skill should be used when user asks to "set up overleaf", "configure overleaf cookie", "overleaf auth failed", "overleaf 401", "overleaf session expired", "overleaf unauthorized", or needs to install or refresh their Overleaf session cookie for the overleaf-skills plugin.
  • 100overleaf-editing
    How to read and edit Overleaf documents through the overleaf_* MCP tools without disrupting people who have the project open. Use whenever you are about to read, edit, create, move or delete files in an Overleaf project, or when a tool result contains an <external-changes>…
  • 100overleaf-sync
    Two-way sync between a local paper directory and an Overleaf project, so ARIS audit/edit workflows stay on the local copy while collaborators edit in the Overleaf web UI. Use when user says \"Sync overleaf\", \"overleaf sync\", \"Push it. overleaf\", \"connect overleaf\",…
  • 100overleaf
    Set up and use a reproducible Overleaf MCP for Git-backed LaTeX editing, reviewed publishing, optional GitHub sync, and local or Overleaf online compilation on Windows and macOS. Use for connecting or operating Overleaf projects, not generic prose polishing without a project.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.