skeptic-communicate
Skeptic communication of evaluated results. Use after formulate, protocol, clean, examine, analyze, and evaluate to package only claims that survived evaluation for the intended audience, without upgrading claims, widening the claim boundary, or introducing new analysis. Terminal stage of Skeptic. Use when Codex should run the Skeptic communicate stage as a standalone skill, including requests like skeptic communicate --auto to run this stage with autonomous cycle execution.
Repository SourceNeeds Review
skeptic-evaluate
Skeptic route-appropriate PCS evaluation. Use after formulate, protocol, clean, examine, and analyze to adjudicate whether outputs and claims survive route-appropriate PCS checks, rendering per-claim survival verdicts that determine what communicate may package. Use when Codex should run the Skeptic evaluate stage as a standalone skill, including requests like skeptic evaluate --auto to run this stage with autonomous cycle execution.
Repository SourceNeeds Review
skeptic-examine
Skeptic cleaned-data examination. Use after formulate, protocol, and clean. Characterize what the cleaned, protocol-visible data can actually support through iterative cycles that stay inside the approved question and the protocol contract. Fourth stage of Skeptic. Use when Codex should run the Skeptic examine stage as a standalone skill, including requests like skeptic examine --auto to run this stage with autonomous cycle execution.
Repository SourceNeeds Review
skeptic
Use when running a question-first Veridical Data Science lifecycle: formulate the question, define protocol rules, clean under those rules, examine what the data can support, execute route-specific analysis under an explicit contract lock, evaluate claims, and communicate only claims that survived evaluation. Use when the user says "data analysis", "analyze this dataset", "analyze this CSV", "analyze this parquet", "data science", "Skeptic", or invokes any /skeptic subcommand.
Repository SourceNeeds Review