evidence-checker
Skill5 starsChanged 43 days agoMITView on GitHub
Use when reviewing factual claims, research notes, technical statements, or literature summaries against supplied evidence.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- AymanShams/codex-coding-ostheir own version, first seen Sep 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- AymanShams/codex-coding-os★ 1same 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 repository36 other files it gives its agents.
- bioinformatics-planningSkill
- biology-literature-analysisSkill
- biology-paper-analysisSkill
- chemistry-research-analysisSkill
- skill-authorSkill
- codebase-explorerSkill
- codebase-understandingSkill
- code-reviewSkill
- debug-systematicallySkill
- implementation-plannerSkill
- implementation-reviewSkill
- ledger-tasks-yyloSkill
- test-and-verifySkill
- algorithm-learningSkill
- system-design-basicsSkill
- defensive-security-reviewSkill
- threat-modelingSkill
- data-analysisSkill
- tutorSkill
- experiment-analysisSkill
- model-evaluationSkill
- numerical-methodsSkill
- mathematics-problem-solverSkill
- proof-solvingSkill
- physics-research-analysisSkill
- data-cleaningSkill
- data-visualizationSkill
- evidence-comparisonSkill
- experimental-planningSkill
- literature-synthesizerSkill
- reproducibility-auditSkill
- research-questionSkill
- source-verificationSkill
- api-designSkill
- frontend-planningSkill
- technical-editorSkill
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈4
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 28
Never fabricate a source, citation, result, statistic, experiment, or quotation.
- Distinctive: line 30
If the evidence is absent, say that it is absent.
- Distinctive: line 38
Use this skill when the task involves evidence checker and the user needs a structured, repeatable approach.
- Distinctive: line 64
Do not invent missing facts, data, citations, or project-specific behavior.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Evidence Checker
Goal
Prevent a draft from becoming stronger than its evidence.
For every important claim:
- Identify the claim.
- Locate supporting evidence in the supplied material.
- Classify it as:
- directly supported
- partially supported
- contradicted
- not established
- Explain the classification briefly.
- Identify missing context or alternative interpretations.
- Rewrite overly strong claims conservatively when requested.
Never fabricate a source, citation, result, statistic, experiment, or quotation.
If the evidence is absent, say that it is absent.
Purpose
Support users who need to reviewing factual claims, research notes, technical statements, or literature summaries against supplied evidence..
When to use
Use this skill when the task involves evidence checker and the user needs a structured, repeatable approach.
Instructions
Apply the guidance and checks above in sequence. Use the supplied context as the source of truth, make assumptions explicit, and verify important conclusions before presenting them.
Inputs
- The user's task, question, or objective.
- Relevant source material, data, constraints, and prior decisions.
- The required audience, depth, and output format, when specified.
Outputs
- A result tailored to the stated task and audience.
- The key steps, evidence, or reasoning needed to make the result understandable.
- Assumptions, checks, and unresolved limitations where relevant.
Example
Scenario: A user requests help with evidence checker and supplies the relevant context.
Expected result: Apply the guidance above, show the task-relevant result, and distinguish verified information from assumptions or open questions.
Limitations
Do not invent missing facts, data, citations, or project-specific behavior. State uncertainty where the supplied evidence is insufficient, and seek qualified human review when the task has material safety, legal, scientific, or operational consequences.
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.

