fact-checking
Skill3.4k starsChanged 2 months agoMITView on GitHub
Review and validate claims using counter-hypothesis testing. Use when verifying technical content, checking references, validating API endpoints, or performing quality assurance on deliverables.
6 other projects use a version of this.
Adopted by
Most recently taken up by
- axiomantic/spellbooktheir own version, first seen Nov 1, 2026
- KMaruthi2002/universal-llm-skillstheir own version, first seen Oct 25, 2026
- microsoft/github-vteam-industry-demosword for word, first seen Oct 25, 2026
- nimadorostkar/Claude-Skills-collectiontheir own version, first seen Oct 13, 2026
- ccgargantua/gars-claude-skillstheir own version, first seen Sep 16, 2026
- github/gh-awword for word, first seen May 27, 2026
Other versions6 projects use a version of this.
Word for word · 2
- github/gh-aw★ 5.6k100% same
- microsoft/github-vteam-industry-demos★ 2100% same
Edited · 0
None found.
Wrote their own version · 4
- nimadorostkar/Claude-Skills-collection★ 33same name
- axiomantic/spellbook★ 11same name
- ccgargantua/gars-claude-skills★ 1same name
- KMaruthi2002/universal-llm-skills★ 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 repository247 other files it gives its agents.
- .github/agents.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- packages/squad-cli/templates/copilot-instructions.mdCopilot instructions
- packages/squad-sdk/templates/copilot-instructions.mdCopilot instructions
- .squad-templates/copilot-instructions.mdCopilot instructions
- .squad/templates/copilot-instructions.mdCopilot instructions
- templates/copilot-instructions.mdCopilot instructions
- action-skill-contractsSkill
- agent-collaborationSkill
- agent-conductSkill
- architectural-proposalsSkill
- architectural-reviewSkill
- archival-integritySkill
- ci-validation-gatesSkill
- client-compatibilitySkill
- cli-wiringSkill
- content-scopeSkill
- distributed-meshSkill
- documentation-maintenanceSkill
- github-multi-accountSkill
- git-workflowSkill
- history-hygieneSkill
- init-modeSkill
- model-selectionSkill
- pr-lifecycleSkill
- protected-filesSkill
- release-processSkill
- reskillSkill
- reviewer-protocolSkill
- secret-handlingSkill
- security-reviewSkill
- squad-conventionsSkill
- test-disciplineSkill
- windows-compatibilitySkill
- agentic-workflow-designerSkill
- gh-aw-reliabilitySkill
- iterative-retrievalSkill
- reflectSkill
- {skill-name}Skill
- agent-collaborationSkill
- agent-conductSkill
- architectural-proposalsSkill
- ci-validation-gatesSkill
- client-compatibilitySkill
- cli-wiringSkill
- coordinator-init-modeSkill
- coordinator-response-modeSkill
- coordinator-source-of-truthSkill
- cross-machine-coordinationSkill
- cross-squad-communicationSkill
- cross-squadSkill
- distributed-meshSkill
- docs-standardsSkill
- e2e-template-testingSkill
- economy-modeSkill
- error-recoverySkill
- external-commsSkill
- gh-auth-isolationSkill
- gh-aw-enlistmentSkill
- github-multi-accountSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
3 rules. 0 are common, 3 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 4 edited versions we read keep these.
3
Distinctive
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 24
Ask: "What evidence supports this?
- Distinctive: line 26
Verify URLs, package names, API endpoints, and external references actually exist
- Distinctive: line 31
When reviewing another agent's work, use this template:
“Common” is measured: kept by at least 6 in 10 of the 4 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
Skill: Fact Checking
Context
Codifies the challenger agent review output format and methodology so any agent performing fact-checking or review produces consistent, structured output.
Pattern
Review Methodology
For every claim or deliverable under review:
- Ask: "What evidence supports this? What would disprove it?"
- Generate counter-hypotheses and test them against available data
- Verify URLs, package names, API endpoints, and external references actually exist
- Flag confidence levels: ✅ Verified, ⚠️ Unverified, ❌ Contradicted
Review Output Format
When reviewing another agent's work, use this template:
### Fact Check — {deliverable name}
**Claims verified:** {count}
**Issues found:** {count}
| # | Claim | Status | Evidence/Notes |
|---|-------|--------|---------------|
| 1 | {claim} | ✅/⚠️/❌ | {supporting or contradicting evidence} |
**Counter-hypotheses tested:**
- {alternative explanation + result}
**Verdict:** {PASS / PASS WITH NOTES / NEEDS REVISION}Confidence Levels
- ✅ Verified — evidence confirms the claim
- ⚠️ Unverified — cannot confirm or deny; suggest verification method
- ❌ Contradicted — evidence disproves the claim
Ceremony Integration
Auto-trigger this skill before any architecture decision, or when an agent claim contains superlatives or percentage thresholds (e.g., "saves 75%", "always", "never"). The coordinator spawns the challenger agent with:
Challenger — fact-check {agent}'s claim: "{claim}"
Cite evidence for every verdict. Max 3 investigation cycles.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.

