ds-receiving-analysis-review

What problem does it solve?

This Skill prevents analysts from blindly applying review comments that may contain misunderstandings or non-methodological preferences, protecting statistical correctness and causal validity.

Core Features & Use Cases

• Methodology-vs-Style Separation: Distinguishes claims that affect design, implementation, denominators, units, and inference from comments that only affect presentation or readability.
• Claim Restatement + Artifact Verification: Rephrases each comment in precise analytical terms, then checks it against the notebook, SQL, and experiment design before acting.
• Fail-Closed for Ambiguity: Stops and asks for clarification when feedback is unclear or blocking, avoiding partial updates that could change interpretation.
• Causal Clarity Guardrails: Pushes back when suggestions weaken causal validity, blur exploratory vs primary results, introduce leakage/post-treatment metrics, or ignore randomization units and cluster dependence.
• Controlled Implementation Order: Clarifies items first, fixes blocking methodological issues next, and only then addresses reproducibility/presentation, rerunning affected sections after each important fix.

Quick Start

Use ds-receiving-analysis-review when a reviewer challenges your experiment design, SQL logic, notebook results, or statistical conclusion and you need to verify each comment against the actual analytical artifacts before updating anything.