true-seeing

Verify claims against primary sources and produce a ground-truth assessment.

105|13|Updated Mar 9, 2026
One-click install
npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill true-seeing
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: true-seeing
Source: https://github.com/Hmbown/Wizards-of-the-Ghosts/tree/main/generated/hermes/investigation-and-preparation/true-seeing
Command: npx skills add https://github.com/Hmbown/Wizards-of-the-Ghosts --skill true-seeing

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Surface-level claims, marketing language, and obfuscated descriptions can hide the actual behavior or ground truth. This skill pierces through that surface to reveal what is genuinely true.

Core Features & Use Cases

  • Ground-truth verification of claims by tracing to primary sources and actual behavior.
  • Identification of discrepancies between stated descriptions and real implementation.
  • Deliverables include a clear truth assessment, confirmed facts, identified gaps, and remaining uncertainties.

Quick Start

Provide a target description and I will surface ground truth by exposing what is actually true behind surface claims.

Frequently Asked Questions about true-seeing

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

FAQPage Schema
How do I verify ground truth behind marketing claims and system descriptions?

Verify ground truth by tracing claims to primary sources and actual behavior, piercing surface-level marketing language. This process reveals confirmed facts, identifies discrepancies between stated descriptions and real implementation, and highlights remaining uncertainties.

What is claims verification against primary sources and how does it work?

Claims verification is the process of tracing polished descriptions back to primary sources and actual behavior to expose discrepancies. It works by analyzing target documents or system descriptions to surface a ground-truth assessment including confirmed facts and identified gaps.

How do I identify discrepancies between outdated documentation and actual behavior?

Identify discrepancies by analyzing the target documentation against primary sources and actual system behavior. This surfaces a ground-truth assessment that highlights gaps between stated descriptions and real implementation, clarifying what is genuinely true.

Do I need a specific runtime to trace actual behavior beneath abstractions?

Yes, you need the Hermes Agent as the runtime environment to trace actual behavior beneath abstractions. Running the verification process requires this agent to output a complete ground-truth assessment including confirmed facts and remaining uncertainties.

What's the best way to surface confirmed facts and remaining uncertainties from overly polished claims?

The best way to surface confirmed facts is applying claims verification to trace overly polished descriptions to primary sources. This approach outputs a ground-truth assessment that explicitly distinguishes between confirmed facts, identified discrepancies, and remaining uncertainties.

When should I not use ground-truth assessment for documentation analysis?

Avoid ground-truth assessment when claims do not appear overly polished or require no verification against primary sources. The process is specifically designed for documents or system descriptions that hide actual behavior beneath marketing language and abstractions.