global-proof

Drafts a theorem-level diagnostic proof from an accepted proof sketch before step-level proof work.

65|2|Updated Aug 10, 2026
One-click install
npx skills add https://github.com/DechenZhang/VALG-ML-Theory-Agent --skill global-proof-dechenzhang
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: global-proof
Source: https://github.com/DechenZhang/VALG-ML-Theory-Agent/tree/main/skills/global-proof
Command: npx skills add https://github.com/DechenZhang/VALG-ML-Theory-Agent --skill global-proof-dechenzhang

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? When developing machine-learning theory proofs, jumping straight from a high-level proof sketch to detailed step-level proofs often hides missing mechanisms, broken dependency flows, and theorem-contract defects until late in the process. This Skill produces a review-ready, theorem-level diagnostic draft that exposes hard steps, closure mechanisms, and obstructions before any step-level proof work begins. ## Core Features & Use Cases - Theorem-Level Diagnostic Drafting: Expands an accepted proof sketch into a detailed whole-proof draft with named theorem-level blocks, dependency flow, and assembly logic. - Mechanism and Closure Audits: Applies shared gates (Assumption Provenance, Generated Output Flow, Theorem-Critical Mechanism Witness, Residual-To-Target Adequacy) to certify that every theorem-critical condition has a concrete closure mechanism and source. - Failure Classification and Routing: Classifies hard obligations as step-local, sketch/interface defects, or idea/theorem-contract defects, and routes blockers back to the proof-sketch stage with COMPLETE, PARTIAL_BLOCKED, or SKETCH_BLOCKED status. - Use Case: After a proof sketch for a convergence theorem is accepted, run this Skill to generate global_proof.md, which maps every sketch step to theorem-level blocks, certifies recurrence and invariant closures, and flags any missing mechanism before step workers start. ## Quick Start Ask the agent to run the global-proof stage on the accepted proof sketch in the current idea branch to produce the theorem-level diagnostic draft global_proof.md.

Frequently Asked Questions about global-proof

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

FAQPage Schema
How do I validate a proof sketch before writing detailed proof steps?

Run the global-proof stage after the sketch is accepted. It expands the sketch into a theorem-level diagnostic draft, maps every step to proof blocks, and certifies that each theorem-critical condition has a concrete closure mechanism before step workers run.

What inputs does the global-proof stage require?

It requires the branch setting.md, an accepted proof_sketch.md, and an accepting proof_sketch_review.md. Optional inputs include a proof tracker, a prior global proof review when rerunning after REVISE_GLOBAL, and diagnostic history from earlier failures.

When should global-proof run in a theorem development workflow?

It runs after proof-sketch review accepts a sketch and before any proof-step work starts. It acts as a theorem-level diagnostic gate that exposes hard steps, missing mechanisms, and contract defects early.

Can global-proof modify the accepted proof sketch or setting?

No. The accepted sketch is binding; global-proof cannot change steps, dependencies, assumptions, output targets, or the theorem contract. If repair requires such changes, it marks the draft SKETCH_BLOCKED and routes back to the proof-sketch stage.

What happens when global-proof finds a missing closure mechanism?

The missing mechanism is recorded as a blocker in the Scope And Closure Certificate, the status becomes SKETCH_BLOCKED, and routing returns to proof-sketch. Candidate idea-level obstructions are labeled as evidence for the global-proof reviewer to classify.