Agent skill · Security

citation-audit

Zero-context verification that every bibliographic entry in the paper is real, correctly attributed, and used in a context the cited paper actually supports. Uses a fresh cross-model reviewer with web/DBLP/arXiv lookup to catch hallucinated authors, wrong years, fabricated venues, version mismatches, and wrong-context citations (cite present but the cited paper does not establish the claim). Use when user says \"审查引用\", \"check citations\", \"citation audit\", \"verify references\", \"引用核对\", or before submission to ensure bibliography integrity.

majiayu000github.com/majiayu000GitHub ↗
claude-codecan modify filesMIT
Install
npx skills add majiayu000/claude-skill-registry --skill citation-audit-wanshuiyin-auto-claude-code-res --agent claude-code

Same command for any agent — swap --agent for codex, cursor, copilot.

Facts
Files in the skill folder: 2
SKILL.md size: 15 KB
Bundled scripts: none
Allowed tools: Bash(*)ReadGrepGlobEditWriteAgentWebSearchWebFetch
Path: skills/analysis/citation-audit-wanshuiyin-auto-claude-code-res/SKILL.md
Open the folder on GitHub →
Where it comes from
Stars: 534
Language: HTML

Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.

From the SKILL.md

# Citation Audit Verify every `\cite{...}` in a paper against three independent layers: 1. **Existence** — the cited paper actually exists at the claimed arXiv ID / DOI / venue. 2. **Metadata correctness** — author names, year, venue, and title match canonical sources (DBLP, arXiv, ACL Anthology, Nature, OpenReview, etc.). 3. **Context appropriateness** — the cited paper actually supports the claim it is being used to support in the manuscript. This skill is the fourth layer of \aris{}'s evidence-and-claim assurance, complementing `experiment-audit` (code), `result-to-claim` (science verdict), and `paper-claim-audit` (numerical claims). Together they form a bottom-up integrity stack from raw evaluation code to manuscript bibliography. ## When to Use This Skill **Run before submission.** The right gating point is: - After `paper-write` has produced the LaTeX draft and bib file - After `paper-claim-audit` has verified numerical claims - Before final `paper-compile` for submission **Do not** run this on a half-written draft — most of the work is in cross-checking each `\cite` against context, which is wasted on placeholder text. ## What This Skill Catches The dangerous citation proble

What's inside
Steps it walks through
  1. When to Use This Skill
  2. What This Skill Catches
  3. Constants
  4. Workflow
  5. Step 1: Discover bib file and section files
  6. Step 2: Extract all (cite-key, context) pairs
  7. Step 3: Send each entry to fresh cross-model reviewer
  8. Step 4: Aggregate verdicts
  9. Step 5: Generate human-readable report
  10. Step 6: Apply fixes (interactive)
  11. Step 7: Recompile and verify
  12. Key Rules
  13. Comparison with Other Audit Skills
  14. Known Limitations
Ships with 1 file
  • metadata.json
Commands it runs
latexmk -C && latexmk -pdf -interaction=nonstopmode main.tex
More from claude-skill-registry
All skills →
About this skill
What does the citation-audit skill do?

Zero-context verification that every bibliographic entry in the paper is real, correctly attributed, and used in a context the cited paper actually supports. Uses a fresh cross-model reviewer with web/DBLP/arXiv lookup to catch hallucinated authors, wrong years, fabricated venues, version mismatches, and wrong-context citations (cite present but the cited paper does not establish the claim). Use when user says \"审查引用\", \"check citations\", \"citation audit\", \"verify references\", \"引用核对\", or before submission to ensure bibliography integrity.

How do I install it?

Run `npx skills add majiayu000/claude-skill-registry --skill citation-audit-wanshuiyin-auto-claude-code-res --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.

Where does this skill come from?

From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.

Is a popular skill a good skill?

Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.

Keep going