research-verification
Skill34 starsChanged 37 days agoMITView on GitHub
Independently assess research claims against supplied evidence before they are relied upon.
In this repository31 other files it gives its agents.
- .github/AGENTS.mdAGENTS.md
- tui/AGENTS.mdAGENTS.md
- actionability-passSkill
- agent-memory-opsSkill
- blocked-page-retrievalSkill
- brain-consistency-auditorSkill
- brainstorm-panelSkill
- concurrent-push-integrationSkill
- curation-auditSkill
- decomposed-local-researchSkill
- dual-model-reconciliationSkill
- eval-integritySkill
- file-organizationSkill
- fleet-model-routingSkill
- fleet-operational-runbookSkill
- generate-review-fix-loopSkill
- guard-target-correctnessSkill
- honesty-stop-gateSkill
- large-file-cartographerSkill
- local-lane-build-loopSkill
- local-model-onboardingSkill
- model-routing-tableSkill
- multi-agent-code-workflowSkill
- peer-drop-watcherSkill
- protected-function-guardSkill
- research-dispatchSkill
- research-workflowSkill
- shared-brain-bookkeepingSkill
- should-weSkill
- task-dependency-sequencingSkill
- verify-running-buildSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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 9
Before reporting a finding, ask an independent verifier to classify each claim against the actual evidence as supported, contradicted, …
- Distinctive: line 22
Keep the initial evidence judgment separate from summary-assisted review.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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
Research Verification
Overview
Before reporting a finding, ask an independent verifier to classify each claim against the actual evidence as supported, contradicted, unsupported, or overstated. This is a lightweight claim gate, not a replacement for multi-source reconciliation on high-stakes research.
Procedure
- Preserve the exact claim, its producer, and the primary evidence available.
- Select a verifier different from the producer and suitable for the subject.
- Supply the task, rubric and primary evidence, especially for numbers, dates, quotations and precise technical assertions; retain an initial evidence-based judgment before showing the producer's evaluative summary, then assess that summary separately as attributed information rather than ground truth.
- Require a verdict and reasoning for each claim. Hold unsupported claims; correct or flag contradicted and overstated claims.
- Escalate contested or reliability-critical research to independent source reconciliation.
Rules
- Independence is essential: a model's self-review is not the same as independent verification.
- Plausibility-only checks are weak for precise facts; evidence context is the preferred mode.
- Choose a verifier with appropriate safety and subject-matter limitations for sensitive topics.
- Keep the initial evidence judgment separate from summary-assisted review; the research-team protocol cites both the adversarial-report harm and the honest-report improvement, so this rule is not a claim that all summaries degrade accuracy.
Pitfalls
- Calling an unsupported number verified because it sounds plausible.
- Using the producing worker as the only verifier.
- Treating a local claim check as a complete evidence review.
Verification checklist
- Producer and verifier differ.
- Primary evidence was provided where available.
- Unsupported and overstated claims were withheld or clearly labeled.
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.

