← ClaudeAtlas

crypto-experiment-reproducibilitylisted

Use when designing, auditing, reproducing, or packaging cryptography/ZKP/lattice experiments, benchmarks, estimators, proof checkers, datasets, code artifacts, tables, figures, or claim-to-artifact evidence.
RiaoMike/crypto-research-agent-skills · ★ 0 · DevOps & Infrastructure · score 72
Install: claude install-skill RiaoMike/crypto-research-agent-skills
# Crypto Experiment Reproducibility Make empirical and computational claims independently inspectable. Availability, functionality, and reproduced results are separate evidence grades. ## Scope In scope: experiment design, claim-to-artifact mapping, environment/version capture, fair baselines, statistical analysis, replay, raw evidence, portability, artifact packaging, anonymity, ethics/privacy/disclosure, and limitation reporting. Out of scope: fabricating runs/results, calling code availability reproducibility, or releasing sensitive artifacts without authorization and risk review. ## Required Inputs - claims/tables/figures to support; - source/data/configuration and exact versions; - environment, hardware, parameters, seeds, workload, baselines, and expected outputs; - sharing, anonymity, licensing, privacy, ethics, and disclosure constraints. ## Success Criteria - Every empirical/concrete claim maps to exact inputs, command/workflow, raw output, processing, and tolerance. - Environment and dependencies can be recreated or limitations are explicit. - Baselines use compatible security/parameters/hardware/batch/resource rules. - Statistical design, repetitions, seeds, uncertainty, exclusions, and nondeterminism are documented. - Artifact availability, functionality, and result reproduction receive evidence-based statuses. - Sensitive/unshareable components have justified safe alternatives or remain limitations. ## Failure Modes - Missing raw evidence/version/config