anti-defensive-writing
Remove audit, defensive, self-critical, developer-facing and commitment writing from…
Verify that cited references actually exist and that their metadata matches, using the runnable scripts this skill ships for CrossRef, Semantic Scholar, arXiv, and PubMed. Use when the bibliography must be checked against live sources rather than inspected locally: detecting
$ npx -y skills add boom5426/nature-paper-skills --skill reference-audit-guide --agent claude-codeHow it fires
How this skill gets triggered: by you, by Claude, or both.
/reference-audit-guideContext preview
The summary Claude sees to decide when to auto-load this skill.
Verify that cited references actually exist and that their metadata matches, using the runnable scripts this skill ships for CrossRef, Semantic Scholar, arXiv, and PubMed. Use when the bibliography must be checked against live sources rather than inspected locally: detecting
name: reference-audit-guide description: >- Verify that cited references actually exist and that their metadata matches, using the runnable scripts this skill ships for CrossRef, Semantic Scholar, arXiv, and PubMed. Use when the bibliography must be checked against live sources rather than inspected locally: detecting fabricated or hallucinated citations, confirming that DOIs resolve, and matching title, authors, venue, and year against the record. Also covers the underlying verification principles and reference-audit best practices. For an offline hygiene pass over a .bib or .tex file, run citation-verifier first; for whether a real source supports the sentence citing it, run claim-source-verification.
Verification principles plus runnable citation checkers for academic writing.
This repository separates three citation questions that are routinely confused. Run them in order.
1. `citation-verifier`: is the bibliography a well-formed artifact? Duplicate keys, missing fields, DOI syntax, cited-but-undefined. Offline, immediate. 2. **This skill**: does the cited work exist, and does its metadata match what the manuscript says? Queries live scholarly APIs. This is the only stage that catches a fabricated citation carrying a well-formed DOI. 3. `claim-source-verification`: does the real, correctly-cited source actually support the sentence citing it?
None of the three substitutes for another. A clean local scan shows the bibliography is well-formed, not that the papers are real. A verified DOI shows the paper is real, not that it says what the sentence claims.
**Core Principle**: Proactively verify every citation during the writing process using trusted scholarly sources rather than memory.
Citation issues in academic papers seriously impact research integrity:
1. **Fake citations** - Citing non-existent papers 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:
This skill provides verification principles based on trusted scholarly sources:
**Core idea**: Verify immediately when adding a citation, rather than checking after writing is complete.
Prefer these sources:
**Information that must match**:
**Key principle**: When citing a specific claim, confirm the claim actually appears in the paper.
1. **Never generate citations from memory** 2. **Do not guess when verification fails** 3. **Mark unverifiable references clearly** 4. **Differentiate preprints from published versions** 5. **Verify the claim, not just the metadata**
From first draft to submission and rebuttal, build a clear, evidence-grounded manuscript. 27 skills for Codex and Claude Code, connecting structure, scientific writing, figures, citations and reviewer responses.
Remove audit, defensive, self-critical, developer-facing and commitment writing from…
Use when checking manuscript citations, bibliography hygiene, DOI or PMID completeness,…
Use when a manuscript's claims need to be checked against the sources cited for them, when…
Use when drafting, auditing, or revising Data Availability statements, repository plans,…
Use when a manuscript is being drafted across many sessions and needs auditable open-question…
Use when designing, restructuring, or auditing manuscript figures and you need to define one…