From claude-scholar
Critiques LaTeX manuscripts before submission via structured self-review, evaluating literature, novelty, and other criteria. Prompts for ownership confirmation.
npx claudepluginhub yy/claude-scholar --plugin claude-scholarThis skill uses the workspace's default tool permissions.
Systematically critique your own manuscript before submission. Evaluates the paper across several criteria, identifies weaknesses, and suggests improvements.
Audits academic and technical manuscripts pre-publication, producing section-level refactoring reports with citation hygiene and submission-readiness checks.
Generates structured peer review reports for academic manuscripts, evaluating novelty, methodological rigor, clarity, impact, and ethics. Use when critiquing papers or providing reviewer feedback.
Provides checklists to review academic paper structure, logic, citations, figures/tables, and writing clarity before submission.
Share bugs, ideas, or general feedback.
Systematically critique your own manuscript before submission. Evaluates the paper across several criteria, identifies weaknesses, and suggests improvements.
This skill is for reviewing your own work. Do not use it on others' unpublished manuscripts — uploading someone else's unpublished work to an AI system raises serious ethical concerns.
/presubmit-checks (which covers formatting and technical issues)Search in this order:
paper/current/main.texpaper/main.texmain.tex**/*.tex with \begin{document}Use the AskUserQuestion tool to collect setup in one step. Two questions:
"Is this your own manuscript?" (header: "Ownership")
"Should I search for potentially missing literature via OpenAlex?" (header: "Lit search")
/openalex.Read the manuscript thoroughly. Write a brief neutral summary covering:
This step ensures understanding before critiquing. Do not evaluate yet — just demonstrate that the work has been understood.
Work through each criterion. For each one that applies, identify specific weaknesses and suggest fixes. Skip criteria that are not relevant to the paper.
Is the paper well-situated in prior work? Key questions:
If literature gaps are suspected, note them and guide the user on what to ask Claude to search for. For example: "You could ask me to search OpenAlex for papers on [specific topic] by [specific authors/groups] to check whether key references are missing." Provide concrete query suggestions — topics, author names, keywords — so the user can decide whether to follow up.
If the user explicitly requests a literature search, use /openalex to run targeted queries derived from:
Present results as "potentially relevant papers to review" — clearly distinguish suspected gaps from confirmed missing prior work.
Are the methods appropriate and well-validated? Key questions:
Does the paper make claims that outrun the evidence? Key questions:
Is the data appropriate for the research question? Key questions:
How broadly do the findings apply? Key questions:
Does the paper explain how and why, not just what? Key questions:
Is the paper well-written and self-contained? Key questions:
Before writing, confirm with the user: "I'll save the critique as YYYY-MM-DD-critique-report.md next to the paper — okay?"
Use this structure:
# Manuscript Critique
**Date**: YYYY-MM-DD
**Paper**: [title or filename]
## Summary
(1-3 sentences)
## Top findings
### Top risks
The 3 most important weaknesses that reviewers are likely to flag.
### What to preserve
Key strengths that should survive revisions.
### Anticipated reviewer questions
Questions reviewers are likely to ask. Preparing answers strengthens the paper and cover letter.
## Detailed comments
(Criterion-by-criterion assessment. For each, note strengths, flag weaknesses with suggested fixes. Skip criteria that don't apply.)
### Literature and novelty
...
### Methodological rigor
...
### Causal claims and confounders
...
### Data quality and limitations
...
### Generalizability
...
### Mechanism
...
### Clarity and presentation
...
For each criterion section, anchor every critique point to a specific location in the manuscript (section, figure, table, paragraph, or quoted claim). Vague feedback like "the literature review has gaps" is not useful — instead: "Section 2 does not cite any work on [topic], despite claiming novelty in this area (paragraph 3)."
After writing the file, print a brief summary to the conversation highlighting the top findings. When flagging literature gaps, suggest specific keywords, author names, or research areas the user can ask Claude to search for.