Agent skill · Code Review & Quality

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-tracked LaTeX repo.

fcakyongithub.com/fcakyonGitHub ↗
claude-codecodexcursorApache-2.0
Install
npx skills add fcakyon/claude-codex-settings --skill review-overleaf --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 1
SKILL.md size: 4 KB
Bundled scripts: none
Path: plugins/overleaf-skills/skills/review-overleaf/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 967
Language: Python

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# 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: ```bash python3 ${CLAUDE_PLUGIN_ROOT}/scripts/overleaf_reviews.py --list-projects ``` Each line is `<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 `r

What's inside
Steps it walks through
  1. Step 1: Resolve project ID
  2. Step 2: Cookie precheck
  3. Step 3: Access-level guard
  4. Step 4: Fetch comments
  5. Step 5: Edit loop
  6. Step 6: Wrap up
  7. Non-goals
  8. Pairs naturally with
Commands it runs
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/overleaf_reviews.py --list-projects
python3 ${CLAUDE_PLUGIN_ROOT}/scripts/overleaf_reviews.py --json --repo . < project-id > --unresolved-only
More from claude-codex-settings
All skills →
About this skill
What does the review-overleaf skill do?

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.

How do I install it?

Run `npx skills add fcakyon/claude-codex-settings --skill review-overleaf --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From fcakyon/claude-codex-settings, a repository with 967 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going