lean-formalization
Skill9 starsChanged 4 months agoMITView on GitHub
Use when a coding agent needs Lean 4 formalization, proof repair, theorem transcription, sorry completion, Lean patch review, optional adapter-first Lean-specialist backend work, or local Lean validation.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- LeonardSEO/ambitious-math-researchtheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- LeonardSEO/ambitious-math-research★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository5 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .cursor/rules/lean-formalization.mdcCursor rule
- lean-formalizationSkill
- lean-setupSkill
The file
We split this skill into the rules it gives an agent
1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈1
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 15
Read that concrete Skill before formalization or proof work.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Lean Formalization
This root SKILL.md is a compatibility entrypoint for platforms that expect one
top-level Skill file. The shared Skill layer lives at:
skills/lean-formalization/SKILL.mdRead that concrete Skill before formalization or proof work. Keep platform adapters thin and improve the shared Skill layer first.
Reusable scripts, prompts, examples, references, schemas, and tests live in:
skills/lean-runtime/For setup-only tasks such as installing Lean, checking elan/lake, or creating
a reusable mathlib workspace, use:
skills/lean-setup/SKILL.mdOperating Boundary
- Preserve theorem statements unless the user approves a change.
- Reject final patches containing
sorry,admit, or newly introducedaxiom. - Explain and approve optional backend runtime setup before executing it; use an adapter-first contract, with official Numina and Archon treated as recommended adapter candidates rather than hard requirements.
- Validate final Lean patches locally when possible.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

