proof-assembly

Assemble accepted proof-step artifacts into a paper-ready LaTeX theorem bundle.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? It converts a set of individually reviewed and accepted proof-step artifacts into a single self-contained, journal-style LaTeX paper bundle without introducing unreviewed lemmas or silently dropping derivations. ## Core Features & Use Cases - Coverage and dependency verification: Confirms every required sketch step has an accepted proof and review artifact, and that all step dependencies are closed before assembly. - Structured LaTeX generation: Produces intro, preliminaries, main theorem, proof sketch, and full-detail appendix files plus bibliography and style support files from a shared template. - Honest status reporting: Writes an assembly report marking the result COMPLETE or PARTIAL_BLOCKED with named blockers instead of overstating what is proved. - Use Case: After all proof steps of a machine-learning theorem candidate pass review, run this Skill to generate a compilable arXiv-style LaTeX bundle whose appendix preserves every accepted local derivation in full detail. ## Quick Start Assemble the accepted proof steps for perspective 1 idea 2 into the LaTeX template bundle and report the assembly status.

Frequently Asked Questions about proof-assembly

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

FAQPage Schema
How do I assemble accepted proof steps into a LaTeX paper?

Run the assembly after every required proof step has an accepted proof.md and review.md. The Skill verifies coverage and dependency closure, then writes the five content files, support files, and an assembly report into the latex_template directory.

What inputs are required before proof assembly can run?

It requires the formalized setting.md, an accepted proof_sketch.md with its accepted review, and accepted proof.md and review.md files for every proof step required by the sketch. A final proof_review.md is optional input when repairing assembly flaws.

What happens when a proof step is missing or unreviewed?

Assembly stops honestly instead of inventing content. It keeps valid assembled material, does not present the target as proved, and records the exact blocker in assembly_report.md with status PARTIAL_BLOCKED.

Does the appendix contain full proofs or summaries?

The appendix contains complete journal-style proof detail translated from each accepted step's local derivations, cited-result applications, and target-step assembly. Compression is allowed only for genuine repetition after one complete instance is written.

Can assembly add new lemmas or change step statements?

No. Assembly may only compose accepted step claims and direct assembly-only implications. If an unreviewed lemma, changed assumption, or new proof obligation is needed, it must stop and record the blocker rather than repair it.