Source profileQuality 85/100

Galaxy-Dawn/claude-scholar/skills/citation-verification/SKILL.md

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.

Source repository stars
4,981
Declared platforms
0
Static risk flags
0
Last source update
2026-07-17
Source checked
2026-08-04

Decision brief

What it does—and where it fits

A reference guide for citation verification in academic paper writing, providing verification principles and best practices.

Best for

  • Use when the user asks about "citation verification best practices", "how to verify references", "preventing fake citations", or needs guidance on citation accuracy.

Not for

  • Tasks that require unconfirmed production actions or broad system permissions.
  • Environments where the pinned source and install steps cannot be inspected.

Compatibility matrix

Platform support, with evidence labels

PlatformStatusEvidenceWhat to check
CodexNot declaredNo explicit evidencePortability before use
Claude CodeNot declaredNo explicit evidencePortability before use
CursorNot declaredNo explicit evidencePortability before use
Gemini CLINot declaredNo explicit evidencePortability before use
Open the compatibility checker

Installation

Inspect first. Install second.

The source command is displayed only when detected. A safe inspection prompt is always available so your agent can explain every action before execution.

Source-detected install commandSource
npx skills add https://github.com/Galaxy-Dawn/claude-scholar --skill "skills/citation-verification"
Safe inspection promptEditorial

Inspect the Agent Skill "citation-verification" from https://github.com/Galaxy-Dawn/claude-scholar/blob/2f7766fd541a723d4ddc6230b3277f948d61b093/skills/citation-verification/SKILL.md at commit 2f7766fd541a723d4ddc6230b3277f948d61b093. List every install step, command, network request, credential, file read/write, external action, and rollback step. Explain whether it fits my task. Do not install or execute anything until I approve.

Workflow

What the source asks the agent to do

  1. 01

    Verification Principles

    This skill provides verification principles based on canonical scholarly metadata and claim-level checking:

    Search for the paper via WebSearch each time a citation is neededConfirm the paper exists on Google ScholarAdd to bibliography only after verification passes
  2. 02

    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 neededConfirm the paper exists on Google ScholarAdd to bibliography only after verification passes
  3. 03

    2. Canonical Metadata Verification

    Preferred authority order: 1. DOI / publisher landing page 2. arXiv ID or arXiv landing page 3. CrossRef 4. Semantic Scholar 5. Zotero metadata imported from a verified identifier 6. Google Scholar only for manual discovery or fallback lookup

    DOI / publisher landing pagearXiv ID or arXiv landing pageCrossRef
  4. 04

    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)

    Title (minor differences allowed, e.g., capitalization)Authors (at least the first author must match)Year (±1 year difference allowed, considering preprints)
  5. 05

    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 PDFSearch for relevant keywordsConfirm the accuracy of the claim

Permission review

Static risk signals and limitations

No configured static risk pattern was detected

This is not proof of safety. Runtime behavior, indirect dependencies, and hidden external systems are outside the static scan.

Evidence record

Why each signal appears

EvidenceSourceComputedTestedEditorial
SignalValueEvidence typeMeaning
Quality score85/100ComputedDocumentation, specificity, maintenance, and trust rules
Repository stars4,981SourceRepository attention, not individual Skill quality
Compatibility0 platformsSourceDeclared in the catalog source record
Usage guideautomated source guideEditorialGenerated or reviewed according to the visible evidence level

Pinned source

Provenance and original SKILL.md

Repository
Galaxy-Dawn/claude-scholar
Skill path
skills/citation-verification/SKILL.md
Commit
2f7766fd541a723d4ddc6230b3277f948d61b093
License
MIT
Collected
2026-08-04
Default branch
main
View the original SKILL.md

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:

  1. Fake citations - Citing non-existent papers (common issue with AI-generated citations)
  2. Incorrect information - Mismatched authors, titles, years, etc.
  3. Inconsistent formatting - Mixed citation formats
  4. 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:

  1. DOI / publisher landing page
  2. arXiv ID or arXiv landing page
  3. CrossRef
  4. Semantic Scholar
  5. Zotero metadata imported from a verified identifier
  6. Google Scholar only for manual discovery or fallback lookup

Verification steps:

  1. Find a DOI, arXiv ID, publisher URL, or verified Zotero item.
  2. Confirm title, first author, year, venue, and identifier.
  3. Fetch BibTeX from CrossRef, arXiv, publisher metadata, Zotero, or another programmatic source when possible.
  4. 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:

  1. Check spelling - Is the title or author name correct?
  2. Try different queries - Use different keyword combinations
  3. Find alternative sources - Try arXiv, DOI, CrossRef, Semantic Scholar, publisher pages, or Zotero
  4. Mark as pending - Use [CITATION NEEDED] marker
  5. Notify the user - Clearly state the citation cannot be verified

If information doesn't match:

  1. Confirm the source - Did you find the correct paper?
  2. Check versions - Preprint vs. published version
  3. Update information - Use the most accurate version
  4. Record discrepancies - Note the reason for differences

Best Practices

Preventing Fake Citations

  1. Never generate citations from memory - AI-generated citations have 40% error rate
  2. Use WebSearch to find - Verify every citation through WebSearch
  3. Confirm on Google Scholar - Verify paper existence on Google Scholar
  4. Verify promptly - Verify when adding citations, don't wait until finished

Handling Verification Failures

  1. Don't guess - If you can't find the paper, don't fabricate information
  2. Mark clearly - Use [CITATION NEEDED] to mark explicitly
  3. Notify the user - Clearly state which citations cannot be verified
  4. Provide reasons - Explain why verification failed (not found, info mismatch, etc.)

Improving Verification Accuracy

  1. Complete queries - Include title, author, year
  2. Check citation count - Citation count on Google Scholar is a credibility indicator
  3. Confirm venue - Verify conference/journal name is correct
  4. 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:

  1. WebSearch to find the paper
  2. Google Scholar to verify existence
  3. Confirm details
  4. Get BibTeX
  5. Verify claims (if needed)
  6. 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.

Alternatives

Compare before choosing

Computed 10023,781

alirezarezvani/claude-skills

app-store-optimization

App Store Optimization (ASO) toolkit for researching keywords, analyzing competitor rankings, generating metadata suggestions, and improving app visibility on Apple App Store and Google Play Store. Use when the user asks about ASO, app store rankings, app metadata, app titles and descriptions, app store listings, app visibility, or mobile app marketing on iOS or Android. Supports keyword research and scoring, competitor keyword analysis, metadata optimization, A/B test planning, launch checklist

Computed 10014,225

wanshuiyin/Auto-claude-code-research-in-sleep

citation-audit

Use it for operations and research tasks; the detail page covers purpose, installation, and practical steps.

Computed 9832,606

K-Dense-AI/scientific-agent-skills

dask

Distributed computing for larger-than-RAM pandas/NumPy workflows. Use when you need to scale existing pandas/NumPy code beyond memory or across clusters. Best for parallel file processing, distributed ML, integration with existing pandas code. For out-of-core analytics on single machine use vaex; for in-memory speed use polars.

Computed 9832,606

K-Dense-AI/scientific-agent-skills

neurokit2

Use NeuroKit2 to build or audit reproducible research workflows for physiological time-series preprocessing, event/interval analysis, multimodal alignment, variability, and complexity. Trigger when code imports neurokit2 or needs its current APIs, schemas, and method-aware validation—not for diagnosis or device validation.