citation-audit
Skill340 starsChanged 7 months agoMITView on GitHub
Verify that every citation in a manuscript is real, correctly attributed, and accurately described. Detects ghost papers, wrong arXiv IDs, inverted claims, and dead links by fetching each cited work. Optional fix mode applies bib metadata corrections and surfaces prose rewrites for claim errors. Triggers on: "check my citations", "verify references", "citation audit", "are my references real", "check bib", "reference check", "bib audit", "citation verification". Companion to manuscript-review (Pass 5 hygiene); this skill audits factual truth.
We split this skill into the rules it gives an agent
18 rules. 0 are common, 14 are distinctive, and 4 are very specific to this project.
0
Common
Most of the 9 edited versions we read keep these.
14
Distinctive
This author's own choices. Worth a look.
4
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 17
Verify every citation in a manuscript against its actual source.
- Distinctive: line 32
All three are invisible to structural audits (cross-reference checks, compilation tests).
- Distinctive: line 63
If the fetched paper has a DIFFERENT title/authors than the bib entry, this is a WRONG ID or GHOST PAPER
- Distinctive: line 67
Search for the paper by title + author on the web
- Distinctive: line 68
Verify: venue, year, author list
- Distinctive: line 69
If the paper cannot be found at the stated venue, flag as
- Distinctive: line 74
Verify it loads and the content matches the described resource
- Distinctive: line 75
If the URL is dead or redirects to unrelated content, flag as
- Distinctive: line 163
NEVER trust your own knowledge of papers.
- Very specific: line 173
When a bib entry has both an eprint (arXiv ID) and a booktitle (venue), verify both independently.
- Distinctive: line 178
When the user invokes with an argument containing "fix" or "on", execute Phases 1–4 as above, then apply fixes for every non-PASS citation.
- Very specific: line 229
After user decisions, apply prose changes to the .tex file
- Very specific: line 230
Verify: re-read the .bib and .tex to confirm all fixes applied
- Very specific: line 231
Update the audit report: mark each finding as [FIXED], [RESOLVED], or [DEFERRED]
- Distinctive: line 236
NEVER invent a replacement citation.
- Distinctive: line 239
NEVER change the manuscript's argument.
- Distinctive: line 241
NEVER remove a citation without user confirmation, even if it is a ghost paper.
- Distinctive: line 243
When fixing URLs, always verify the new URL loads and contains the expected content before writing it.
“Common” is measured: kept by at least 6 in 10 of the 9 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 Audit Skill
Purpose
Verify every citation in a manuscript against its actual source. LLMs hallucinate citations, invent arXiv IDs, misattribute findings, and confuse authors. This skill catches all of that by fetching and reading each cited work.
Why This Exists
LLMs are unreliable with citations in three distinct ways:
- Ghost papers — The paper does not exist. Title, authors, or venue are fabricated.
- Wrong metadata — The paper exists but the bib entry has the wrong arXiv ID, wrong authors, wrong year, or wrong venue.
- Inverted claims — The paper exists and the bib is correct, but the manuscript mischaracterizes what the paper says.
All three are invisible to structural audits (cross-reference checks, compilation tests). They require reading the actual cited work.
Inputs
- The manuscript
.texfile(s) - The
.bibfile - Web access (to fetch papers from arXiv, conference sites, URLs)
Execution
Phase 1: Extract citation contexts
For each \citep{}, \citet{}, \cite{} in the manuscript:
- Record the bib key
- Record the surrounding sentence or paragraph (the claim context)
- Classify the claim type:
- FACTUAL: "X et al. found Y" / "X et al. measured Y"
- METHODOLOGICAL: "We follow X" / "We use the benchmark from X"
- POSITIONAL: "Unlike X, we..." / "X does not measure..."
- PARENTHETICAL: "(X, 2024)" — no specific claim, just a reference
- For FACTUAL and POSITIONAL claims, extract the specific assertion the manuscript makes about the cited work
Phase 2: Verify bib entry metadata
For each bib entry, verify against the actual source:
For arXiv papers (eprint field present):
- Fetch
https://arxiv.org/abs/{eprint_id} - Compare: title, authors, year
- If the fetched paper has a DIFFERENT title/authors than the bib entry, this is a WRONG ID or GHOST PAPER
For conference/journal papers (booktitle or journal field):
- Search for the paper by title + author on the web
- Verify: venue, year, author list
- If the paper cannot be found at the stated venue, flag as UNVERIFIABLE or GHOST PAPER
For web resources (howpublished with URL):
- Fetch the URL
- Verify it loads and the content matches the described resource
- If the URL is dead or redirects to unrelated content, flag as DEAD LINK
For each entry, check:
- Paper exists (reachable via arXiv, DOI, URL, or web search)
- Title matches (exact or near-exact)
- Authors match (at least first author correct)
- Year matches
- Venue matches (if applicable)
- Entry type appropriate (
@inproceedingsfor conferences,@articlefor journals,@miscfor preprints/blogs)
Phase 3: Verify claim accuracy
For each FACTUAL or POSITIONAL claim:
- Read the cited paper (abstract + relevant sections at minimum)
- Compare the manuscript's claim against what the paper actually says
- Classify:
- ACCURATE — The claim faithfully represents the cited work
- INACCURATE — The claim mischaracterizes the cited work
- INVERTED — The claim says the opposite of what the paper found
- OVERCLAIMED — The claim is stronger than what the paper supports
- UNDERCLAIMED — The cited work supports a stronger claim than stated
- UNVERIFIABLE — Cannot access the paper to verify
For INACCURATE and INVERTED findings, provide:
- What the manuscript claims
- What the cited paper actually says
- The specific section/page of the cited paper that contradicts the claim
- A suggested correction
Phase 4: Check for missing citations
Scan the manuscript for:
- Claims that cite no source but should (empirical claims without attribution)
- Tools, benchmarks, or datasets mentioned by name without citation
- Methods described as "standard" or "well-known" that have a canonical citation
Output Format
Per-citation report
### [bib_key] — [VERDICT]
**Bib entry:** [title] by [authors] ([year])
**Actual paper:** [actual title] by [actual authors] ([actual year])
**Metadata match:** title [✓/✗] | authors [✓/✗] | year [✓/✗] | venue [✓/✗]
**Claim in manuscript (line N):** "[exact text]"
**What the paper actually says:** "[summary of actual finding]"
**Claim accuracy:** [ACCURATE / INACCURATE / INVERTED / OVERCLAIMED / UNDERCLAIMED]
**Fix required:** [description of what needs to change, or "None"]Summary table
| Bib Key | Exists | Metadata | Claim | Verdict |
|---------|--------|----------|-------|---------|
| key1 | ✓ | ✓ | ✓ | PASS |
| key2 | ✓ | ✗ | ✗ | FAIL |
| key3 | ✗ | — | — | GHOST |Verdict categories
- PASS — Paper exists, metadata correct, claims accurate
- METADATA — Paper exists, bib entry has errors (wrong ID, wrong authors, wrong year)
- CLAIM — Paper exists, metadata correct, but manuscript mischaracterizes it
- GHOST — Paper does not exist as described
- DEAD — URL/link is broken
- UNVERIFIABLE — Cannot access the paper to verify
Severity
- CRITICAL: GHOST papers, INVERTED claims
- HIGH: Wrong arXiv IDs, wrong authors, INACCURATE claims
- MEDIUM: Wrong year, wrong venue, OVERCLAIMED
- LOW: Missing citations, incomplete bib entries, UNDERCLAIMED
Important notes
- NEVER trust your own knowledge of papers. ALWAYS fetch and verify. Your training data contains hallucinated citations. The only way to verify is to read the actual source.
- For arXiv papers, always fetch the abstract page to confirm the paper exists and matches.
- For conference papers, search DBLP, ACM DL, or the conference site.
- WebFetch and WebSearch are your primary tools. Do not skip verification because a citation "looks right."
- Blog posts and documentation URLs change. Always check that the URL still works and points to the described content.
- When a bib entry has both an
eprint(arXiv ID) and abooktitle(venue), verify both independently.
Phase 5: Fix (when invoked with "fix" or "on")
When the user invokes with an argument containing "fix" or "on", execute Phases 1–4 as above, then apply fixes for every non-PASS citation.
What to auto-fix (no user confirmation needed)
These are mechanical corrections with a single correct answer:
METADATA errors (paper exists, bib entry wrong):
- Wrong arXiv ID → replace
eprintwith the correct ID - Wrong authors → replace with authors from the actual paper
- Wrong year → replace with year from the actual paper
- Wrong title → replace with title from the actual paper
- Wrong venue → replace with venue from the actual paper
- Wrong entry type → change
@misc/@inproceedingsas appropriate
DEAD links:
- URL redirects → update
howpublishedURL to the final destination - URL 404 but resource found at different URL → update URL
- URL 404 and resource gone → flag as HUMAN-REQUIRED
Minor author corrections:
- Misspelled author names → fix spelling
- Missing authors from author list → add them
- Collective author name where individual names are available → replace (keep collective name as a note if it is how the group identifies)
What requires HUMAN-REQUIRED decision
Present these and wait for the user:
GHOST papers:
- Paper does not exist at all → present options: (a) Replace with a real paper that makes the same point (b) Remove the citation and adjust the prose (c) The user knows the paper exists and provides the correct reference
INVERTED or INACCURATE claims:
- The manuscript says X about a paper that actually says Y → present:
- What the manuscript claims
- What the paper actually says
- A suggested rewrite of the prose that accurately represents the paper
- Whether the paper still supports the manuscript's argument (and how)
- Let the user decide the final wording
Dead URLs with no replacement found:
- Blog post / resource deleted with no archive or alternative
Fix procedure
- Apply all auto-fixes to the
.bibfile - For each HUMAN-REQUIRED item, present the options clearly
- After user decisions, apply prose changes to the
.texfile - Verify: re-read the
.biband.texto confirm all fixes applied - Update the audit report: mark each finding as
[FIXED],[RESOLVED], or[DEFERRED]
Safety rules
- NEVER invent a replacement citation. If a ghost paper needs replacing, search for real papers that make the cited point. Present candidates to the user with abstracts. Let the user choose.
- NEVER change the manuscript's argument. If an inverted claim needs fixing, present the rewrite as a suggestion, not an edit.
- NEVER remove a citation without user confirmation, even if it is a ghost paper. The user may know something you do not.
- When fixing URLs, always verify the new URL loads and contains the expected content before writing it.
Save report as
[name]-citation-audit.md in the manuscript directory.
Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
- wanshuiyin/Auto-claude-code-research-in-sleep★ 18ksame name
- Chanw-research/claude-code-paper-writing★ 42same name
- catalsqlb-cmd/Prism-H★ 16same name
- seandavi/scriptorium★ 5same name
- raja21068/AutoResearch★ 2same name
- tansuasici/claude-research-kit★ 2same name
- khadinakbarlabs/vibelocal★ 0same name
- kurtvalcorza/citation-audit★ 0same name
- talhaMah56/claude_skills★ 0same 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.
Used alongsideProjects with it also use figure-spec, comm-lit-review-claude-single and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
raja21068Skillfigure-spec
Generate deterministic publication-quality architecture, workflow, and pipeline diagrams from structured JSON (FigureSpec) into editable SVG. Use when user says \"架构图\", \"workflow 图\", \"pipeline 图\", \"确定性矢量图\", \"figure spec\", \"draw architecture\", or needs precise, editable, publication-ready vector diagrams. Preferred over AI illustration for formal architecture/workflow figures.
Also in 4 projects that use this
raja21068Skillcomm-lit-review-claude-single
Communications-domain literature review with Claude-style knowledge-base-first retrieval. Use when the task is about communications, wireless, networking, satellite/NTN, Wi-Fi, cellular, transport protocols, congestion control, routing, scheduling, MAC/PHY, rate adaptation, channel estimation, beamforming, or communication-system research and the user wants papers, related work, a survey, or a landscape summary. Search Zotero, Obsidian, and local paper folders first when available, then search IEEE Xplore, ScienceDirect, ACM Digital Library, and broader web in that order.
Also in 3 projects that use this
rongaredeSkillsemantic-scholar
使用 Semantic Scholar API 检索和验证学术论文。支持并发多关键词搜索、批量 ID/DOI 查询、引用分析、批量补全摘要、统一 Markdown 导出。覆盖 2.14 亿+ 学术论文,无需 API Key 即可使用。触发词:论文检索、论文验证、Semantic Scholar、S2 搜索、查论文、补全摘要、导出MD
Also in 4 projects that use this
Yusong-EnceladusSkillfeishu-notify
Send notifications to Feishu/Lark. Internal utility used by other skills, or manually via /feishu-notify. Supports push-only (webhook) and interactive (bidirectional) modes. Use when user says \"发飞书\", \"notify feishu\", or other skills need to send status updates.
Also in 3 projects that use this
- +8 more from raja21068
In this repository94 other files it gives its agents.
- AGENTS.mdAGENTS.md
- adr-writerSkill
- agent-builderSkill
- animateSkill
- api-docs-generatorSkill
- appraiseSkill
- architecture-diagramSkill
- architecture-reviewerSkill
- arxiv-figuresSkill
- arxiv-packageSkill
- arxiv-preflightSkill
- benchmark-runnerSkill
- changelog-composerSkill
- chart-claritySkill
- codebase-advisorSkill
- code-refinerSkill
- competitive-analyzerSkill
- concept-to-imageSkill
- debug-investigatorSkill
- decision-mapSkill
- dependency-auditSkill
- devils-advocateSkill
- domain-modelingSkill
- engineering-retroSkill
- env-validatorSkill
- estimate-calibratorSkill
- feasibility-assessorSkill
- figure-rhetoricSkill
- figure-table-qualitySkill
- filesystemSkill
- githubSkill
- gpu-optimizerSkill
- handoffSkill
- html-presentationSkill
- html-videoSkill
- humanizeSkill
- idea-validatorSkill
- immuneSkill
- intakeSkill
- kg-builderSkill
- launch-videoSkill
- learning-workspaceSkill
- lightpanda-browserSkill
- linkedin-post-styleSkill
- literature-reviewSkill
- manuscript-provenanceSkill
- manuscript-reviewSkill
- manuscript-typographySkill
- market-analyzerSkill
- marp-slidesSkill
- mcp-to-skillSkill
- md-to-pdfSkill
- migration-risk-analyzerSkill
- milestone-runnerSkill
- module-deepeningSkill
- notebooklmSkill
- package-evaluatorSkill
- package-optimizerSkill
- paper-to-skillSkill
- plan-promptsSkill
- The first 60 shown.
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.

