fact-check

Verify factual claims in documents using multi-LLM triage and source-grounded verification.

Updated Mar 16, 2026

Search Tags:#documentation #verification #MCP #claims #fact-check #multimodel

Ready to run

npx skills add https://github.com/machug/fact-checker --skill fact-check-machug

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: fact-check
Source: https://github.com/machug/fact-checker/tree/main/skills/fact-check
Command: npx skills add https://github.com/machug/fact-checker --skill fact-check-machug

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires litellm, and includes scripts (resource) components.

What problem does it solve?

Systematically verify factual claims in documents using a hybrid approach: multi-LLM triage and source-grounded verification.

Core Features & Use Cases

Multi-LLM triage: send claims to multiple models for cross-checking and uncertainty flagging.
Source-grounded verification: deep verification against MCP servers and credible external sources, with structured reporting.
Use case: ensure pricing, dates, and capabilities in Microsoft/Azure documentation are accurate before publishing.

Quick Start

Provide a document and run the full pipeline to extract claims, triage with multiple models, verify against authoritative sources, and generate a report.

Frequently Asked Questions about fact-check

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I verify factual claims in technical documentation automatically?▼

You can verify factual claims in technical documentation automatically by using a multi-LLM triage pipeline that extracts statements and cross-checks them against authoritative sources. This systematically flags uncertainties in pricing, dates, and compliance materials.

What is multi-LLM triage for document fact-checking?▼

Multi-LLM triage for document fact-checking is a process where extracted claims are sent to multiple language models for cross-checking and uncertainty flagging. It identifies potentially inaccurate information before deep verification against external sources.

Do I need litellm to verify document facts with multiple models?▼

Yes, you need the litellm library to verify document facts with multiple models, as it manages the model calls required for the triage phase. Optional external providers and an MCP-backed source registry are also used for authoritative verifications.

How do I check pricing and licensing accuracy in Azure documentation before publishing?▼

To check pricing and licensing accuracy in Azure documentation before publishing, run a full fact-checking pipeline that extracts claims, triages them with multiple models, and verifies them against credible external sources to generate a structured accuracy report.

What is the best way to source-ground verification for software documentation claims?▼

The best way to source-ground verification for software documentation claims is to query MCP servers and credible external providers during the verification phase. This ensures claims about capabilities and dates are checked against authoritative registries rather than relying solely on model inference.

Are there limitations to using multi-LLM triage for compliance and governance fact-checking?▼

A limitation of using multi-LLM triage for compliance and governance fact-checking is its reliance on the availability of MCP-backed source registries and optional external providers. Verification accuracy depends on the coverage and credibility of these external authoritative sources.