clarity-gate

Verify documents for epistemic quality before knowledge base ingestion.

32|3|Updated Dec 16, 2025
One-click install
npx skills add https://github.com/frmoretto/clarity-gate --skill clarity-gate
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: clarity-gate
Source: https://github.com/frmoretto/clarity-gate/tree/main/.claude/skills/clarity-gate
Command: npx skills add https://github.com/frmoretto/clarity-gate --skill clarity-gate

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) components.

What problem does it solve?

Clarity Gate provides pre-ingestion verification to ensure documents entering a knowledge base are epistemically qualified, preventing unverified or hedged claims from becoming entrenched in downstream systems.

Core Features & Use Cases

  • Enforces a standardized CGD (Clarity-Gated Document) creation and SOT validation per FORMAT_SPEC v2.1.
  • Supports a mandatory HITL verification flow (Round A: Derived Data Confirmation; Round B: True HITL) to ensure human oversight.
  • Bundles deterministic tooling (scripts/claim_id.py and scripts/document_hash.py) for stable claim IDs and document hashes, enabling traceability during ingestion.
  • Ideal for RAG pipelines, documentation hand-offs, and content with projections or uncertain data to prevent misinterpretation.

Quick Start

Ingest a document through the Clarity Gate workflow to generate a CGD, then review the HITL records and verification statuses before ingestion into your knowledge base.

Frequently Asked Questions about clarity-gate

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

FAQPage Schema
How do I verify document quality before ingestion into a RAG knowledge base?

Pre-ingestion verification enforces epistemic quality before documents enter a RAG knowledge base. It validates source documents and drafts using a standardized Clarity-Gated Document format and human-in-the-loop gating to prevent unverified claims from entrenching downstream.

What is human-in-the-loop gating for pre-ingestion document verification?

Human-in-the-loop gating for pre-ingestion verification ensures human oversight through a mandatory two-round flow: Round A confirms derived data, and Round B performs true human verification. This HITL gating prevents hedged or unverified claims from passing into the knowledge base.

How do I generate deterministic claim IDs and document hashes for RAG ingestion?

Deterministic claim IDs and document hashes are generated via bundled scripts, specifically claim_id.py and document_hash.py. These scripts compute stable identifiers to ensure traceability and verifiable integrity during the document ingestion process.

Does Clarity Gate validate source of truth files for RAG pipelines?

Clarity Gate validates source of truth files per FORMAT_SPEC v2.1. This validation ensures ingested drafts and source documents meet strict epistemic formatting requirements before they are committed to the RAG knowledge base.

When should I use pre-ingestion epistemic verification in a knowledge base pipeline?

Pre-ingestion epistemic verification is needed when processing documentation hand-offs, drafts, or content with projections and uncertain data. It prevents misinterpretation by ensuring unverified or hedged claims are caught before entering the knowledge base.

What is the step-by-step workflow to create a Clarity-Gated Document for knowledge ingestion?

To create a Clarity-Gated Document, ingest a source document through the verification workflow to generate the CGD. Then review the HITL records and verification statuses before final ingestion into the knowledge base.