← ClaudeAtlas

citation-disciplinelisted

Use when adding, verifying or cleaning citations and BibTeX entries in Stage 07 (Writing), when a reference cannot be resolved cleanly from DBLP or CrossRef, when checking that a cited paper actually supports the claim attributed to it, or when filling citation_verification.json.
tangxiangru/AutoR · ★ 805 · AI & Automation · score 79
Install: claude install-skill tangxiangru/AutoR
# Citation discipline Stage 07 must write `workspace/artifacts/citation_verification.json`, and the gate checks it has a non-empty `claim_coverage` list where every entry carries a claim and at least one `citation_keys` or `source_ids` value. That file is a record of verification, so it is only worth anything if verification happened. `reference.md` in this directory is the long-form treatment: source APIs, the full verification workflow, BibTeX field rules, entry templates by publication type, and a troubleshooting table. Read it when a specific reference will not resolve. ## The rule that matters most **Never generate a citation from memory.** The dangerous failure is not an obviously fake reference. It is one that looks plausible: real authors with a fabricated title, a real title with the wrong year, a real arXiv ID attached to the wrong venue, a preprint and its published version silently merged into one entry. These survive a read-through and surface during review. If a citation cannot be verified programmatically or from the run's own `workspace/literature/sources.json`, mark it unresolved and say so. Do not produce a plausible-looking BibTeX entry to fill the hole. ## Verification loop For each citation: 1. **Resolve** the work against a source of record — DBLP for CS venues, CrossRef for DOIs, the publisher page, or arXiv for preprints. 2. **Match the metadata exactly**: authors, title, year, venue. A mismatch in any one of them means you have the wron