consistency-auditor

Inventory and reconcile quantitative parameter values across multiple project documents.

6|Updated Feb 3, 2026

Search Tags:#consistency #parameters #auditing #provenance #discrepancy #cross-document

Ready to run

npx skills add https://github.com/dangeles/claude --skill consistency-auditor

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: consistency-auditor
Source: https://github.com/dangeles/claude/tree/main/claude-config/skills/consistency-auditor
Command: npx skills add https://github.com/dangeles/claude --skill consistency-auditor

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams inventory and reconcile parameter values across multiple project documents to establish a single source of truth and prevent inconsistent decisions.

Core Features & Use Cases

Parameter inventory: Collect all quantitative values used across documents.
Discrepancy detection: Identify and explain mismatches with context.
Provenance tracking: Track where each value originated and how decisions were made.
Use Case: When hepatocyte oxygen consumption is reported differently in two reports, this Skill highlights the discrepancy and suggests which value to adopt based on context.

Quick Start

Run a consistency audit across your project documents to inventory values.

Frequently Asked Questions about consistency-auditor

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

FAQPage Schema

How do I find conflicting parameter values across multiple project documents?▼

Cross-document validation inventories quantitative measurements, detects discrepancies with context, and establishes a single source of truth across project reports, specifications, and logs.

What is parameter provenance tracking and why does it matter for consistency auditing?▼

Parameter provenance tracking records where each quantitative value originated and how decisions were made. It matters for consistency auditing because it justifies chosen values and traces mismatches back to their source documents.

How do I reconcile mismatched quantitative values reported in different specifications?▼

To reconcile mismatched quantitative values, perform context-aware comparison across documents to highlight discrepancies and suggest which value to adopt based on surrounding project context and provenance.

Can I use cross-document validation for technical reports and project logs?▼

Yes, cross-document validation applies to any project with measurements spread across reports, specifications, and logs. It comprehensively inventories values and performs structured reporting to prevent inconsistent decisions.

What is the best way to establish a single source of truth for quantitative measurements?▼

The best way to establish a single source of truth is running a consistency audit that inventories all quantitative values, tracks provenance, detects mismatches, and justifies the final adopted parameters.