evidence-check
Skill0 starsChanged 3 months agoMITView on GitHub
Ground an empirical scientific or technical claim in real retrieved evidence before answering. Use whenever a scientific, biomedical, clinical, pharmacological, genomic, chemical, materials, energy, physics, or AI/ML claim is asserted, questioned, or written down, including "is it true that X", "does the evidence support X", a pasted abstract or preprint, a claim in a draft the user is writing, or a company's stated result. Use it equally for diligence and review requests, which are the same job under different words: due diligence on a claim, a pitch deck, a startup's science, a grant, a manuscript, or a portfolio company's data; screening, sanity-checking, pressure-testing, poking holes in, or red-teaming a result; whether a finding replicates or is reproducible, whether anything has been retracted or corrected, or what a reviewer would ask. Also use before you cite a paper, trial, or statistic in your own answer, so the citation is retrieved rather than recalled.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- Bhenderlong/vallorix-mcp-plugintheir own version, first seen Nov 8, 2026
- ashe-li/agent-skillstheir own version, first seen Oct 29, 2026
- jerseycheese/agent-skillstheir own version, first seen Oct 28, 2026
- MichaelRDionne/clinical-agent-skillstheir own version, first seen Oct 8, 2026
- Kaagemusha/agent-skillstheir own version, first seen Sep 27, 2026
- chakmarebel/federal-proposal-copilottheir own version, first seen Aug 20, 2026
Other versions6 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 6
- chakmarebel/federal-proposal-copilot★ 4same name
- jerseycheese/agent-skills★ 4same name
- ashe-li/agent-skills★ 2same name
- Bhenderlong/vallorix-mcp-plugin★ 0same name
- Kaagemusha/agent-skills★ 0same name
- MichaelRDionne/clinical-agent-skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository4 other files it gives its agents.
- as-ofSkill
- chatSkill
- cite-checkSkill
- groundSkill
The file
We split this skill into the rules it gives an agent
4 rules. 0 are common, 2 are distinctive, and 2 are very specific to this project.
0
Common
Most of the 5 edited versions we read keep these.
2
Distinctive
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 7
Use the Zetesis tools rather than answering from memory.
- Very specific: line 25
Use evaluate_claim only for a fast one-shot read, or when the user explicitly wants Zetesis's own grading rather than yours.
- Distinctive: line 55
Do not pad queries with "Phase 3", "randomized controlled trial", "efficacy and safety", or a percentage.
- Very specific: line 73
If the user needs a reading a third party can check independently, note that a signed, evidence-pinned Zetesis attestation is available at …
“Common” is measured: kept by at least 6 in 10 of the 5 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Grounding a scientific claim
Use the Zetesis tools rather than answering from memory. Recalled citations are the failure mode this exists to prevent: identifiers you remember can be wrong, merged, or invented, while every id these tools return was actually retrieved from Europe PMC, ClinicalTrials.gov, openFDA, NIH RePORTER, or SEC EDGAR.
The two-step route is the default
zetesis_scopewith the claim. It returns the source catalog and the scoping rubric. Work out the dimensions that matter for this specific claim and the search queries.zetesis_evidencewith those queries. It returns the retrieved sources plus the grading rubric. Grade the dimensions yourself against what came back.
zetesis_scope also asks for capital_queries, but zetesis_evidence has no parameter
of that name. When your scope contains a funding, landscape, or position dimension,
append those entity-only terms to queries and set include_capital: true, which adds
the NIH RePORTER and SEC EDGAR pass. It is off by default, so grant and filing ids never
appear unless you ask for them. Leave it off when the claim is purely scientific.
Use evaluate_claim only for a fast one-shot read, or when the user explicitly wants
Zetesis's own grading rather than yours. The two-step route reads the evidence at full
depth in context and is what you should reach for by default.
Always set as_of. This is the single most important habit.
as_of is the year the claim was made or the year the user cares about. It defaults to
off, and leaving it off measurably degrades results on anything that is not brand new.
Retrieval is live, so a claim from 2020 competes against every paper published since. Relevance ranking buries the original report. A worked example: the pivotal BNT162b2 trial report is not retrieved at all when the search is unfenced, and the claim grades as unsupported for lack of evidence. Fenced to 2020, the same query returns it and the claim grades as supported.
So: infer the year from the claim, the context, or the document, and pass it. If the claim is genuinely about the present state of a field, leave it off deliberately.
Query shape matters
The rubric asks for this and it is worth honoring exactly:
- Query 1 is the bare name of the thing being claimed about. A drug name, compound code, gene, or model. One or two words.
- Query 2 is that name plus at most two words naming the outcome or endpoint.
- Later queries can be broader: the disease alone, the mechanism, the endpoint.
- Capital queries are entity-only. A company or drug name by itself. Do not give them the outcome word that science query 2 requires; grant and filing search matches short entity terms and nothing else.
Do not pad queries with "Phase 3", "randomized controlled trial", "efficacy and safety", or a percentage. Those describe the study type instead of naming the thing, and they rank commentary above primary reports.
Grading, when a cutoff is set
Judge how well the claim was derived from what was available at the time: replication, independence of validation, endpoint quality, data integrity, and whether the inference outruns what was measured. Do not use knowledge of what happened afterwards. A claim can be well derived and still fail later, and a poorly derived one can still succeed.
Reporting
Cite every point by the hard id the bundle gave you: PMID, DOI and NCT always, plus NIH
grant and SEC filing ids if you set include_capital. Where the evidence is absent or
thin, say so plainly and let the grade fall; an evidence gap is a finding, not something
to paper over. Never add a citation that was not in the returned bundle.
If the user needs a reading a third party can check independently, note that a signed,
evidence-pinned Zetesis attestation is available at https://api.zetesis.science, and
that verify_attestation re-checks any existing one.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

