result-verification

Verifies analysis results by reconciling totals, reproducing from clean sessions, and tying figures to prose.

2|Updated Jun 8, 2026
One-click install
npx skills add https://github.com/lancegui/causal-powers --skill result-verification-lancegui
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: result-verification
Source: https://github.com/lancegui/causal-powers/tree/main/skills/result-verification
Command: npx skills add https://github.com/lancegui/causal-powers --skill result-verification-lancegui

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Empirical analyses often produce numbers that run cleanly but are silently wrong — stale figures, unreconciled totals, or results that only exist due to cached session state. This Skill enforces evidence-before-assertion checks so a result is verified, not just submitted, before it ships. ## Core Features & Use Cases - Reconciliation and clean-room reproduction: Ties totals to source by an independent path and re-runs the analysis from raw inputs in a fresh kernel with a fixed seed, in R, Julia, Python, or Stata. - Reliability vs. validity checks: Confirms determinism and approved robustness, then anchors the number's level against external benchmarks, known shocks, or alternative construct definitions. - Economic interpretation pass: Converts coefficients into interpretable units, checks economic significance, magnitude plausibility, mechanism consistency, and literature benchmarks. - Use Case: Before reporting a regression estimate, ask the assistant to verify it — it reconciles the headline number to source, reproduces it from a clean session, confirms the approved robustness ran, and ties every table cell to the current run's output. ## Quick Start Ask the assistant to verify this analysis result by reconciling the totals to source and reproducing it from a clean session before reporting. ## Core Features & Use Cases See above for the full checklist-driven verification workflow. ## Quick Start Ask the assistant to verify this result before shipping it.

Frequently Asked Questions about result-verification

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

FAQPage Schema
How do I verify an analysis result before reporting it?▼

Invoke the verification workflow to reconcile totals to source by an independent path, reproduce the result from a clean session with a fixed seed, confirm determinism, and tie every figure and table to the current run's output. Failed checks block the claim rather than being footnoted.

How to reproduce a result from a clean session in R or Python?▼

Restart the kernel or R process so no cached objects remain, set the seed, and run the analysis end to end from raw inputs. In Python use a fresh script run with np.random.seed; in R use Rscript or callr::r() with set.seed.

Does result verification run new robustness checks automatically?▼

No. Verification only confirms that robustness checks already approved by the user or pre-committed in a pre-analysis plan actually ran and moved something. Proposing or running new specifications is treated as an analysis decision that belongs upstream with the user.

What is the difference between reliability and validity checks?▼

Reliability checks confirm the number is computed correctly: reconciliation, reproduction, determinism, and robustness. Validity checks confirm it measures the intended construct, using external anchors like known shocks, independent benchmarks, or expanded construct definitions.

What happens when a verification check fails?▼

The workflow stops and brings the failure to the user as a decision rather than shipping with a caveat. Data bugs route to wrong-number-debugging, while design, sample, or specification changes route to analysis-checkpoints.