validate

Validate Reality Check database schema, referential integrity, and duplicates.

38|Updated Jan 20, 2026
One-click install
npx skills add https://github.com/lhl/realitycheck --skill validate-lhl
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: validate
Source: https://github.com/lhl/realitycheck/tree/main/integrations/claude/skills/validate
Command: npx skills add https://github.com/lhl/realitycheck --skill validate-lhl

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Validate Reality Check database integrity and referential consistency. Run after adding data or before committing.

Core Features & Use Cases

  • Schema validation: verify records conform to the expected schema
  • Referential integrity: ensure all source_ids point to existing sources
  • Data quality checks: detect missing fields and duplicates
  • Use Case: After data updates, run validation to catch issues before committing changes

Quick Start

Run the rc-validate command or uv run python scripts/validate.py to execute the validation.

Frequently Asked Questions about validate

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

FAQPage Schema
How do I validate referential integrity in my database after data updates?

To validate referential integrity after data updates, run validation scripts to ensure all source_ids point to existing sources. This process applies before commits to catch cross-reference integrity issues across claims, sources, and chains.

What is schema validation and how does it check data quality?

Schema validation verifies that database records conform to the expected schema structure. It enforces data quality checks by detecting missing fields, duplicates, and ID format errors to ensure data integrity before committing changes.

How do I check for duplicate records and missing fields before a commit?

You can check for duplicate records and missing fields by running the rc-validate command or uv run python scripts/validate.py. This executes data quality checks automatically to detect schema conformity issues before you commit updates.

When should I run database integrity checks in my data pipeline?

You should run database integrity checks after adding data or before committing changes. Running validation at these points ensures cross-reference integrity, embedding presence, and schema conformance across claims, sources, and chains.

Can I verify embedding presence and ID formats using automated validation scripts?

Yes, automated validation scripts verify embedding presence and enforce ID format checks. They validate cross-reference integrity across claims, sources, and chains to ensure complete data consistency before commits.