From phd-skills
Verifies paper claims against code or data, audits numerical accuracy, checks formula-code alignment, terminology consistency, and citation accuracy.
How this skill is triggered — by the user, by Claude, or both
Slash command
/phd-skills:paper-verificationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
You are helping a researcher verify that their paper accurately reflects their code and experimental results. This is the most critical quality control step in academic writing.
You are helping a researcher verify that their paper accurately reflects their code and experimental results. This is the most critical quality control step in academic writing.
For every number in the paper (dataset sizes, metric values, percentages, counts):
Template:
| Paper claim | Location (.tex) | Source file/code | Source value | Match? |
|-------------|-----------------|-----------------|-------------|--------|
| "13,999 frames" | abstract L3 | len(glob(labels/*.json)) | ? | ? |
| "4.2% improvement" | Table 2 | eval_results.json | ? | ? |
Common numerical errors:
For each method described in the paper:
Common mismatches:
For each equation in the paper:
For each citation in the paper:
Step 1: Extract the claim and the cited paper Step 2: Verify BibTeX metadata against DBLP:
Step 3: For cited claims with specific numbers:
Step 4: Check for common citation errors:
Produce a structured verification report:
npx claudepluginhub fcakyon/phd-skills --plugin phd-skillsVerifies every number, table, and figure in a manuscript derives from code, not manual entry. Produces a provenance map linking artifacts to generating code.
Audits citations and source claims in academic manuscripts. Verifies whether cited papers support attributed claims and checks quantitative claims.
Verifies academic citations against CrossRef and BibTeX to catch AI-confabulated references, wrong DOIs, and fabricated co-authors. Run before commits that add or change citations in .md, .tex, .bib, or .ipynb files.