reference-verify
Verify references in an academic paper: check whether each BibTeX entry is real, whether in-text citations match the cited paper's actual content, and produce a structured verification report. Use when user says \"验证参考文献\", \"ref verify\", \"check references\", \"核实引用\", \"引用是否正确\", or wants to audit citations in a LaTeX manuscript.
Profile →npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill reference-verify --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Ref-Verify: 学术论文参考文献验证 Verify references for: **$ARGUMENTS** --- ## Purpose This skill performs a systematic audit of every reference cited in a LaTeX manuscript. For each citation it: 1. Confirms the BibTeX entry describes a **real, published paper** (not hallucinated). 2. Locates **every place** the reference is cited in the manuscript. 3. Extracts the **claim or viewpoint** the author attribu
What does the reference-verify skill do?
Verify references in an academic paper: check whether each BibTeX entry is real, whether in-text citations match the cited paper's actual content, and produce a structured verification report. Use when user says \"验证参考文献\", \"ref verify\", \"check references\", \"核实引用\", \"引用是否正确\", or wants to audit citations in a LaTeX manuscript.
How do I install it?
Run `npx skills add brycewang-stanford/Auto-Empirical-Research-Skills --skill reference-verify --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 brycewang-stanford/Auto-Empirical-Research-Skills, a repository with 3,244 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.