proof-step

Proves one accepted proof-sketch step with local lemmas, checked citations, and target-step assembly.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developing a rigorous mathematical proof requires decomposing a high-level proof sketch into individually verified steps, each with self-contained local lemmas, discharged citation assumptions, and explicit notation provenance. This Skill automates the disciplined construction of a single proof step so reviewers can audit every local unit without hidden gaps. ## Core Features & Use Cases - Local Proof Unit Decomposition: Splits each nontrivial subclaim into named lemmas, propositions, claims, hypotheses, or invariants with stable IDs and paper-ready LaTeX labels. - Citation Assumption Checking: Restates every cited theorem in current notation and verifies where each required assumption is discharged before use. - Assumption and Constant Provenance Tracking: Classifies every new symbol, constant, rate, and invariant condition as setting-derived, dependency-supplied, or locally proved. - Use Case: Given an accepted proof sketch for a learning-theory theorem, invoke this Skill on Step 3 to produce a self-contained proof artifact with local derivations, checked cited results, and an explicit target-step assembly ready for independent review. ## Quick Start Ask the agent to prove Step 3 from the accepted proof sketch in perspective_1/idea_2 using the proof-step workflow and write the result to proof_steps/step_003/proof.md.

Frequently Asked Questions about proof-step

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

FAQPage Schema
How do I prove a single step from a proof sketch?

Provide the setting.md file, the accepted proof_sketch.md, its accepted review, and the target Step ID. The Skill loads the sketch row, plans local proof units, checks cited results, and writes a self-contained proof artifact to proof_steps/<Step ID>/proof.md.

What inputs does the proof-step workflow require?

It requires setting.md, an accepted proof_sketch.md, the accepted proof_sketch_review.md, the target Step ID, and accepted dependency step proofs when dependencies exist. An accepted global_proof.md with its accepted review may optionally supply planning guidance only.

Can proof-step use results from a global proof draft?

Only as planning guidance, and only when global_proof.md is paired with an accepted global_proof_review.md. It cannot serve as proof evidence, a cited result, or an assumption source, and any claim change it suggests must be routed back to the proof-sketch stage.

What happens when a proof step cannot be completed?

The Skill preserves the valid partial derivation, sets Step Proof Status to PARTIAL_BLOCKED, and names the exact obstruction in the Blockers section, such as a failed local unit, missing cited result, invalid assumption, or dependency gap.

How does proof-step handle cited theorems and external results?

Every cited result must be restated in current notation with its source, instantiated objects, required assumptions, and conclusion. Each assumption must be explicitly discharged in the setting, accepted dependencies, or the local proof before the result can be used.