What problem does it solve? Automating Lean 4 proof generation requires coordinating an external prover, handling authentication failures, feeding kernel errors back for repair, and verifying results — all without hand-authoring proofs or mutating frozen theorem statements. This Skill encodes that orchestration discipline so proof spikes like S2 run headless on Windows without silent pipeline failures. ## Core Features & Use Cases - Headless prover invocation: Drives the Leanstral prover via vibe -p "<prompt>" --agent lean --trust in programmatic mode, avoiding interactive sessions that hang under automation. - Generate-compile-heal loop: Lifts frozen theorem statements verbatim, generates proof terms, kernel-checks with lake env lean or named lake build targets, and re-prompts the prover with exact kernel error messages (capped at ~5 iterations). - Mandatory preflight and guardrails: Smoke-tests authentication before any proof work, enforces frozen signatures, keeps defs out of promoted files, and records prover_identity and prover_data_exposure provenance honestly. - Use Case: Running a Lean proof spike such as S2.MaxAriBound — the orchestrator decomposes a hard lemma into helper lemmas, lets Leanstral fill them, verifies the axiom set with #print axioms, and reports an obstruction with a pre-authored fallback if the prover cannot close the goal. ## Quick Start Ask the agent to drive the Leanstral prover to generate and kernel-check a Lean 4 proof for a frozen theorem statement, starting with the mandatory smoke-test preflight.