From superscientist
Use before marking any workflow stage as completed — verify outputs exist, are valid, and meet success criteria defined in workflow-state.json
How this skill is triggered — by the user, by Claude, or both
Slash command
/superscientist:result-verificationThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Claiming a stage is complete without verification is dishonesty, not efficiency.
Claiming a stage is complete without verification is dishonesty, not efficiency.
Core principle: Evidence before claims, always.
Violating the letter of this rule is violating the spirit of this rule.
NO STAGE MARKED COMPLETED WITHOUT PASSING VERIFICATION
If verification fails, the stage is marked failed and superscientist:systematic-debugging is invoked.
You MUST complete every check. A single failure = stage is failed.
# For each expected output in workflow-state.json stage.outputs:
test -s "$output_file" || echo "FAIL: $output_file missing or empty"
Read the success_criteria from workflow-state.json for this stage. Check each criterion against actual output:
| Criterion type | How to verify |
|---|---|
| Convergence metric | Parse output, check final value meets threshold from success_criteria |
| Numerical result | Extract value, compare against target or reference |
| Output file produced | Check file exists, non-empty, and in expected format |
| Visualization | Check image file valid, non-zero size, expected content present |
| Script/process completion | Check exit code is 0 and no fatal errors in logs |
Domain-specific reasonableness checks (derive from experiment design):
Check log/output files for:
After verification, report:
If passed:
Verification PASSED for stage-N ([name]):
- All N output files present and non-empty
- Success criteria met: [specific evidence]
- Sanity checks passed: [brief summary]
→ Marking stage as completed.
If failed:
Verification FAILED for stage-N ([name]):
- Failed check: [which check failed]
- Evidence: [what was found]
- Expected: [what was expected]
→ Marking stage as failed. Invoking systematic-debugging.
| Thought | Reality |
|---|---|
| "Output file exists, good enough" | Check it's non-empty and parseable too. |
| "Calculation converged, must be right" | Check the answer is physically reasonable. |
| "No errors in the log" | Check for warnings too. |
| "I'll verify the next stage instead" | Every stage gets verified. No shortcuts. |
| "Results look reasonable" | Compare against success criteria, not intuition. |
npx claudepluginhub chenghao-wu/superscientist --plugin superscientistGuides creation, editing, and verification of skills for AI coding agents using test-driven development with subagent scenarios. Use when authoring or debugging skills.