- name
SKILL.md
The skill file stays in the publisher's repository.
Paste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add fcakyon/labrat --skill paper-check -a cursor -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add fcakyon/labrat --skill paper-check -a claude-code -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add fcakyon/labrat --skill paper-check -a codex -yPaste the copied command in a terminal. It installs this SKILL.md into that agent.
npx skills add fcakyon/labrat --skill paper-check -a grok -ySend the copied message in a Grok Bot chat. The Bot fetches this SKILL.md from GitHub and adds it to the skills all your Bots share.
Install this skill: https://github.com/fcakyon/labrat/tree/HEAD/plugin/skills/paper-checkFrom the publisher
Every number, method claim and citation in the paper must trace to code, data, results or a cited source. Output a prioritized list of issues with specific fixes.
For a code release request, follow references/code-release.md and skip Steps 1-4.
**/*.tex)When you run the checks yourself, read the full paper, or the sections the user names. When you hand checks to subagents, pass them the file paths from items 1-5 instead.
Run all six checks by default. When the user names specific checks (for example only citations or BibTeX), run only those, and only the Step 1 items they need (check 5 needs just the .bib files and the \cite sites).
The checks are independent. If the harness supports subagents, they can run in parallel, one check each. Each check returns a structured list of findings.
For every number in the paper (dataset sizes, metric values, percentages, counts):
Record each number as a row of the Numerical Audit table in Output Format.
Common numerical errors:
For each method or algorithm described in the paper:
Common mismatches:
For each equation in the paper:
Read the .bib file(s). Search the .tex files for citation patterns (\cite{...}, \citep{...}, \citet{...}) to find where each entry is used. Check every entry. For a quick pass, spot-check the 5 most important citations.
Extract the claim and the cited paper key.
Use paper-search tool get_crossref_paper_by_doi <doi> to retrieve the cited record. For an arXiv paper, use paper-search download arxiv <id> and paper-search read arxiv <id>. Follow paper search setup if the CLI is missing. Inspect the PDF itself when text extraction loses table or equation layout.
Verify BibTeX metadata against DBLP. Search DBLP for the paper title via web search (query: site:dblp.org "paper title") and check:
Flag any discrepancy with the corrected value.
For cited claims with specific numbers:
Read the evaluation scripts and result files. Check for:
Run the evaluation if possible and compare its output to the paper's values.
Merge all findings into one prioritized list:
Before reporting, check the findings:
Refine any finding that fails these checks.
## Paper Check Report
### Summary
- Files checked: N .tex files, M code files, K result files
- Issues found: X HIGH, Y MEDIUM, Z LOW
### HIGH
1. [Check] Description
- Paper says: "..." (file:line)
- Code/data shows: "..." (file:line)
- Suggested fix: specific replacement text
### MEDIUM
[Same format]
### LOW
[Same format]
### Numerical Audit
| Paper claim | Location (.tex) | Source file/code | Source value | Match? |
|-------------|-----------------|-----------------|-------------|--------|
### Unverified Claims
| .tex location | Claim | Cited paper | Status | Suggestion |
|--------------|-------|------------|--------|------------|
### Corrected BibTeX Entries
(Ready-to-paste corrected entries for any that need fixing, each with a comment naming its DBLP or Crossref source)
### Verified Claims
(Claims checked and correct)
Tag each issue with its check name.
For HIGH priority issues that have clear fixes (wrong numbers, typos, stale values):
>
---name: paper-checkdescription: >---# plugin/skills/paper-check/SKILL.mdFAQ
Download plugin/skills/paper-check/SKILL.md from the publisher, or copy the path and open the repository. PlugMCP lists the skill and does not host the file.
The publisher keeps it at https://github.com/fcakyon/labrat.
Claude, Cursor, Codex, and Grok Build can read a SKILL.md you add from the publisher's repository. Grok Bot installs it when you send the skill's GitHub folder link in a chat.