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.
This listing is imported from SkillsMP metadata and should be treated as untrusted until upstream source review is completed.
Install skill "skeptic-communicate" with this command: npx skills add Filivignaga/skillsmp-filivignaga-filivignaga-skeptic-communicate
This source entry does not include full markdown content beyond metadata.
This detail page is rendered from real SKILL.md content. Trust labels are metadata-based hints, not a safety guarantee.
Related by shared tags or category signals.
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.
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.
Skeptic problem formulation and data context. Use when starting a new data analysis project. Refine a vague domain question into a precise, data-answerable question through iterative question-first cycles with format-aware dataset inspection. First stage of Skeptic. Use when Codex should run the Skeptic formulate stage as a standalone skill, including requests like skeptic formulate --auto to run this stage with autonomous cycle execution.
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.