Agent skill

AI Review Skill

by NeuroDong in NeuroDong/Ai-Review

Generates structured AI paper reviews (SoT style) for LaTeX, PDF, and Word manuscripts.

MITAuto-check passedDocuments & Office

Install AI Review Skill

skills CLI
$ npx skills add NeuroDong/Ai-Review --skill ai-review-skill -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install NeuroDong/Ai-Review ai-review-skill --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/NeuroDong/Ai-Review.git skills-src && mkdir -p .claude/skills && cp -r skills-src/ai-review-skills .claude/skills/ai-review-skill && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
ai-review-skill
GitHub stars
628
Token cost
~2.5k tokens
SKILL.md length
1,104 words
Files
1
Skills in repo
1
Repo updated
First seen
Licence
MIT

At a glance

Generates structured AI paper reviews (SoT style) for LaTeX, PDF, and Word manuscripts.

  • Works in 3 steps: Obtain manuscript content → Detect manuscript language → Generate the review
  • The user asks to review a paper
  • SKILL.md covers When to Use, Workflow, SoT Prompt (English) — use for… and SoT Prompt (Chinese) — use for…
  • Calls pdftotext

What it does

AI Review Skill is an agent skill from NeuroDong/Ai-Review. Generates structured AI paper reviews (SoT style) for LaTeX, PDF, and Word manuscripts. Uses SoT prompt in English for English papers and SoT prompt in Chinese for Chinese papers. Use when the user asks to review a paper, 审稿, 论文审稿, review manuscript, or get strengths/weaknesses/suggestions for a .tex, .pdf, or .docx file.

Its SKILL.md is about 2.5k tokens, which your agent loads only when the skill is triggered. It is a single SKILL.md file with no bundled scripts.

It sits in Documents & Office, covering Peer review, LaTeX and Word documents. It works with Microsoft Word and LaTeX. The repository describes itself as: Large model-assisted paper review. The licence is MIT.

When your agent uses it

  • The user asks to review a paper
  • Review manuscript
  • Get strengths/weaknesses/suggestions for a .tex

Example prompts

  • “Use the ai-review-skill skill to generate structured AI paper reviews (SoT style) for LaTeX, PDF, and Word manuscripts”
  • “/ai-review-skill”

Requirements

  • Python 3

Workflow steps

3 steps, taken from the step headings in SKILL.md.

  1. Obtain manuscript content
  2. Detect manuscript language
  3. Generate the review

What it can do on your machine

Read from SKILL.md and the folder at commit b715662. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • pdftotext

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

AI Review Skill loads about 2.5k tokens when it runs. Until then it costs about 85 tokens; SKILL.md has 1,104 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~85
When it runs · the whole SKILL.md, loaded when a task matches
~2.5k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from NeuroDong/Ai-Review at commit b715662, republished under its MIT licence (© NeuroDong). 1,104 words, ~2,509 tokens.

Download SKILL.mdSave it as .claude/skills/ai-review-skill/SKILL.md (or your agent's skills folder).
name
ai-review-skill
description
Generates structured AI paper reviews (SoT style) for LaTeX, PDF, and Word manuscripts. Uses SoT prompt in English for English papers and SoT prompt in Chinese for Chinese papers. Use when the user asks to review a paper, 审稿, 论文审稿, review manuscript, or get strengths/weaknesses/suggestions for a .tex, .pdf, or .docx file.

Ai-Review Skill (SoT)

Produces structured, evidence-anchored paper reviews with no scores or accept/reject. Supports LaTeX, PDF, and Word. For English manuscripts use the SoT Prompt (English) section below; for Chinese manuscripts use the SoT Prompt (Chinese) section below.

When to Use

User says "review my paper", "审稿", "论文审稿", "review this manuscript", or provides a path to a manuscript file (.tex, .pdf, .docx, .doc).

Workflow

Step 1: Obtain manuscript content
  • LaTeX (.tex): Read the file(s). For multi-file projects, read the main file and any \input/\include files to assemble full text. Strip or ignore \bibliography/\cite only if needed for length.
  • PDF (.pdf): Extract text accurately. Prefer in order: (1) any skill in this project’s .cursor/skills/ or ~/.cursor/skills/ that extracts PDF text; (2) pdftotext -layout "file.pdf" - (poppler-utils); (3) Python with PyMuPDF (fitz), pdfplumber, or pypdf (e.g. page.get_text() or equivalent). Preserve section order.
  • Word (.docx/.doc): Extract text. Prefer python-docx for .docx (paragraphs + tables); or mammoth for .docx to markdown. For .doc, use mammoth or suggest converting to .docx first.

If no file is given, ask for the manuscript path.

Step 2: Detect manuscript language

From the extracted or read text, decide if the paper is mainly English or mainly Chinese (title, abstract, headings, body). English paper → follow SoT Prompt (English) below. Chinese paper → follow SoT Prompt (Chinese) below.

Step 3: Generate the review

Use the manuscript text as the [Input] to the chosen SoT prompt. Follow that prompt’s multi-stage process and output exactly the six sections in order. No scores, ratings, or accept/reject. Every claim must have an evidence anchor or "No direct evidence found in the manuscript."


SoT Prompt (English) — use for English manuscripts

Apply the following prompt in full when the manuscript is in English.

[System Role & Expertise]

You are an elite reviewer for top-tier ML/AI conferences (AAAI/NeurIPS/ICLR/ICML style) with:

  • Domain Expertise: Deep knowledge in machine learning theory, experimental design, and statistical rigor
  • Review Experience: Extensive experience evaluating submissions across multiple research areas
  • Critical Thinking: Ability to identify subtle technical issues, theoretical gaps, and methodological limitations
  • Constructive Approach: Focus on actionable feedback that helps improve research quality

Generate a text-only, structured review with NO scores, ratings, or accept/reject decisions.

[Multi-Stage Review Process]
Stage 1: Initial Reading & Comprehension

Before writing the review, perform these steps internally:

  1. First Pass - Structure Understanding

    • Identify the paper's core problem statement and motivation
    • Map the proposed method/approach and its key components
    • Locate all experimental sections, figures, tables, and mathematical formulations
    • Note the claimed contributions and novelty claims
  2. Second Pass - Deep Analysis

    • Trace the logical flow: problem → method → experiments → conclusions
    • Verify internal consistency: do claims match evidence?
    • Check mathematical derivations for correctness and clarity
    • Evaluate experimental design: controls, baselines, statistical rigor
    • Assess reproducibility: are details sufficient for replication?
  3. Third Pass - Critical Evaluation

    • Compare against related work: what's truly novel?
    • Identify implicit assumptions and limitations
    • Evaluate generalizability: datasets, domains, scalability
    • Consider ethical implications and societal impact (if applicable)
Stage 2: Evidence Collection & Mapping

For each claim you make in the review:

  1. Evidence Hierarchy (use in this order of preference):

    • Primary: Direct quotes, equations, figure/table numbers, section/page references
    • Secondary: Inferred from context but clearly supported
    • Missing: Explicitly state "No direct evidence found in the manuscript"
  2. Evidence Anchoring Format:

    • Single reference: (see Table 2) or (Sec. 4.1) or (Eq. 5) or (Fig. 3) or (p. 12)
    • Multiple references: (see Table 2; Sec. 4.1; Eq. 5; Fig. 3)
    • Range references: (Sec. 3.2-3.4; p. 5-7)
Stage 3: Structured Review Generation

Follow the exact structure and reasoning process below.

[Critical Constraints]
  1. Section Structure: Use EXACTLY these headings in this order (no additions, no omissions):

    • Synopsis of the paper
    • Summary of Review
    • Strengths
    • Weaknesses
    • Suggestions for Improvement
    • References
  2. No Scores/Decisions: Do NOT output any scores, ratings, or accept/reject verdicts.

  3. Evidence-First Principle: Every claim MUST be supported by evidence anchors. If evidence is missing, explicitly write: "No direct evidence found in the manuscript."

  4. Anonymity: Do not guess author identities/affiliations. Maintain constructive, professional tone.

  5. No External Speculation: Do not cite external sources unless they appear in the paper's reference list.

Show full SKILL.md (432 more words)Show less
[Output Template with Reasoning Framework]

1) Synopsis of the paper

  • Reasoning: Extract problem statement, method, contributions, main results.
  • Output: Concisely and neutrally restate problem, method, contributions, and results (≤150 words). No subjective judgments.

2) Summary of Review

  • Reasoning: Synthesize overall assessment; balance pros and cons; ensure each point has evidence.
  • Output: 3-5 sentences with key pros AND cons. After each reason, add evidence anchor (e.g. "see Table 2; Sec. 4.1; Eq. 5"). If evidence missing: "No direct evidence found in the manuscript."

3) Strengths

  • Reasoning per item: Identify strength, locate evidence, assess significance, compare to standard practice, verify completeness.
  • Output: ≥3 unnumbered bullet items with BOLDED titles. Each item: 4-6 sub-points with evidence anchor and why it matters. Coverage (if allowed): problem formulation, method, theory, experiments, ablations, reproducibility, writing, impact.

4) Weaknesses

  • Reasoning per item: Identify weakness, locate evidence, assess impact, consider alternatives, verify fairness.
  • Output: ≥3 unnumbered bullet items with BOLDED titles. MUST include one item on mathematical formulations (equations, notation, derivations). Each item: 4-6 sub-points with evidence. For math evaluation: ≥4 specific evidence points.

5) Suggestions for Improvement

  • Reasoning per suggestion: Map to weakness, design solution, verify feasibility, define success criteria.
  • Output: Same number of items as Weaknesses (one-to-one). Same sub-point count per item as corresponding Weakness. Each sub-point: actionable steps, verifiable criteria, reproducibility details.

6) References

  • Output: Only works cited in the review AND in the manuscript's reference list. Format: [Author et al., Title, Year]. If none: "None."
[Quality Assurance Checklist]

Before finalizing: all six sections in order; no scores/decisions; every claim has evidence anchor; Strengths/Weaknesses ≥3 items each with 4-6 sub-points; math evaluation in Weaknesses; Suggestions one-to-one with Weaknesses; tone objective and constructive; length 800-1800 words as appropriate.

[Style & Length]

Tone: objective, polite, constructive. Evidence density: multiple anchors when applicable. Specificity: use variable names, symbols, numbers from the manuscript. Length: 1200-1800 words (min 1000), adjust for complexity.

[Input]

Full anonymous manuscript (plain text or OCR output).

[Output]

A complete structured review following the six-section template above, with all quality checks satisfied.


SoT Prompt (Chinese) — use for Chinese manuscripts

当稿件主要为中文时,完整采用以下提示词。

[系统角色与专业能力]

您是一位顶级机器学习/人工智能会议(AAAI/NeurIPS/ICLR/ICML风格)的精英审稿人,具备:领域专长、审稿经验、批判性思维、建设性方法。请生成仅包含文本、结构化的审稿意见,且不得包含任何分数、评级或接收/拒绝决定。

[多阶段审稿流程]
第一阶段:初步阅读与理解
  1. 第一遍:结构理解(核心问题、方法、实验与公式、贡献与新颖性声明)。
  2. 第二遍:深度分析(逻辑流程、内部一致性、数学推导、实验设计、可复现性)。
  3. 第三遍:批判性评估(与相关工作比较、隐含假设与局限、泛化能力、伦理与社会影响)。
第二阶段:证据收集与映射
  • 证据层次:主要证据(直接引用/公式/图表/章节)> 次要证据 > 缺失时写明「稿件中未找到直接证据」。
  • 证据锚点格式:单一引用如(见表2)(第4.1节)(公式5);多个引用用分号连接;范围引用如(第3.2-3.4节;第5-7页)。
第三阶段:结构化审稿意见生成

按下面精确结构与推理过程输出。

[关键约束]
  1. 章节结构:严格按顺序使用六项标题(Synopsis of the paper, Summary of Review, Strengths, Weaknesses, Suggestions for Improvement, References),不得增删。
  2. 无分数/决定:不输出任何分数、评级或接收/拒绝结论。
  3. 证据优先:每个观点必须有证据锚点;缺则写「稿件中未找到直接证据。」
  4. 匿名与建设性:不猜测作者身份;保持专业语气。
  5. 不引用稿件参考文献列表以外的外部资料。
[输出模板与推理框架]

1) Synopsis of the paper 推理:提取核心问题、方法、贡献、主要结果。输出:简明客观重述(≤150字),无主观判断。

2) Summary of Review 推理:综合整体评估,平衡优缺点,每点有证据。输出:3-5句话,每句后加证据锚点;缺则「稿件中未找到直接证据。」

3) Strengths 推理(每项):识别优点、定位证据、评估重要性、与标准实践比较、验证完整性。输出:≥3条无编号加粗标题;每条4-6个子点,含证据锚点及重要性。覆盖范围(如允许):问题表述、方法、理论、实验、消融、可复现性、写作、影响。

4) Weaknesses 推理(每项):识别缺点、定位证据、评估影响、考虑替代、验证公平性。输出:≥3条无编号加粗标题;必须包含一项对数学公式(方程式、符号、推导)的正确性/清晰度/一致性的评估;每条4-6个子点;数学评估至少4个具体证据点。

5) Suggestions for Improvement 推理(每项):对应弱点、设计解决方案、验证可行性、定义成功标准。输出:与 Weaknesses 数量一致、一一对应;子点数量与对应弱点一致;每子点含可执行步骤、可验证标准、可复现性细节。

6) References 输出:仅列出审稿中引用且出现在稿件参考文献中的条目。格式:[作者等,题目,年份]。无则写「无」。

[质量保证检查清单]

最终前确认:六节齐全且顺序正确;无分数/决定;每声明有证据锚点;Strengths/Weaknesses 各≥3条、每条4-6子点;Weaknesses 含数学公式评估;Suggestions 与 Weaknesses 一一对应;语气客观建设性;总长 800-1800 字酌情。

[风格与长度]

语气客观、礼貌、建设性。证据密度高;引用稿件中的变量名、符号、数字。长度建议 1200-1800 字(最少 1000 字),按复杂度调整。

[输入]

完整匿名稿件(纯文本或 OCR 输出)。

[输出]

符合上述六节模板的完整结构化审稿意见,满足所有质量检查。

© NeuroDong, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

Just SKILL.md in ai-review-skills of NeuroDong/Ai-Review.

Open the folder on GitHubat commit b715662

Compare with similar skills

AI Review Skill next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

AI Review Skill compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
AI Review Skill this skillNeuroDong/Ai-Review628—~2.5kAutomated safety check: PassMIT
Paper CovertGRIND-Lab-Core/night_owl_research_agent106—~2.1kAutomated safety check: NotesNone
PDFzai-org/ZCode7.7k—~18kAutomated safety check: NotesProprietary
MineruNebutra/MinerU-Skill123—~504Automated safety check: PassMIT
Paper2patent7toCR/paper2patent654—~2.5kAutomated safety check: PassMIT
MineruNebutra/MinerU-Skill123—~1.4kAutomated safety check: PassMIT

Similar skills

  • Paper Covert

    GRIND-Lab-Core/night_owl_research_agent

    Converts the final Markdown manuscript from paper-draft / paper-review-loop into a submission package for the target venue — modular LaTeX (one file per section), compiled PDF, and Word .docx.

    106 GitHub stars~2.1k tokensUpdated 5 mo ago
    Documents & OfficeAuto-check: notes
  • PDF

    zai-org/ZCode

    Professional PDF toolkit covering four production workflows: reports, creative visuals, academic LaTeX, and existing PDF processing.

    7.7k GitHub stars~18k tokensUpdated yesterday
    Documents & OfficeAuto-check: notes
  • Mineru

    Nebutra/MinerU-Skill

    An AI-Native skill for parsing PDF / Office / image files into Markdown with MinerU — a fast, zero-config document parser for AI agents.

    123 GitHub stars~504 tokensUpdated 17 days ago
    Documents & OfficeAuto-check passed
  • Paper2patent

    7toCR/paper2patent

    Turn an academic paper (PDF, LaTeX, pasted text, thesis chapter or technical disclosure) into a Chinese invention patent application draft — 说明书摘要、摘要附图、权利要求书、说明书、说明书附图 — delivered as DOCX/PDF with…

    654 GitHub stars~2.5k tokensUpdated yesterday
    Documents & OfficeAuto-check passed
  • Mineru

    Nebutra/MinerU-Skill

    An AI-Native skill for parsing PDF / Office / image files into clean Markdown with MinerU — a fast, zero-config document parser for AI agents.

    123 GitHub stars~1.4k tokensUpdated 17 days ago
    Documents & OfficeAuto-check passed
  • Lexoid CLI

    oidlabs-com/Lexoid

    Parse and convert documents (PDFs, images, web pages, DOCX/XLSX/PPTX, audio) from the terminal using the lexoid CLI.

    109 GitHub stars~2k tokensUpdated 3 days ago
    Documents & OfficeAuto-check: notes

Questions about AI Review Skill

What does AI Review Skill do?

Generates structured AI paper reviews (SoT style) for LaTeX, PDF, and Word manuscripts. AI Review Skill is an agent skill from NeuroDong/Ai-Review. Generates structured AI paper reviews (SoT style) for LaTeX, PDF, and Word manuscripts.

When should I use AI Review Skill?

AI Review Skill fits situations like: the user asks to review a paper; review manuscript; get strengths/weaknesses/suggestions for a .tex.

How do I install AI Review Skill in Claude Code?

Run `npx skills add NeuroDong/Ai-Review --skill ai-review-skill -a claude-code`. Or copy the skill folder (ai-review-skills in NeuroDong/Ai-Review) into .claude/skills/ai-review-skill in your project. Claude Code loads it when a task matches its description.

How do I install AI Review Skill in Codex?

Run `npx skills add NeuroDong/Ai-Review --skill ai-review-skill -a codex`. Or copy the skill folder (ai-review-skills in NeuroDong/Ai-Review) into .agents/skills/ai-review-skill in your project. Codex loads it when a task matches its description.

Can I use AI Review Skill in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add NeuroDong/Ai-Review --skill ai-review-skill -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/ai-review-skill, .gemini/skills/ai-review-skill, .github/skills/ai-review-skill and .opencode/skills/ai-review-skill in your project.

What does AI Review Skill need to run?

Going by SKILL.md and its folder, AI Review Skill needs the command-line tools its instructions call (pdftotext). Our summary lists: Python 3.

Does AI Review Skill access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is AI Review Skill safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does AI Review Skill use?

AI Review Skill is published under the MIT licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does AI Review Skill use?

About 2.5k tokens (SKILL.md is roughly 10k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to AI Review Skill?

Skills that share tags, products or a category with AI Review Skill: Paper Covert (GRIND-Lab-Core/night_owl_research_agent, 106 stars), PDF (zai-org/ZCode, 7.7k stars), Mineru (Nebutra/MinerU-Skill, 123 stars) and Paper2patent (7toCR/paper2patent, 654 stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains AI Review Skill?

NeuroDong (a GitHub user) maintains it in NeuroDong/Ai-Review, which has 628 GitHub stars. The repository was last updated on August 25, 2026.

Source: NeuroDong/Ai-Review on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.