citation-verifier
Skill661 starsChanged 36 days agoMITView on GitHub
Use when checking manuscript citations, bibliography hygiene, DOI or PMID completeness, placeholder references, or BibTeX consistency before submission or revision.
7 other projects use a version of this, 1 of them edited.
Adopted by
Most recently taken up by
- TidalPaladin/skillstheir own version, first seen Nov 8, 2026
- papersflow-ai/papersflow-skillstheir own version, first seen Nov 8, 2026
- jkitchin/knowhowtheir own version, first seen Nov 1, 2026
- Nero1688/claude-academic-skillstheir own version, first seen Oct 20, 2026
- AlpaZZ/office-agent-skillstheir own version, first seen Oct 7, 2026
- KhaledSaeed18/dotclaudetheir own version, first seen Jul 4, 2026
Other versions7 projects use a version of this.
Word for word · 0
None found.
Edited · 1
- Chanw-research/claude-code-paper-writing★ 4295% same
Wrote their own version · 6
- jkitchin/knowhow★ 42same name
- Nero1688/claude-academic-skills★ 13same name
- KhaledSaeed18/dotclaude★ 5same name
- papersflow-ai/papersflow-skills★ 4same name
- AlpaZZ/office-agent-skills★ 1same name
- TidalPaladin/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository26 other files it gives its agents.
- anti-defensive-writingSkill
- claim-source-verificationSkill
- data-availabilitySkill
- draft-marker-disciplineSkill
- figure-plannerSkill
- manuscript-optimizerSkill
- paper-bootstrapSkill
- paper-workflowSkill
- rebuttal-responseSkill
- results-section-revisionSkill
- review-article-architectureSkill
- scientific-prose-styleSkill
- scientific-writingSkill
- stats-reporting-auditSkill
- submission-auditSkill
- write-scientific-manuscriptSkill
- figure-styleSkill
- nature-figureSkill
- academic-presentationsSkill
- conference-paper-writingSkill
- reference-audit-guideSkill
- academic-researcherSkill
- paper-analyzerSkill
- results-analysisSkill
- paper-reviewerSkill
- nature-portfolio-playbookSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. 0 are common, 13 are distinctive, and 1 is very specific to this project.
0
Common
Most of the 6 edited versions we read keep these.
13
Distinctive
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 10
Use this skill when citation integrity is the bottleneck.
- Very specific: line 12
Use this skill together with scientific-writing or submission-audit, not instead of them.
- Distinctive: line 25
Use this skill when:
- Distinctive: line 32
Do not use this skill for:
- Distinctive: line 39
Start with a local citation scan before any online verification.
- Distinctive: line 49
Use it to find:
- Distinctive: line 57
Treat imported BibTeX and Google Scholar-style exports as draft metadata, not as verified truth.
- Distinctive: line 62
Remove or flag all placeholder citations.
- Distinctive: line 63
Check BibTeX-key uniqueness and obvious identifier gaps.
- Distinctive: line 72
Only then finalize formatting for the venue.
- Distinctive: line 76
When you report field-level mismatches, grade each one so authors fix the dangerous ones first:
- Distinctive: line 84
Author-order reversal: verify the first author specifically, not just that all names are present.
- Distinctive: line 90
Prefer this order when moving beyond local scans:
- Distinctive: line 108
When using this skill, report:
“Common” is measured: kept by at least 6 in 10 of the 6 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Citation Verifier
Overview
Use this skill when citation integrity is the bottleneck. It is narrower and more operational than general writing skills: the goal is to catch unverifiable references, missing identifiers, duplicated BibTeX keys, placeholder citations, and mismatches between local citation artifacts before they become submission problems.
Use this skill together with scientific-writing or submission-audit, not instead of them.
This is stage one of three. It shows the bibliography is well-formed; it cannot show that the
cited papers are real, and it cannot show that a real paper supports the sentence citing it.
Hand the surviving entries to reference-audit-guide (optional set, installed with --set all),
which queries CrossRef, Semantic Scholar, arXiv, and PubMed to confirm existence and match
metadata, then to claim-source-verification for claim-to-evidence support. When
reference-audit-guide is not installed, say that existence was not machine-verified rather than
letting a clean local scan stand in for it. A fabricated citation carrying a well-formed DOI passes this skill
and fails the next one.
When To Use
Use this skill when:
- a manuscript is close to submission or resubmission
- the bibliography may contain placeholders, guessed entries, or stale metadata
- a
.bibfile needs a hygiene pass - the draft mixes DOI, arXiv, PMID, or plain-text references inconsistently
- you need to verify that local citation artifacts are ready before manual or online source verification
Do not use this skill for:
- generic literature discovery from scratch
- full manuscript restructuring
- venue formatting that does not depend on citation integrity
Local First Pass
Start with a local citation scan before any online verification.
The helper script:
python ~/.agents/skills/citation-verifier/scripts/scan_citations.py path/to/file_or_dir [...]
# Claude Code (global install): replace ~/.agents/skills with ~/.claude/skills
# Claude Code (project-local install): replace ~/.agents/skills with .claude/skillsUse it to find:
[CITATION NEEDED]or similar placeholdersPLACEHOLDER_...citation keysTODO: verifymarkers- DOI, arXiv, and PMID tokens
- LaTeX
\cite{...}keys - duplicate BibTeX keys inside
.bibfiles
Treat imported BibTeX and Google Scholar-style exports as draft metadata, not as verified truth.
Verification Order
- Scan the local draft and bibliography artifacts.
- Remove or flag all placeholder citations.
- Check BibTeX-key uniqueness and obvious identifier gaps.
- Normalize metadata fields that are commonly wrong in copied BibTeX:
- author list and spelling
- year
- venue or journal name
- volume, issue, pages, or article number
- DOI versus preprint identifier
- For every citation that matters to a scientific claim, verify the paper exists in trusted sources.
- If a claim depends on a specific result, confirm the cited paper actually supports that claim. For a systematic pass over many such claims, hand off to
claim-source-verification: existence and metadata checks do not catch a real paper made to carry a conclusion it does not reach. - Only then finalize formatting for the venue.
Severity Grading
When you report field-level mismatches, grade each one so authors fix the dangerous ones first:
- Critical (must fix): wrong or fabricated first author, reversed author order, a DOI that resolves to a different paper, a title whose core terms do not match, or a page range off by five or more.
- Warning (verify): volume-year inconsistent with the DOI-registration year, a missing or extra issue number, a missing middle initial, a page range off by one to four, or an ambiguous publisher-name variant.
- Info (note only): title case versus sentence case, abbreviated versus full journal name, and punctuation or conjunction differences (
andversus&).
Two checks are easy to miss and worth running explicitly:
- Volume-year versus DOI-year: a citation whose stated volume-year differs from the year encoded in the DOI or the online-publication date is a common sign of a miscopied entry.
- Author-order reversal: verify the first author specifically, not just that all names are present; a reversed or shifted author list still passes a set-membership check.
Roll each reference up to one confidence verdict: verified, check_suggested (has a Warning), needs_fix (has a Critical), or unverifiable (no source could confirm it).
Trusted Verification Sources
Prefer this order when moving beyond local scans:
- publisher page or DOI resolver
- PubMed for biomedical papers
- arXiv for preprints
- Crossref or Semantic Scholar for metadata cross-checking
- Google Scholar only as a fallback discovery aid, not as the sole source of truth
Common Failure Modes
- writing BibTeX from memory
- leaving placeholder citation keys in the draft
- assuming an arXiv preprint and published version are interchangeable
- citing a paper correctly but using it to support a claim it does not make
- letting duplicate BibTeX keys silently overwrite entries
- blindly trusting copied Scholar or BibTeX metadata for venue names, pages, years, or DOI fields
Output Standard
When using this skill, report:
- placeholder or unverifiable items
- duplicate or suspicious BibTeX keys
- missing or inconsistent DOI/arXiv/PMID information
- suspicious metadata fields that need manual correction
- claims that still need source verification
- the minimum safe next step before submission
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

