verifying-results-before-claiming
Use when about to claim a result, effect, significance, or that an analysis reproduces, before reporting or writing it up - requires running the analysis fresh and reading the actual output first; evidence before claims always
npx skills add K-Dense-AI/science-superpowers --skill verifying-results-before-claiming --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.
# Verifying Results Before Claiming ## Overview Claiming a finding without fresh verification is dishonesty, not efficiency. **Core principle:** Evidence before claims, always. **Violating the letter of this rule is violating the spirit of this rule.** ## The Iron Law ``` NO CLAIMS WITHOUT FRESH REPRODUCED EVIDENCE ``` If you haven't run the analysis in this state and read its actual output, you cannot claim its result. "It was significant earlier" is not evidence now. ## The Gate Function ``` BEFORE claiming any result or expressing satisfaction: 1. IDENTIFY: What command/analysis proves this claim? 2. RUN: Execute it fresh and complete (from the immutable raw data, fixed seed) 3. READ: The actual output — the estimate, the interval, the p-value, the diagnostics 4. CHECK: Do the method's assumptions hold? Does it reproduce? For a CONFIRMATORY claim: does the pre-registration audit pass? (prereg.sh, ships with science-superpowers:preregistering-analysis: <skills root>/preregistering-analysis/prereg.sh audit) 5. VERIFY: Does the output actually support the claim? - If NO: state the real result with evidence - If YES: state the claim WITH the evidence (number + interval) 6. ONLY THEN
- Overview
- The Iron Law
- The Gate Function
- Common Failures
- Red Flags - STOP
- Rationalization Prevention
- Key Patterns
- When To Apply
- The Bottom Line
- Related Skills
What does the verifying-results-before-claiming skill do?
Use when about to claim a result, effect, significance, or that an analysis reproduces, before reporting or writing it up - requires running the analysis fresh and reading the actual output first; evidence before claims always
How do I install it?
Run `npx skills add K-Dense-AI/science-superpowers --skill verifying-results-before-claiming --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 K-Dense-AI/science-superpowers, a repository with 280 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.
