result-to-claim

Judge experimental results against intended claims and route pivot, supplement, or confirm actions.

1|Updated Mar 24, 2026
One-click install
npx skills add https://github.com/kitcaf/skills --skill result-to-claim-kitcaf
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: result-to-claim
Source: https://github.com/kitcaf/skills/tree/main/skills/skills-codex/skills/result-to-claim
Command: npx skills add https://github.com/kitcaf/skills --skill result-to-claim-kitcaf

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Experiments produce numbers; this gate judges what those numbers mean by providing an objective assessment of whether the results support the intended claims and routing to the next action (pivot, supplement, or confirm).

Core Features & Use Cases

  • Collect results from available sources (W&B, EXPERIMENT_LOG.md, EXPERIMENT_TRACKER.md, log files, and project notes) and assemble the key information: what experiments were run, the methods, datasets, configurations, main metrics, baselines, and verdicts.
  • Perform a secondary Codex judgment to evaluate whether the results support the intended claim, including fields like claim_supported, what_results_support, what_results_dont_support, missing_evidence, and suggested_next_experiments.
  • Parse and normalize the Codex response and route decisions accordingly, recording the verdict and reasoning in findings.md and project notes.

Quick Start

Provide the collected results and intended claim, then trigger the result-to-claim workflow to obtain a verdict and routing guidance.

Frequently Asked Questions about result-to-claim

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

FAQPage Schema
How do I objectively evaluate if my experimental results support the intended claim?

To evaluate if experimental results support a claim, you provide collected metrics, baselines, and logs for a secondary Codex judgment. This process checks what evidence supports or contradicts the claim and identifies missing data before routing decisions.

What is the best way to decide whether to pivot, supplement, or confirm after an experiment?

The best way to decide whether to pivot, supplement, or confirm is to route experimental outcomes through an objective assessment gate. It analyzes results against intended claims and outputs explicit verdict fields with suggested next experiments to guide your research workflow.

How do I document experiment veracity before writing research papers or conducting ablations?

To document experiment veracity before writing papers or conducting ablations, you parse and normalize the experimental judgment into a findings document. This records the verdict, reasoning, and evidence gaps to ensure claims are objectively validated prior to publication.

Can I use W&B logs and EXPERIMENT_TRACKER.md files to verify research claims?

Yes, you can use W&B logs and EXPERIMENT_TRACKER.md files to verify research claims. The verification process collects results from these available sources, assembles key methods and metrics, and performs a secondary judgment to evaluate claim support.

What specific fields are generated when analyzing missing evidence for research claims?

When analyzing missing evidence for research claims, the generated fields include claim_supported, what_results_support, what_results_dont_support, missing_evidence, and suggested_next_experiments. These fields provide a normalized response to route your next decisions.