result-to-claim
Use when experiments complete to judge what claims the results support, what they don't, and what evidence is still missing. A secondary Codex agent evaluates results against intended claims and routes to next action (pivot, supplement, or confirm). Use after experiments finish — before writing the paper or running ablations.
npx skills add majiayu000/claude-skill-registry --skill result-to-claim-wanshuiyin-auto-claude-code-res --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
# Result-to-Claim Gate Experiments produce numbers; this gate decides what those numbers *mean*. Collect results from available sources, get a secondary Codex judgment, then auto-route based on the verdict. ## Context: $ARGUMENTS ## When to Use - After a set of experiments completes (main results, not just sanity checks) - Before committing to claims in a paper or review response - When results are ambiguous and you need an objective second opinion ## Workflow ### Step 1: Collect Results Gather experiment data from whatever sources are available in the project: 1. **W&B** (preferred): `wandb.Api().run("<entity>/<project>/<run_id>").history()` — metrics, training curves, comparisons 2. **EXPERIMENT_LOG.md**: full results table with baselines and verdicts 3. **EXPERIMENT_TRACKER.md**: check which experiments are DONE vs still running 4. **Log files**: `ssh server "tail -100 /path/to/training.log"` if no other source 5. **docs/research_contract.md**: intended claims and experiment design Assemble the key information: - What experiments were run (method, dataset, config) - Main metrics and baseline comparisons (deltas) - The intended claim these experiments were designed to test - Any
- Context: $ARGUMENTS
- When to Use
- Workflow
- Step 1: Collect Results
- Step 2: Codex Judgment
- Step 3: Parse and Normalize
- Step 3.5: Check Experiment Integrity (if audit exists)
- Step 4: Route Based on Verdict
- Step 5: Update Research Wiki (if active)
- Rules
- Review Tracing
What does the result-to-claim skill do?
Use when experiments complete to judge what claims the results support, what they don't, and what evidence is still missing. A secondary Codex agent evaluates results against intended claims and routes to next action (pivot, supplement, or confirm). Use after experiments finish — before writing the paper or running ablations.
How do I install it?
Run `npx skills add majiayu000/claude-skill-registry --skill result-to-claim-wanshuiyin-auto-claude-code-res --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From majiayu000/claude-skill-registry, a repository with 534 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.