agent-identifier
Use when creating or configuring Claude Code agents and their frontmatter.
This skill should be used when the user asks to "review paper quality", "check paper completeness", "validate paper structure", "self-review before submission", "audit claims", "check overclaiming", "verify whether results support claims", or mentions systematic paper quality
$ npx -y skills add Galaxy-Dawn/claude-scholar --skill paper-self-review --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/paper-self-reviewContext preview
The summary Claude sees to decide when to auto-load this skill.
This skill should be used when the user asks to "review paper quality", "check paper completeness", "validate paper structure", "self-review before submission", "audit claims", "check overclaiming", "verify whether results support claims", or mentions systematic paper quality
name: paper-self-review description: This skill should be used when the user asks to "review paper quality", "check paper completeness", "validate paper structure", "self-review before submission", "audit claims", "check overclaiming", "verify whether results support claims", or mentions systematic paper quality checking. Provides comprehensive quality assurance checklist for academic papers. version: 0.1.0
A systematic paper quality checking tool that helps researchers conduct comprehensive self-review before submission.
Check whether all sections of the paper are complete and conform to academic standards:
Verify the logical coherence of the paper:
Check the completeness and accuracy of citations:
Check whether the paper's claims are supported by the available evidence:
This audit does not replace `results-analysis` for statistics or `citation-verification` for bibliographic verification. It checks whether paper claims correctly use the available evidence.
Evaluate the quality and effectiveness of figures and tables:
Check writing clarity and readability:
Use this checklist for systematic paper self-review:
Paper Quality Checklist: - [ ] Abstract includes problem, method, results, contributions - [ ] Introduction clearly states research motivation - [ ] Method is reproducible - [ ] Results support conclusions - [ ] Main claims are supported by named evidence - [ ] Over-strong claims are weakened or removed - [ ] Discussion addresses limitations - [ ] All figures/tables have captions - [ ] Citations are complete and accurate
Use this skill in the following scenarios:
Follow these steps for systematic paper review:
Start with the overall structure, checking if all sections are complete and logically coherent.
Dive into each section, checking content accuracy and completeness.
Check whether each major claim is supported by the evidence available in the draft, analysis bundle, citations, or project notes.
Use this output shape:
## Claim Audit Claim: Verdict: keep | weaken | revise | remove Evidence used: Missing evidence: Overclaim risk: Suggested wording:
Verify the completeness and accuracy of all citations.
Check the quality and captions of all figures and tables.
Review language expression and writing clarity.
Use the quality checklist for final verification.
The Paper Self-Review skill provides a systematic paper quality checking process, helping researchers identify and resolve issues before submission, improving paper quality and acceptance rates.
Load only what is needed:
Semi-automated research assistant for academic research and software development. Supports Claude Code, Codex CLI, Kimi Code CLI, and OpenCode across ideation, coding, experiments, writing, and publication.
Repo: Galaxy-Dawn/claude-scholar
Use when creating or configuring Claude Code agents and their frontmatter.
Use only when creating new registrable ML components that require Factory or Registry patterns.
This skill should be used when the user asks to "debug this", "fix this error", "investigate this bug", "troubleshoot this issue", "find the problem",…
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how…
This skill should be used when the user asks to review a diff or pull request, write review comments, audit code quality, establish review standards, or…
This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command…