القائمة
Confirm a paper actually exists (arXiv / Semantic Scholar / OpenAlex) before citing it. Use before writing any new citation.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | verify-citation |
| description | Confirm a paper actually exists (arXiv / Semantic Scholar / OpenAlex) before citing it. Use before writing any new citation. |
Verify that a paper exists before writing it as a citation.
Inspired by the citation-verification patterns in flonat/claude-research and Imbad0202/academic-research-skills.
Run /verify-citation before writing any new citation into a .tex, .bib,
or .md file. If the user asks you to "add a reference to X", run this skill
first — do not write the citation until verification passes.
/verify-citation "Author, Title, Year"
/verify-citation "the paper we discussed about spectral geometry"
/verify-citation (no argument — verify all citations in the last assistant turn)
Step 1 — Extract the citation. If an argument is given, use it. Otherwise, extract every paper reference from the last assistant turn (titles, author–year pairs, DOIs, arXiv IDs).
Step 2 — Search. For each citation, search at least two of:
https://arxiv.org/search/?searchtype=all&query=<title+author>https://api.semanticscholar.org/graph/v1/paper/search?query=<title>https://api.openalex.org/works?search=<title>Use WebSearch or WebFetch to run the searches.
Step 3 — Report verdict.
| Result | Action |
|---|---|
| Found on 2+ sources, title and authors match | VERIFIED — write the citation |
| Found on 1 source, minor title variation | LIKELY — note the discrepancy, write with caution |
| Found on 0 sources, or title/author mismatch | UNVERIFIED — do NOT write the citation |
For UNVERIFIED: say "I cannot confirm this paper exists. Do you have a DOI or arXiv ID?" Do not invent an alternative. Do not write a citation that cannot be verified.
Step 4 — Write the citation (VERIFIED and LIKELY only). Use the metadata from the verified source (exact title, exact authors, correct year). Never reconstruct citation details from memory — use what the database returned.
Add this to your project's CLAUDE.md to make this the default:
Never write a citation into any file without first running /verify-citation.
If you cannot confirm a paper exists on Semantic Scholar, arXiv, or OpenAlex,
say so explicitly and wait for a DOI or arXiv ID from me.
The write-side inverse of /check-pipeline and the pipeline-auditor — read a Pipeline/ doc (and/or an audit report) and EDIT the code accordingly: apply an optimization the pipeline describes, correct code the pipeline (backed by your authoritative notes) shows is wrong, or bring the code in line with the documented behavior. Use when the user wants the code changed based on the pipeline. High-stakes: bakes in live-editor editing, mirror sync, ground-truth protection, and control-gating. Proposes a diff and gets approval before any risky edit.
Check that a code and its Pipeline/ .md are still compatible — that every symbol, cell number, data file, and data-flow claim in the pipeline doc still matches the current code (drift detection). Use after editing a documented notebook/engine/script, before trusting a pipeline doc, or on request ("does the pipeline still match the code?"). Reports mismatches (missing symbols, wrong cell numbers, renamed functions, changed I/O) and can update the doc. Companion to /write-pipeline.
Write (or refresh) a Pipeline/ .md that documents the calculation-and-code pipeline of ANY large code in the project — a notebook (.wb/.nb/.ipynb), an engine, or a script. Use when a load-bearing code has no pipeline doc yet, when a new main code is added, or when the user asks to "write the pipeline" for a file. Produces the standard Purpose / data-flow diagram / key-symbols table / gotchas / inputs-outputs format used across Pipeline/, cross-referenced to the project's authoritative notes (workbook.tex).
Playbook for the Wolfbook MCP tools — driving the LIVE Wolfram kernel and a .wb/.nb notebook in VS Code from Claude Code (read/search/edit/run cells, evaluate expressions, checkpoint/restore kernel state, step-debug, look up symbols, find paclets, search INSPIRE/arXiv papers). Use whenever working through the Wolfbook MCP (mcp__wolfbook__*) instead of headless wolframscript: pick the right tool, avoid the multi-statement reparse and runCell bridge bugs, and use kernel checkpoints for safe rollbacks. Complements the wolfram-headless skill (which covers headless .wls runs).
Run heavy Wolfram Language (wolframscript) computations from Claude Code reliably, and diagnose the misleading "The product exited because of a license error". Use whenever invoking wolframscript on a non-trivial computation, when a wolframscript job dies with a "license error" despite a valid license, or when Wolfram numerics give silently wrong results in headless runs.
Convert Mathematica .nb or .m files to Wolfbook .wb format so they open and run in VS Code. Use when bringing existing .nb/.m files into Wolfbook, or to make an existing .wb bridge-safe.