proof-sketch

Generates branch-local proof sketches with lemma-sized steps, dependencies, and assumptions for theorem proving.

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

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Developing a formal proof for a machine-learning theory result requires a structured roadmap before any step-level proof writing begins. This Skill converts a formalized setting and goal into an explicit proof sketch with lemma-sized steps, dependency graphs, assumption provenance, and mechanism witnesses, so downstream proof stages have a verifiable plan instead of broad prose. ## Core Features & Use Cases - Proof Roadmap Selection: Selects or repairs a proof roadmap targeting the exact formalized goal, using prior branch failures as negative signals and technical surveys for candidate proof frameworks. - Lemma-Sized Step Decomposition: Splits the roadmap into stable step IDs with exact intended claims, acyclic dependencies, assumption IDs, proof tools, rate objectives, and pending review status. - Contract-Gated Viability Checks: Applies shared gates for assumption provenance, noncircular closure, scope accumulation, generated output flow, and baseline invariance, recording blockers instead of deferring hard obligations. - Use Case: Given a formalized theorem setting and a proof tracker from a research branch, produce a proof_sketch.md that decomposes the argument into reviewable steps with explicit mechanism sources before any detailed proof writing. ## Quick Start Ask the agent to run the proof-sketch stage on the current idea branch to generate or repair proof_sketch.md from the existing setting.md and proof_tracker.md.

Frequently Asked Questions about proof-sketch

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

FAQPage Schema
How do I create a proof sketch before writing a formal proof?

Provide the formalized setting.md and proof_tracker.md for the branch, and the skill selects a proof roadmap, splits it into lemma-sized steps with dependencies and assumptions, and writes proof_sketch.md. Each step records an exact claim, proof tool, and pending review status.

What inputs does the proof-sketch stage require?

It requires perspective_M/idea_N/setting.md and perspective_M/idea_N/proof_tracker.md. Optional inputs include idea.md, LITERATURE_SURVEY.md, technical_survey.md, prior sketches, and triggering review artifacts when repairing after a routed failure.

How does proof-sketch handle a failed previous sketch?

In revise_sketch retry mode it reads the latest sketch and the triggering review, then repairs the roadmap, step decomposition, dependencies, or blockers under the unchanged setting and goal. Target-changing repairs are recorded as blockers for controller routing instead of being made silently.

Can the proof sketch use web search for proof techniques?

Yes, when SEARCH_MODE is OPEN it can build or extend technical_survey.md with idea-local proof frameworks from literature and focused theory-only web search. In CLOSE mode it relies only on branch-local tracker history and prior artifacts.

What are the limitations of the proof-sketch stage?

It does not write step proofs, step reviews, final manuscripts, or accepted results, and it cannot change primitive assumptions, theorem scope, or the formalized goal. When a hard obligation has no viable mechanism source, it records a blocker rather than deferring the problem to later proof steps.