Skip to content
Back to skills

Verify Citations

ASecurity

Audit every entry in a BibTeX file against the Corbis paper index and cross-check LaTeX citation keys when a manuscript is available

  • 11 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added May 27, 2026
developmentpython

Security analysis

A100/100

Scanned September 26, 2026

npx -y skills add Agentic-Assets/corbis-literature-starter-kit --skill verify-citations --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Verify Citations?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Verify Citations
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/agentic-assets-verify-citations/badge)](https://www.skillsdirectory.com/skills/agentic-assets-verify-citations)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: verify-citations
description: Audit every entry in a BibTeX file against the Corbis paper index and cross-check LaTeX citation keys when a manuscript is available
user_invocable: true
---

# Verify Citations

Audit the whole `.bib` file, including entries that a manuscript does not cite. Corbis `verify_bibtex` resolves entries against its paper index and reports field-level corrections. An unresolved entry remains unverified, not false.

## Inputs

- `/verify-citations` finds the project's `.bib` file. If more than one plausible file exists, use the manuscript's `\bibliography{}` or `\addbibresource{}` reference when available; otherwise ask which file to audit.
- `/verify-citations path/to/references.bib` audits that full file without requiring a `.tex` file.
- `/verify-citations path/to/paper.tex` locates its bibliography and also checks in-text citation keys.
- `/verify-citations --key key_name` audits one entry from the selected bibliography.

## Workflow

1. Read the selected `.bib` file. Never send credentials, private notes, or unrelated files with it.
2. Call `verify_bibtex` with `bibtexContent` set to the raw BibTeX content and `maxEntries` large enough for the file (up to 200). For larger bibliographies, split on complete BibTeX entries into batches of at most 200. Check `totalEntries`, `parsedCount`, `parseErrors`, and every returned entry so no record is silently skipped.
3. Report each entry as **OK** (resolved, no corrections), **CORRECTION** (resolved, with field-level differences), **UNVERIFIED** (unresolved), or **PARSE ERROR**. Show the proposed correction and its Corbis basis; do not silently alter the `.bib` file. Verify consequential differences against the publisher, DOI landing page, or paper PDF before applying them.
4. Run `python utils/citation_keys.py path/to/references.bib --tex path/to/main.tex` when a manuscript exists. The helper scans the manuscript and included `.tex` files for natbib commands, including `\cite`, `\citep`, `\citet`, and optional-argument forms. It reports missing keys and unused bibliography entries separately. Without a manuscript, run it with the `.bib` path alone to list every entry. This is a key-coverage check, not metadata verification.
5. Save the report to `output/citation_audit.md` with file paths, total/parsed/resolved/unresolved counts, parse errors, corrections, missing keys, and unused entries. Append a dated entry to `notes/lab_notebook.md`.

If `verify_bibtex` is unavailable for the current connection, say so and verify entries using `search_papers` followed by `get_paper_details_batch` for discovered IDs. Label any entry that still lacks a source **UNVERIFIED**. Never invent a citation or copy unverified supplied metadata into a verified bibliography.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.