truth

Verifies claims by inspecting referenced files and producing evidence outputs.

Updated Apr 26, 2026
One-click install
npx skills add https://github.com/EndUser123/cc-marketplace --skill truth
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: truth
Source: https://github.com/EndUser123/cc-marketplace/tree/main/plugins/cc-skills-meta/skills/truth
Command: npx skills add https://github.com/EndUser123/cc-marketplace --skill truth

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Verifies claims by reading files, running lightweight checks, and presenting actual outputs as evidence to reduce reliance on assertions.

Core Features & Use Cases

  • Evidence-driven verification of claims against project artifacts (plans, docs, and code).
  • Plan-aware validation: cross-checks plan metadata, documentation updates, and success criteria.
  • Auditing and compliance demonstrations by generating a structured verification report.

Quick Start

Ask it to verify a claim by inspecting the referenced files and showing the actual outputs as evidence.

Frequently Asked Questions about truth

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

FAQPage Schema
How do I verify project claims against actual documentation and code artifacts?

To verify project claims, read referenced files and run lightweight checks to produce deterministic command outputs as verifiable evidence. This evidence-first approach reduces reliance on unverified assertions during documentation audits.

What is evidence-driven verification for software documentation audits?

Evidence-driven verification validates project claims by inspecting plans, docs, and code to generate a structured verification report. It ensures claims are backed by actual file contents and command outputs without speculation.

Can I use plan-aware validation to check plan metadata and success criteria?

Yes, plan-aware validation cross-checks plan metadata, documentation updates, and success criteria against project artifacts. It confirms that plan-driven claims hold true by examining the actual referenced files.

Does claim verification require deterministic steps and explicit outputs?

Yes, claim verification requires deterministic verification steps and explicit outputs to avoid speculation. It reads referenced files and shows actual command outputs as evidence to demonstrate auditing compliance.

What are the limitations of using automated verification for plan-driven claims?

Automated verification is limited to reading referenced files and producing deterministic command outputs without speculation. It cannot infer or validate claims if the referenced project artifacts are missing or inaccessible.