Total Skills
8
Author Profile: Filivignaga
Skills published by Filivignaga with real stars/downloads and source-aware metadata.
Total Stars
8
Total Downloads
0
Skills Performance
Comparison chart based on real stars and downloads signals from source data.
skeptic
1
Stars
1
Downloads
0
skeptic-analyze
1
Stars
1
Downloads
0
skeptic-clean
1
Stars
1
Downloads
0
skeptic-communicate
1
Stars
1
Downloads
0
skeptic-evaluate
1
Stars
1
Downloads
0
skeptic-examine
1
Stars
1
Downloads
0
skeptic-formulate
1
Stars
1
Downloads
0
skeptic-protocol
1
Stars
1
Downloads
0
Published Skills
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
skeptic-analyze
Skeptic analysis contract lock and execution. Use after formulate, protocol, clean, and examine to lock one executable analysis contract within upstream constraints and execute it, producing auditable outputs for route-appropriate PCS evaluation without widening the claim boundary or self-revising based on result quality. Use when Codex should run the Skeptic analyze stage as a standalone skill, including requests like skeptic analyze --auto to run this stage with autonomous cycle execution.
Repository SourceNeeds Review
skeptic-clean
Skeptic auditable data cleaning. Use after formulate and protocol to build an auditable cleaning pipeline under protocol-defined data visibility, without widening the claim boundary or assuming predictive workflow defaults. Third stage of Skeptic. Use when Codex should run the Skeptic clean stage as a standalone skill, including requests like skeptic clean --auto to run this stage with autonomous cycle execution.
Repository SourceNeeds Review
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-formulate
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.
Repository SourceNeeds Review
skeptic-protocol
Skeptic protocol and project rules. Use after formulate to lock the project rules of the game before clean starts. Defines the data-usage mode, admissible evidence logic, validation requirements, stage prohibitions, and backtracking triggers through iterative question-first cycles. Second stage of Skeptic. Use when Codex should run the Skeptic protocol stage as a standalone skill, including requests like skeptic protocol --auto to run this stage with autonomous cycle execution.
Repository SourceNeeds Review