From tooluniverse
Cross-validates a specific scientific claim against 3+ independent databases, decomposing it into testable assertions and reporting concordance across sources.
How this command is triggered — by the user, by Claude, or both
Slash command
/tooluniverse:cross-validate [a specific testable claim, e.g. 'BRAF V600E is FDA-approved indication for vemurafenib in melanoma' or 'TP53 mutations occur in >50% of breast cancers']The summary Claude sees in its command listing — used to decide when to auto-load this command
Cross-validate this claim against independent databases: $ARGUMENTS A single source for a high-stakes fact is fragile. Force 3+ sources from DIFFERENT databases (not 3 tools that all wrap the same upstream API). ## Process ### 1. Decompose the claim into testable assertions A claim like "BRAF V600E is FDA-approved indication for vemurafenib in melanoma" has three independent assertions: - (a) BRAF V600E exists as an annotated cancer variant - (b) Vemurafenib is FDA-approved - (c) The approved indication includes BRAF-V600E-positive melanoma Each assertion can be confirmed/refuted separ...
Cross-validate this claim against independent databases: $ARGUMENTS
A single source for a high-stakes fact is fragile. Force 3+ sources from DIFFERENT databases (not 3 tools that all wrap the same upstream API).
A claim like "BRAF V600E is FDA-approved indication for vemurafenib in melanoma" has three independent assertions:
Each assertion can be confirmed/refuted separately. Write them out before calling tools — this is the anchor for what you'll verify.
For a numeric claim ("X% of breast cancers carry TP53 mutations"), the assertion is the value itself; cross-validate by getting the same number from independent cohorts.
"Independent" means different upstream maintainers, not different tools wrapping the same API. Examples:
| Domain | Independent sources |
|---|---|
| Drug approvals | OpenFDA, ChEMBL, DrugBank — each maintains its own approval table |
| Variant pathogenicity | ClinVar (NIH), CIViC (academic crowd-sourced), OncoKB (MSKCC), gnomAD frequency (Broad) |
| Gene-disease association | OpenTargets (composite), DisGeNET, OMIM, GenCC |
| Mutation frequency in cancer | TCGA (GDC), COSMIC, IntOGen — each samples different cohorts |
| Clinical trial existence | ClinicalTrials.gov, EU CTR, ChiCTR |
| Protein function | UniProt, Reactome, KEGG |
| Pharmacology | DrugBank, ChEMBL, PharmGKB, FDA Label |
Pick 3. If the claim's domain only has 2 truly-independent sources, note that in the report — don't fabricate a third.
Use tu run <tool> per source. Don't shortcut to a compound tool that aggregates
multiple sources — that defeats the cross-validation point. Track each source's
verdict separately:
Source 1 (ClinVar): CONFIRMS — V600E listed as Pathogenic, condition: Melanoma
Source 2 (CIViC): CONFIRMS — V600E linked to vemurafenib sensitivity in melanoma
Source 3 (OncoKB): CONFIRMS — V600 variant Level 1 evidence for vemurafenib in melanoma
If a source returns "no record found", that's not the same as "refutes" —
mark it as INDETERMINATE and note possible reasons (different namespace,
absent in that database, query string mismatch).
If a source explicitly contradicts (e.g., gnomAD shows population frequency
suggesting it's a benign polymorphism), that's REFUTES.
Format:
## Claim
<verbatim claim>
## Verdict: <CONFIRMED | DISPUTED | UNSUPPORTED>
## Per-source results
| Source | Verdict | Evidence | Date |
|---|---|---|---|
| ClinVar | CONFIRMS | V600E Pathogenic for Melanoma | 2025-Q4 |
| CIViC | CONFIRMS | V600E + vemurafenib (Level A) | 2026-01 |
| OncoKB | CONFIRMS | Level 1: vemurafenib in BRAF V600 melanoma | 2026-Q1 |
## Concordance: 3/3 confirm
## Caveats
- All three databases share clinical-trial sourcing (overlapping evidence)
- (Or:) Sources disagree on dosing — ClinVar lists 240mg BID; OpenFDA label lists 960mg BID
The verdict logic:
End with a "Caveats" section flagging:
UNREACHABLE, replace with one
alternate. Don't retry.npx claudepluginhub matheus-rech/tooluniverse --plugin tooluniverse3plugins reuse this command
First indexed May 21, 2026
/cross-validateCross-validates a specific scientific claim against 3+ independent databases, decomposing it into testable assertions and reporting concordance across sources.
/fact-checkVerify a claim, section, or manuscript against scientific literature and report confidence levels
/cross-referenceCross-references ENCODE experiments with external databases by linking identifiers. Supports PubMed, GEO, ClinicalTrials.gov, and bioRxiv.
/craft-research-verifyVerify existing research findings against independent primary sources. Upgrades confidence from 'sources agree' to 'independently verified.'
/factcheckVerifies BibTeX entries and cited claims in research papers by cross-referencing author names, venues, years, and numerical claims against DBLP and web sources. Produces a structured correction report.
/researchResearches evidence for PR/FAQ claims or topics from .tex files, generates biblatex citations, caches results, and offers to update documents.