bibchecklisted

Audit an existing .bib file entry-by-entry against ground truth (DOI, Semantic Scholar, OpenAlex, arXiv) to catch the silent citation errors that pass spell-check but kill peer review — wrong year, mis-cited authors, wrong journal/volume, swapped title-author pairs, fabricated DOIs, and outright hallucinated entries (a real concern with LLM-assisted drafting). Spawns one narrow-focus subagent per entry so each citation gets full attention rather than the gradient-decay that single-pass audits suffer at scale. Use whenever the user says "/bibcheck", "audit my .bib", "verify references", "check my bibliography for errors", "any fake citations", "pre-submission bib audit", "did Claude hallucinate any of these", or before shipping a manuscript / R&R to Marketing Science, JMR, JCR, Management Science. Read-only and audit-only — never adds, edits, or removes entries; produces a PASS/WARN/FAIL report and a `corrected.bib` the user can diff and move into place themselves. Strictly distinct from `/cite` (which ADDS on
ericluo04/claude-academic-workflow · ★ 3 · AI & Automation · score 72

Install: claude install-skill ericluo04/claude-academic-workflow

# bibcheck — Per-Entry Bibliography Audit Audit-only sister skill to `/cite`. Given a `.bib` file, spawn one subagent per entry to verify the entry against canonical sources (DOI metadata, Semantic Scholar, OpenAlex, arXiv, Zotero). Report PASS / WARN / FAIL per entry with a one-line diagnostic, group by severity, and write a dated report plus a `corrected.bib` the user can review and merge themselves. Never overwrites the source `.bib`. **Why per-entry parallelism.** One agent asked to audit 80 entries in a single pass drifts: early entries get careful treatment, late entries get pattern-matched. Spawning one subagent per entry gives each citation a full attention budget and removes the late-batch quality cliff. This mirrors the structure of `/seven-pass-review` (parallel lenses) and `/audit-reproducibility` (per-claim checking). **The LLM-fabrication concern.** Hallucinated citations have a recognizable signature: plausible author names + plausible title + a DOI that 404s + no Semantic Scholar / OpenAlex / arXiv match anywhere. `/bibcheck` is built to surface exactly this pattern. ## When to use - **Pre-submission**: before MKSCI / JMR / JCR / MS submission or resubmission, especially for drafts where any text was AI-assisted. - **Inherited `.bib`**: when picking up a coauthor's or RA's bibliography and you don't know its provenance. - **Post-Zotero-export sanity check**: even Better BibTeX can carry forward bad upstream metadata. - **After a large `/litreview` batch**