← ClaudeAtlas

claim-checklisted

Walk every substantive claim in a section, classify it (cited / author's-own / common-knowledge / UNSUPPORTED), verify the citation licenses the claim's verb and quantifier, and report supported/overstated/uncited counts
tansuasici/claude-research-kit · ★ 0 · AI & Automation · score 75
Install: claude install-skill tansuasici/claude-research-kit
# Claim Check ## Core Rule Every substantive claim is one of four things: **cited**, **the author's own reasoning/data** (stated as such), **common knowledge** in the field, or **UNSUPPORTED**. A claim that is none of these does not belong in the manuscript yet. Never fabricate a citation to "fix" an uncited claim — flag it with `[CITE]` and tell the author what is missing. A plausible-looking reference you cannot point to is a fabrication, not a fix. This is the flagship skill. It is the manual, source-reading half of verification that a hook cannot do: `citation-gate.sh` proves a `\cite` key *resolves* to a `.bib` entry; only a reader can prove the entry *licenses* the sentence. ## When to Use Invoke with `/claim-check` when: - A section draft is "done" and you want to know what a skeptical Reviewer 2 would attack. - You inherited prose (yours or a co-author's) and need to know which sentences are load-bearing but unsourced. - Before submission, on the Introduction, Results, and Discussion — the three sections where overclaim hides. - After a revision that added claims, to confirm none slipped in uncited. Scope it: `/claim-check sections/discussion.tex` for one section, or name a paragraph. Checking a whole manuscript at once produces a table too long to act on — go section by section. ## Process ### Phase 1: Establish Ground Truth Before reading a single claim, load what the section is allowed to assert: 1. **Read `MANUSCRIPT_MAP.md`** — the Thesis, the Key sour