proof-writer

Writes rigorous mathematical proofs for ML/AI theorems with feasibility triage and dependency mapping.

Updated Apr 1, 2026
One-click install
npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill proof-writer-zniihgnexy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: proof-writer
Source: https://github.com/zniihgnexy/vid_tokenizer/tree/main/.claude/skills/proof-writer
Command: npx skills add https://github.com/zniihgnexy/vid_tokenizer --skill proof-writer-zniihgnexy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Drafting proofs for ML/AI theory often produces polished but flawed arguments with hidden gaps, unstated assumptions, or misapplied theorems. This Skill produces mathematically honest proof packages that either prove the claim, correct it, or report exactly why it cannot be justified. ## Core Features & Use Cases - Feasibility Triage: Classifies every claim as PROVABLE AS STATED, PROVABLE AFTER WEAKENING / EXTRA ASSUMPTION, or NOT CURRENTLY JUSTIFIED before writing anything. - Structured Proof Packages: Writes a standardized PROOF_PACKAGE.md containing the exact claim, assumptions, notation, proof strategy, dependency map, numbered steps, and open risks. - Honest Blockage Reports: When a proof cannot be completed, it documents the exact blocker and the minimal extra assumption or corrected weaker statement instead of fabricating steps. - Use Case: You have a lemma in your paper appendix whose sketch only supports a weaker bound. The Skill identifies the gap, states the corrected claim with the minimal extra assumption, and writes a complete verified proof of the repaired statement. ## Quick Start Ask the AI to prove the stated theorem under the given assumptions and write the result into PROOF_PACKAGE.md.

Frequently Asked Questions about proof-writer

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

FAQPage Schema
How do I write a rigorous proof for an ML theory lemma?▼

State the exact claim, list all assumptions separately from conclusions, and define every symbol before use. Build a dependency map of intermediate lemmas and cited theorems, then write numbered steps where every nontrivial implication is explicitly justified.

How to check whether a theorem is provable under stated assumptions?▼

Classify the claim through feasibility triage: verify the conclusion follows from the listed assumptions, check cited theorems are used within their conditions, and look for counterexamples or quantifier failures. If unjustified, weaken the claim or add a minimal extra assumption.

What should I do when a proof sketch only supports a weaker claim?▼

Do not fabricate the missing step. Document why the original statement is not justified, formulate the corrected weaker claim with the minimal extra assumption if one exists, and write a complete proof of the corrected statement.

Can this Skill write proofs directly into LaTeX paper files?▼

By default it writes to PROOF_PACKAGE.md in the project root and does not modify paper sections or appendix .tex files. It only writes into those targets when the user explicitly requests that destination.

What are common mistakes that invalidate mathematical proofs?▼

Common failures include hidden assumptions, undefined notation, incorrect quantifier order, invoking standard results outside their conditions, and unhandled boundary cases. Vague phrases like 'clearly' or 'by standard arguments' often conceal actual gaps.