skeptic-analyze

Name: skeptic-analyze
Availability: InStock
Author: filivignaga

Lock and execute Skeptic analyze contracts with auditable YAML and JSON outputs.

Updated Apr 9, 2026

Search Tags:#automation #workflow #contracts #analyze #auditable #skeptic #pcs

Ready to run

npx skills add https://github.com/Filivignaga/skeptic --skill skeptic-analyze

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: skeptic-analyze
Source: https://github.com/Filivignaga/skeptic/tree/main/codex/skeptic-analyze
Command: npx skills add https://github.com/Filivignaga/skeptic --skill skeptic-analyze

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Skeptic analyze locks a single executable analysis contract, executes it against upstream artifacts under a fixed protocol, and produces auditable outputs for PCS handoff without widening the claim boundary.

Core Features & Use Cases

Lock the analyze contract from upstream artifacts (formulation, protocol, cleaning, examination) and execute only that contract.
Generate compact, auditable outputs (yaml artifacts and JSON evidence) for evaluation and reproducibility.
Use --auto to run autonomous cycles from A through F with explicit fallbacks.

Quick Start

Run skeptic analyze to lock and execute the analyze contract.

Frequently Asked Questions about skeptic-analyze

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I lock and execute an analysis contract for auditable workflow automation?▼

To lock and execute an analysis contract, use a tool that derives a fixed protocol from upstream artifacts, executes deterministically under route constraints, and outputs auditable evidence for reproducibility.

What is contract-based analysis and when do I need route-constrained execution?▼

Contract-based analysis locks a single executable boundary before processing upstream artifacts. You need route-constrained execution to prevent claim boundary expansion and guarantee deterministic, auditable analysis outputs.

How do I automate end-to-end analysis cycles with explicit fallbacks?▼

You can automate end-to-end analysis cycles by running execution with an --auto flag, which triggers autonomous stages from A through F while applying explicit fallbacks for robust workflow automation.

Can I generate auditable YAML artifacts and JSON evidence for reproducible analysis?▼

Yes, executing a locked analysis contract against upstream artifacts under a fixed protocol generates compact YAML artifacts and JSON evidence, ensuring full auditability and reproducibility for downstream evaluation.

Does locked contract execution support upstream formulation and cleaning stages?▼

Yes, locked contract execution applies directly to upstream stages including formulation, protocol, cleaning, and examination, deriving a single executable contract to process these artifacts deterministically.