source-of-truth

Structure Markdown documents with calibrated verification statuses and epistemic safeguards.

3|1|Updated Dec 21, 2025
One-click install
npx skills add https://github.com/frmoretto/source-of-truth-creator --skill source-of-truth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: source-of-truth
Source: https://github.com/frmoretto/source-of-truth-creator/tree/main
Command: npx skills add https://github.com/frmoretto/source-of-truth-creator --skill source-of-truth

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Source of Truth documents often overstate certainty, causing readers to trust unverified or improperly qualified claims; this Skill helps you structure epistemically honest documents that are ready for verification.

Core Features & Use Cases

  • Calibrated verification structure: Produces a templated document with a qualified status, verification status matrix, and explicit exceptions so readers understand what is truly verified.
  • Failure-mode prevention: Enforces eight common epistemic mistakes (e.g., verified-header traps, unverified specific numbers, staleness issues, and temporal incoherence).
  • Clear “what’s evidence vs. what’s judgment” separation: Keeps estimates, illustrative examples, and self-assessments distinct from verified data to prevent false authority.

Quick Start

Use this Skill to create a Source of Truth for a topic by asking Claude: "Create a source of truth for [your topic]".

Frequently Asked Questions about source-of-truth

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

FAQPage Schema
How do I prevent overstatement of certainty in documentation?

Preventing overstatement of certainty in documentation requires applying epistemic calibration techniques that separate verified data from estimates and self-assessments. This enforces explicit uncertainty markers, staleness indicators, and temporal coherence checks to ensure claims are properly qualified for verification readiness.

What is a source of truth document and when do I need one?

A source of truth document is an authoritative reference baseline that consolidates research or documents project state. You need one when building structured outputs where each claim must be appropriately qualified with uncertainty markers to prevent readers from trusting unverified or improperly validated information.

How do I structure a markdown document for research synthesis verification?

Structure markdown documents for research synthesis verification by applying operational templates that separate verified data, estimates, self-assessments, and staleness markers. This includes generating a verification status matrix and defining explicit exceptions to prevent false authority in consolidated outputs.

What are common failure modes when building project state documentation?

Common failure modes in project state documentation include verified-header traps, unverified specific numbers, staleness issues, and temporal incoherence. These epistemic mistakes cause readers to trust unverified claims, which you prevent by enforcing a clear separation between evidence and judgment.

Can I use this approach to track temporal coherence in reference baselines?

Yes, you can track temporal coherence in reference baselines using this approach. It enforces operational templates that include temporal coherence checks and staleness markers, ensuring that documented project state remains internally consistent and accurately reflects verification statuses over time.