Skip to content
back to the quest log
Lean 4 skill installation and documentation page on skills.sh
rare⌘ developer toolinglive

Lean 4 Agent Skill

Source-mapped help for proving and tooling

An installable agent skill for Lean programming, theorem proving, Mathlib, Lake, Elan, and editor workflows, mapped back to official sources.

role
Skill author and curator
org
Independent open source
when
2026

What it is

The Lean 4 skill packages practical guidance for agents working across programs, proofs, formalization, package management, and editor tooling.

Its source snapshot is mapped to official Lean and Mathlib material so instructions can be audited and refreshed instead of becoming unattributed folklore.

It installs directly from the public repository through skills.sh and keeps the main skill concise by routing deeper questions to focused references.

where the effort went

  • Accuracy96
  • Tooling92
  • Teaching90
  • Maintenance86

the numbers

Guides
20
Source map
Included
Install
1 command
Snapshot
2026-08-21

built with

  • Lean 4
  • Mathlib
  • Lake
  • Elan
  • Markdown
  • skills.sh

delivery record

What I made

I kept repeating the same setup, proof-debugging, and source-verification steps across formalization projects, so I turned that working method into a reusable skill.

  • 01

    Installable Lean 4 skill with scoped activation rules

  • 02

    Twenty focused Markdown guides and references

  • 03

    Coverage for proving, programming, Mathlib, Lake, Elan, and VS Code

  • 04

    Source map to the official documentation snapshot

  • 05

    Progressive routing that keeps routine tasks compact

Hard problems

The constraints mattered as much as the finished interface.

01field note

Useful guidance without stale folklore

problem
Lean and Mathlib evolve quickly, while copied snippets lose the version and source that made them correct.
response
I pinned the source snapshot date and mapped guidance back to official material so updates can be audited.
02field note

Breadth without context overload

problem
Loading every proof and tooling guide for every task would bury the actual problem.
response
The main skill routes only the relevant reference for the requested workflow.

Screens

after shipping

What stayed with me

  • Reusable agent instructions need provenance and update boundaries just as much as code dependencies do.

  • The best context is the smallest source-backed slice that can answer the current proof state.