clarity-gate
Pre-ingestion verification for epistemic quality in RAG systems. Ensures documents are properly qualified before entering knowledge bases. Produces CGD (Clarity-Gated Documents) and validates SOT (Source of Truth) files.
Why use this skill?
Enhance RAG system accuracy with Clarity Gate. Automate pre-ingestion verification, validate SOT files, and prevent LLM hallucinations with v2.1 format standards.
Install via CLI (Recommended)
clawhub install openclaw/skills/skills/frmoretto/clarity-gateWhat This Skill Does
Clarity Gate is a sophisticated pre-ingestion verification engine designed to safeguard RAG (Retrieval-Augmented Generation) knowledge bases. By enforcing the Clarity Gate Format Specification (v2.1), the skill acts as a gatekeeper that ensures AI agents do not treat ambiguous assumptions as objective facts. It parses, validates, and transforms raw documentation into Clarity-Gated Documents (CGD), which are structurally sound and epistemically transparent. The system evaluates documents against strict schema requirements, validates HITL (Human-in-the-Loop) claim records, and ensures Source of Truth (SOT) files adhere to the integrity standards required for high-stakes information retrieval.
Installation
To integrate this skill into your environment, use the OpenClaw command-line interface. Run the following command in your terminal:
clawhub install openclaw/skills/skills/frmoretto/clarity-gate
Once installed, ensure your project directory has access to the bundled scripts/claim_id.py for deterministic hash generation, as this is required for managing claim collisions at scale.
Use Cases
- Corporate Knowledge Bases: Automatically vetting internal policy documents to ensure that citations are verified by humans before being indexed by LLMs.
- Technical Documentation Audits: Ensuring that architectural specs contain validated claims and documented sources, preventing hallucination cascades during troubleshooting.
- Compliance Reporting: Enforcing strict SOT structures for regulatory reports where every claim requires a timestamped verification record.
Example Prompts
- "Analyze this policy document and return a validation report using the clarity-gate E-codes to highlight missing HITL records."
- "Transform this raw technical research note into a valid Clarity-Gated Document (CGD) using version 2.1 specs."
- "Run a sanity check on the SOT table in my documentation; ensure all claims are verified and the date formats comply with E-TB06."
Tips & Limitations
- Structure Matters: Always ensure the
## HITL Verification Recordis present if your document contains claims. Missing this will trigger an E-ST10 error immediately. - Deterministic IDs: Use the bundled
claim_id.pyscript to generate IDs; manual IDs often lead to collisions in large datasets. - Validation Codes: Familiarize yourself with the warning (W) versus error (E) codes. Warnings allow the file to persist but indicate a need for human review, whereas errors denote non-compliant files that will be rejected from the ingest pipeline.
- Scope: This tool focuses on structural and epistemic quality; it does not replace the requirement for human experts to verify the actual truth-value of the claims themselves, only the presence of the required metadata.
Metadata
Not sure this is the right skill?
Describe what you want to build — we'll match you to the best skill from 16,000+ options.
Find the right skillPaste this into your clawhub.json to enable this plugin.
{
"plugins": {
"official-frmoretto-clarity-gate": {
"enabled": true,
"auto_update": true
}
}
}Tags(AI)
Flags: file-read, file-write, code-execution