
citation-verification
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports ml-paper-writing by providing detailed verification principles and common error patterns.
- Installs
- 1.5K
- Last 24h
- —
- Trending rank
- —
- Security
- Not audited
Install
Works with every agent the skills CLI supports.
npx skills add https://github.com/galaxy-dawn/claude-scholar --skill citation-verification- 01
Install
Run the command in your project. The CLI asks which agents to install for.
- 02
Describe the task
Ask your agent for something this skill covers. It loads citation-verification automatically when relevant.
- 03
Review the result
The agent follows the SKILL.md steps, scripts and references bundled with the skill.
SKILL.md
The instructions your agent reads when the skill is triggered.
Citation Verification Reference Guide
A reference guide for citation verification in academic paper writing, providing verification principles and best practices.
Core Principle: Proactively verify every citation during the writing process using programmatic or canonical scholarly sources first: arXiv, DOI/CrossRef, Semantic Scholar, publisher landing pages, and Zotero metadata. Google Scholar is useful for manual discovery, but it is not the canonical verification authority.
Core Problems
Citation issues in academic papers seriously impact research integrity:
- Fake citations - Citing non-existent papers (common issue with AI-generated citations)
- Incorrect information - Mismatched authors, titles, years, etc.
- Inconsistent formatting - Mixed citation formats
- Missing citations - Referenced but uncited work
These issues can lead to:
- Paper rejection or retraction
- Damage to academic reputation
- Reviewers questioning research rigor
Special risk with AI-assisted writing: AI-generated citations have approximately 40% error rate; every citation must be verified via WebSearch.
Verification Principles
This skill provides verification principles based on canonical scholarly metadata and claim-level checking:
1. Proactive Verification (Verify During Writing)
Core idea: Verify immediately when adding a citation, rather than checking after writing is complete.
- Search for the paper via WebSearch each time a citation is needed
- Confirm the paper exists on Google Scholar
- Add to bibliography only after verification passes
2. Canonical Metadata Verification
Preferred authority order:
- DOI / publisher landing page
- arXiv ID or arXiv landing page
- CrossRef
- Semantic Scholar
- Zotero metadata imported from a verified identifier
- Google Scholar only for manual discovery or fallback lookup
Verification steps:
- Find a DOI, arXiv ID, publisher URL, or verified Zotero item.
- Confirm title, first author, year, venue, and identifier.
- Fetch BibTeX from CrossRef, arXiv, publisher metadata, Zotero, or another programmatic source when possible.
- If only Google Scholar can find the item, mark it as manual verification and do not treat the BibTeX as final until metadata is checked elsewhere.
3. Information Matching Verification
Information that must match:
- Title (minor differences allowed, e.g., capitalization)
- Authors (at least the first author must match)
- Year (±1 year difference allowed, considering preprints)
- Publication venue (conference/journal name)
4. Claim Verification
Key principle: When citing a specific claim, you must confirm the claim actually appears in the paper.
- Use WebSearch to access the paper PDF
- Search for relevant keywords
- Confirm the accuracy of the claim
- Record the section/page where the claim appears
Verification Workflow
Integration into Writing Process
Need a citation during writing
↓
Find DOI / arXiv ID / publisher page / verified Zotero item
↓
Verify metadata with CrossRef / arXiv / Semantic Scholar / publisher / Zotero
↓
Confirm paper details
↓
Get BibTeX
↓
(If citing a specific claim) Verify the claim
↓
Add to bibliography
Key point: Verification is part of the writing process, not a separate post-processing step.
Usage Guide
Using with ml-paper-writing
The verification principles of this skill are integrated into the Citation Workflow of the ml-paper-writing skill.
Auto-trigger: Citation verification is automatically executed when writing papers with the ml-paper-writing skill.
Manual reference: Refer to this skill when you need detailed verification principles.
Verification Step Example
Scenario: Need to cite the Transformer paper
Step 1: WebSearch lookup
Query: "Attention is All You Need Vaswani 2017"
Result: Found multiple sources for the paper
Step 2: Google Scholar verification
Query: "site:scholar.google.com Attention is All You Need Vaswani"
Result: ✅ Paper exists, 50,000+ citations, NeurIPS 2017
Step 3: Confirm details
- Title: "Attention is All You Need"
- Authors: Vaswani, Ashish; Shazeer, Noam; Parmar, Niki; ...
- Year: 2017
- Venue: NeurIPS (NIPS)
Step 4: Get BibTeX
- Click "Cite" on Google Scholar
- Select BibTeX format
- Copy BibTeX entry
Step 5: Add to bibliography
- Paste into .bib file
- Use \cite{vaswani2017attention} in the paper
Handling Verification Failures
If the paper cannot be verified through canonical sources:
- Check spelling - Is the title or author name correct?
- Try different queries - Use different keyword combinations
- Find alternative sources - Try arXiv, DOI, CrossRef, Semantic Scholar, publisher pages, or Zotero
- Mark as pending - Use
[CITATION NEEDED]marker - Notify the user - Clearly state the citation cannot be verified
If information doesn't match:
- Confirm the source - Did you find the correct paper?
- Check versions - Preprint vs. published version
- Update information - Use the most accurate version
- Record discrepancies - Note the reason for differences
Best Practices
Preventing Fake Citations
- Never generate citations from memory - AI-generated citations have 40% error rate
- Use WebSearch to find - Verify every citation through WebSearch
- Confirm on Google Scholar - Verify paper existence on Google Scholar
- Verify promptly - Verify when adding citations, don't wait until finished
Handling Verification Failures
- Don't guess - If you can't find the paper, don't fabricate information
- Mark clearly - Use
[CITATION NEEDED]to mark explicitly - Notify the user - Clearly state which citations cannot be verified
- Provide reasons - Explain why verification failed (not found, info mismatch, etc.)
Improving Verification Accuracy
- Complete queries - Include title, author, year
- Check citation count - Citation count on Google Scholar is a credibility indicator
- Confirm venue - Verify conference/journal name is correct
- Verify claims - When citing specific claims, confirm they exist in the paper
Common Pitfalls
❌ Wrong approach:
- Generating BibTeX from memory
- Skipping Google Scholar verification
- Assuming a paper exists
- Not marking unverifiable citations
✅ Correct approach:
- Search every citation with WebSearch
- Confirm on Google Scholar
- Copy BibTeX from Google Scholar
- Clearly mark unverifiable citations
Summary
Core Principle: Proactively verify every citation during the writing process using WebSearch and Google Scholar.
Key Steps:
- WebSearch to find the paper
- Google Scholar to verify existence
- Confirm details
- Get BibTeX
- Verify claims (if needed)
- Add to bibliography
Failure handling: When verification fails, mark as [CITATION NEEDED] and clearly notify the user.
Integration: The principles of this skill are integrated into the ml-paper-writing skill for automatic verification.
FAQ
What does the citation-verification skill do?
This skill provides reference guidance for citation verification in academic writing. Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy. This skill supports ml-paper-writing by providing detailed verification principles and common error patterns.
How do I install citation-verification?
Run npx skills add https://github.com/galaxy-dawn/claude-scholar --skill citation-verification in your project. The skills CLI detects the agents you use and copies the skill into the right folder. For Claude Code you can also place the skill folder at ~/.claude/skills/citation-verification/ (personal) or .claude/skills/citation-verification/ (project).
Which AI agents can use citation-verification?
Any agent that supports the open Agent Skills format (a folder with a SKILL.md file), including Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Windsurf, Cline, OpenCode and more.
Is citation-verification safe to install?
No partner security audit is available yet. Skills can run commands and scripts, so read the SKILL.md and any bundled files before installing.
Who maintains citation-verification?
It is published by galaxy-dawn in galaxy-dawn/claude-scholar. It has 1,453 recorded installs.
More from galaxy-dawn/claude-scholar
writing-anti-ai
galaxy-dawn/claude-scholar
This skill should be used when the user asks to "remove AI writing patterns", "humanize this text", "make this sound more natural", "remove AI-generated traces", "fix robotic writing", or needs to eliminate AI writing patterns from prose. Supports both English and Chinese text. Based on Wikipedia's "Signs of AI writing" guide, detects and fixes inflated symbolism, promotional language, superficial -ing analyses, vague attributions, AI vocabulary, negative parallelisms, and excessive conjunctive phrases.
paper-self-review
galaxy-dawn/claude-scholar
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.
review-response
galaxy-dawn/claude-scholar
Systematic review response workflow from comment analysis to professional rebuttal writing. Use when the user asks to "write rebuttal", "respond to reviewers", "draft review response", or "analyze review comments". Improves paper acceptance rates.
results-analysis
galaxy-dawn/claude-scholar
This skill should be used when the user asks to "analyze experimental results", "run strict statistical analysis", "compare model performance", "generate scientific figures", "check significance", "do ablation analysis", or mentions interpreting experiment data with rigorous statistics and visualization. It focuses on strict analysis bundles, not Results-section prose.
research-ideation
galaxy-dawn/claude-scholar
This skill should be used when the user asks to "brainstorm research ideas", "use 5W1H framework", "identify research gaps", "conduct gap analysis", "start research project", "conduct literature review", "define research question", "select research method", "plan research", or mentions research project initiation phase. Provides comprehensive guidance for research startup workflow from idea generation to planning.
ui-ux-pro-max
galaxy-dawn/claude-scholar
This skill should be used when the user asks to design or review a UI, create a landing page or dashboard, choose colors or typography, improve accessibility, or implement polished frontend interfaces with a clear design system.
Popular docs & writing skills
grill-with-docs
mattpocock/skills
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
lark-markdown
open.feishu.cn
飞书 Markdown:查看、创建、上传、编辑和比较飞书中的原生 Markdown 文件。当用户要操作飞书 Markdown 文件,或比较其远端版本及本地草稿时使用。纯本地 Markdown 文件操作不触发本 skill。不负责将 Markdown 导入为飞书在线文档,也不负责文件搜索、权限、评论、移动、删除等云空间管理操作。
writing-beats
mattpocock/skills
Writing, exploit; assemble raw material into a journey of beats, grounding each term before a beat leans on it.
writing-shape
mattpocock/skills
Writing, exploit: shape raw material into an article, paragraph by paragraph.
writing-fragments
mattpocock/skills
Writing, explore: mine raw fragments, no structure yet.
writing-for-agents
mattpocock/skills
Writing documents for agents. Use when creating or editing skills, or modifying AGENTS.md or CLAUDE.md.