review-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 feedback in a local git-traβ¦
Install / Use
npx skills add fcakyon/claude-codex-settings --skill review-overleafInstalls into whichever agent you are using.
SKILL.md
Installable skill definition
Quality Score
Category
MarketingSupported Platforms
Our assessment of review-overleaf
review-overleaf scores 85/100 on our quality scale, 441st of 642 Marketing skills we index.
Its SKILL.md is 3.7 KB long, well organised into 9 sections with 1 code example: a solid amount of guidance for an agent.
With 1,153 GitHub stars, it is one of the more widely adopted skills in the catalogue.
Maintenance, license and trust
- The repository was last updated about 2 months ago, so review-overleaf is actively maintained.
- Our last check on 2026-11-05 found the source still online.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 100/100, with no cautions. These come from repository metadata, not a code audit β read the skill file before letting an agent act on it.
Safety scan
No issues foundOur scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful.
AI review by kimi-k2.7-code on 2026-10-04. Automated pattern scan on 2026-10-04. It catches known dangerous patterns, not every risk β read a skill before letting an agent act on it.
review-overleaf compared with similar skills
All 4 of these similar skills score higher than review-overleaf; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| review-overleaf (this skill)by fcakyon | 85 | 1.2k | 53d ago | SKILL.md |
| Agent-Reachby Panniantong | 100 | 112.3k | 9d ago | CLAUDE.md |
| x402by browser-use | 100 | 121.0k | 3d ago | SKILL.md |
| algorithmic-artby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
| pptxby anthropics | 100 | 177.9k | 55d ago | SKILL.md |
Frequently asked questions
- How do I install review-overleaf?
- Run
npx skills add fcakyon/claude-codex-settings --skill review-overleaf. The install tabs above show the steps for each supported agent. - Which AI agents does review-overleaf work with?
- It is written for Universal, as a SKILL.md file. Other agents that read the same format can often use it too.
- Is review-overleaf safe to use?
- Our scan of the whole file found no instruction hijacking, hidden characters, credential access, data exfiltration or destructive commands. An AI review of the same text found nothing harmful. It is Apache-2.0-licensed and scores 100/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is review-overleaf still maintained?
- The repository was last updated about 2 months ago, so review-overleaf is actively maintained.
Skill content
View source on GitHubname: review-overleaf description: 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 feedback in a local git-tracked LaTeX repo.
Review Overleaf
Pull unresolved review threads from an Overleaf project, locate each in the local repo, propose edits the user reviews, and apply them. Does not push back to Overleaf β the web UI is still the place to mark threads resolved after the user verifies the local change.
Step 1: Resolve project ID
Accept any of:
- Raw 24-char hex ID (
^[0-9a-f]{24}$) - Full URL like
https://www.overleaf.com/project/<id>β extract via regex - Project name in quotes β call:
Each line ispython3 ${CLAUDE_PLUGIN_ROOT}/scripts/overleaf_reviews.py --list-projects<24-hex> <accessLevel> <name>. Fuzzy-match the name. If multiple match, AskUserQuestion to disambiguate.
If the user has not given a project ID at all, run --list-projects and show the user the table so they can pick one.
Step 2: Cookie precheck
If ~/.claude/overleaf-skills/cookie does not exist, tell the user to "set up overleaf" (which triggers the setup skill) and stop.
If it exists but auth fails (the next script call returns a refresh hint), point at the same setup skill and stop.
Step 3: Access-level guard
If the project ID came from name resolution, check the matched entry's accessLevel. If readOnly, warn:
Project is read-only. You can edit local files but cannot sync them back to Overleaf via the web UI; you would need to copy-paste manually. Continue?
For owner, readAndWrite, or review, proceed silently.
Step 4: Fetch comments
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/overleaf_reviews.py --json --repo . < project-id > --unresolved-only
Parses to a JSON array. Each record has: thread_id, doc_id, snippet, offset, resolved, messages (list of {user, ts, content}), file, line. The file and line are null when the snippet did not match any local *.tex.
Step 5: Edit loop
For each record where file is non-null:
Readthe file atlineΒ± 5 lines for context.- Summarize the comment thread in one sentence: who said what.
- Propose a concrete edit grounded in the comment text. If the comment is a question (e.g., "did you mean X?"), the edit should answer it in the prose; if it's a correction (e.g., "wrong notation"), the edit should make the correction.
- Apply via
Edit. Do not batch β one comment, one edit, then move on.
Skip records where file is null (snippet did not map). Collect them in an <unmapped> list.
Step 6: Wrap up
After the loop:
- Run
git diffand show the user the full set of changes. - List the
<unmapped>records (if any) withdoc_id+ snippet preview, so the user can hunt them manually. - Suggest a commit message in the style:
address overleaf review: <one-line summary of the changes>. Do NOT auto-commit. The user can run/github-dev:commit-stagedor commit by hand. - Remind the user to mark the addressed threads as resolved in the Overleaf web UI once they verify the local diff.
Non-goals
- No re-upload to Overleaf (no write API used).
- No thread resolution in Overleaf (web UI only).
- No
.bibedits unless a comment specifically targets a citation. - No multi-line snippets that span paragraph breaks β those land in
<unmapped>for v1; the snippet matcher is line-anchored.
Pairs naturally with
github-devβ/github-dev:commit-stagedafter the edit loop,/github-dev:create-prif the project is collaborative.
Related Skills
Agent-Reach
112.3kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu β one CLI, zero API fees.
x402
121.0kSet up Browser Use Cloud payments with x402 β pay per request from a crypto wallet (USDC on Base mainnet), no signup or API key.
algorithmic-art
177.9kCreating algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use this when users request creating art using code, generative art, algorithmic art, flow fields, or particle systems.
pptx
177.9kUse this skill any time a .pptx or .potx file is involved in any way β as input, output, or both. This includes: creating slide decks, pitch decks, or presentations; reading, parsing, or extracting text from any .pptx or .potx file (even if the extracted content will be used elsewhere, like in an emβ¦
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit β see the Safety scan above for what the skill file itself contains.
