triangulate

Cross-check claims against multiple primary sources and generate audit files.

5|Updated Apr 9, 2026
One-click install
npx skills add https://github.com/KodingDev/meridian --skill triangulate-kodingdev
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: triangulate
Source: https://github.com/KodingDev/meridian/tree/main/skills/triangulate
Command: npx skills add https://github.com/KodingDev/meridian --skill triangulate-kodingdev

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Triangulate enforces rigorous truth-telling by cross-checking specific-value or behavior claims against multiple primary sources before any assertion or action.

Core Features & Use Cases

  • Tiered grounding: performs quick Tier-1 checks or escalates to heavier Tier-2 audits to surface doubt and ensure evidence-backed outputs.
  • Ground Truth Audit generation: produces inline audit rows and full audit files to document sources, confidence, and potential disagreements.
  • Guarded actions: prevents risky decisions by requiring diverse evidence when high confidence is claimed.

Quick Start

Audit a claim against multiple primary sources before asserting or acting on it.

Frequently Asked Questions about triangulate

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

FAQPage Schema
How do I verify API behavior claims against multiple sources before acting?

To verify API behavior claims, you cross-check specific values against multiple primary sources before asserting them. This requires two sources of different kinds for high confidence, outputting inline audit rows and a full audit file to document all evidence and disagreements.

Why does single-source verification fail for critical runtime states?

Single-source verification fails because it lacks the confidence-gating needed to prevent risky decisions. Triangulation requires two sources of different kinds to surface doubt and ensure evidence-backed outputs, whereas a single source is insufficient for high confidence.

What is the best way to audit design tokens across primary sources?

The best way to audit design tokens is performing tiered grounding: executing quick Tier-1 checks or escalating to heavier Tier-2 audits. This generates inline audit rows and a full audit file that documents sources, confidence levels, and potential disagreements.

Do I need multiple dependencies to cross-check config fields?

No dependencies are required to cross-check config fields. The process requires two sources of different kinds for high confidence, but these are primary reference sources rather than external software dependencies or library integrations.

When should I not use claim verification for software engineering tasks?

You should not use claim verification when a single source is sufficient or when quick action is needed without evidence documentation. Use it only for specific-value or behavior claims where high confidence, source documentation, and disagreement tracking are required.

Can I generate a ground truth audit file for config fields?

Yes, you can generate a ground truth audit file for config fields. The process produces inline audit rows and writes a full audit file to document the evidence, source confidence levels, and any potential disagreements found during the cross-check.