---
title: "Writing Lean proofs: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/skills/trailofbits-writing-lean-proofs/
description: "Writes Lean 4 proofs in Mathlib style, gates sorry with the kernel rather than grep, and defers to a project's own CONTRIBUTING file when it conflicts."
---

# Writing Lean proofs: review, setup & limitations · Undominated.ai

> Writes Lean 4 proofs in Mathlib style, gates sorry with the kernel rather than grep, and defers to a project's own CONTRIBUTING file when it conflicts.

[← Explore all skills](/skills/)

DEVELOPMENT WORKFLOW / Trail of Bits

# Writing Lean proofs

Writes Lean 4 proofs in Mathlib style, gates sorry with the kernel rather than grep, and defers to a project's own CONTRIBUTING file when it conflicts.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/trailofbits/skills/tree/82fe8226252622fa807643bdca1710901198553a/plugins/writing-lean-proofs/skills/writing-lean-proofs)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 3 linked sources
 Publisher Trail of Bits
 Licence [CC-BY-SA-4.0 ↗](https://github.com/trailofbits/skills/blob/82fe8226252622fa807643bdca1710901198553a/LICENSE)
 Revision 82fe82262526
 [Read what was—and wasn’t—checked ↓](#review)

“Writes and reviews structured Lean 4 proofs and designs Lean libraries following Mathlib conventions. Use when proving theorems in Lean, formalizing mathematics or specifications in Lean 4, defining new types or definitions in a Lean library, reviewing Lean proofs for readability and maintainability, refactoring long tactic proofs into lemmas, filling in sorry placeholders in a Lean development, setting up CI or linters for a Lean project, diagnosing slow proofs or maxHeartbeats timeouts, or writing custom tactics, macros, or linters.”

 [Trail of Bits · upstream description ↗](https://github.com/trailofbits/skills/blob/82fe8226252622fa807643bdca1710901198553a/plugins/writing-lean-proofs/skills/writing-lean-proofs/SKILL.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Unproved obligations are gated with collectAxioms or #print axioms, not grep, because grep matches comments and misses unproved helpers.
- When NOT to Use excludes Lean 3, Coq, Isabelle, Agda, and Lean used only as a programming language.
- A slow proof is not fixed by raising maxHeartbeats until #count_heartbeats has been read.

### A good fit for

 - Filling a Lean 4 sorry skeleton one goal at a time
- Reviewing a tactic proof for missing API lemmas
- Detect unproved dependencies and unexpected trust assumptions in a Lean library before calling it verified.

### Weigh up before choosing

 - A verified-software project with its own house style takes precedence over Mathlib conventions; the skill says to read CONTRIBUTING first.
- Compiling is described as the floor, not as evidence the proof is maintainable.
- This review did not execute the skill or lake.
- A green lake build can contain sorry warnings; a textual search cannot detect all transitive axioms. Axiom checks only cover the imported modules and declaration filter actually selected.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - plugins/writing-lean-proofs/skills/writing-lean-proofs/SKILL.md
- LICENSE
- README.md
- plugins/writing-lean-proofs/skills/writing-lean-proofs/references/proof-style.md
- plugins/writing-lean-proofs/skills/writing-lean-proofs/references/linting.md

### Our findings

 - The workflow is to design the API, build a sorry skeleton, fill one goal at a time, and then run the checkers rather than eyeball style.
- sorry is gated by asking the kernel, and the quick reference says never to grep for it.
- A rejected excuse is raising maxHeartbeats for a slow proof instead of measuring with #count_heartbeats.
- references/proof-style.md says to outline with sorry or underscore first so later errors stay localized.
- The retained linting reference collects declaration axioms, rejects sorryAx and unexpected axioms and fails if its module filter checks zero declarations.

### Not established by this review

 - The skill was not executed inside a host agent.
- lake build and the Lean linters were not run.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Add a skill to your workflow.

[Upstream setup instructions ↗](https://github.com/trailofbits/skills/blob/82fe8226252622fa807643bdca1710901198553a/README.md)

DOCUMENTED COMMAND

 /plugin marketplace add trailofbits/skills Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - Add the marketplace and install the writing-lean-proofs plugin.
- Do not treat an unfinished proof as accepted.
- Download the complete bundle from https://undominated.ai/resources/skills/trailofbits-writing-lean-proofs/bundle.zip and extract it into a new directory. It holds SKILL.md and 8 supporting files unchanged at revision 82fe8226, the upstream licence and an attribution file.
- Place the extracted directory in your host's documented skills directory, named writing-lean-proofs. Keep SKILL.md and the licence together.

### Before you start

 - Lean 4 with lake; Mathlib for the Mathlib-convention parts

### Compatibility

Claude Code plugin marketplace · Lean 4

### Local Markdown instructions

 - The skill edits Lean sources and runs lake plus the project's linters.
- Runs project compilation and metaprogram checks; dependency resolution may download executable build inputs.

### Cost model

CC-BY-SA-4.0. The pinned LICENSE is Creative Commons Attribution-ShareAlike 4.0 International. The skill does not say a paid Trail of Bits account is required.

THE COMPLETE REVIEWED DEFINITION

## Read it before you reuse it.

Original source bytes, with attribution. Review the host-specific setup notes above.

 Copy definition ↗ [Download complete resource + licence ↗](/resources/skills/trailofbits-writing-lean-proofs/bundle.zip)[Raw Markdown ↗](/resources/skills/trailofbits-writing-lean-proofs/definition.md)
 ---
name: writing-lean-proofs
description: "Writes and reviews structured Lean 4 proofs and designs Lean libraries following Mathlib conventions. Use when proving theorems in Lean, formalizing mathematics or specifications in Lean 4, defining new types or definitions in a Lean library, reviewing Lean proofs for readability and maintainability, refactoring long tactic proofs into lemmas, filling in sorry placeholders in a Lean development, setting up CI or linters for a Lean project, diagnosing slow proofs or maxHeartbeats timeouts, or writing custom tactics, macros, or linters."
---

# Writing Lean Proofs

## Contents

- [When to Use](#when-to-use)
- [When NOT to Use](#when-not-to-use)
- [The workflow](#the-workflow)
- [The extraction ladder](#the-extraction-ladder)
- [Quick reference](#quick-reference)
- [Rationalizations to reject](#rationalizations-to-reject)
- [References](#references)

Structured Lean 4 proof writing and library design, distilled from Mathlib's
style and review conventions and from the methodology of large formalization
projects (Liquid Tensor Experiment, PFR, Fermat's Last Theorem).

**Core principle: design top-down, prove bottom-up.** Lean propositions are
proof-irrelevant — only a theorem's *statement* can affect later declarations.
Statements are the stable interface; proofs are disposable and freely
replaceable. Put design effort into definitions and statements, then fill in
proofs against skeletons that already compile (modulo `sorry`).

## When to Use

- Proving theorems in Lean 4, from single lemmas to multi-file developments
- Formalizing mathematics, protocols, or software specifications in Lean
- Defining new types, structures, or functions in a Lean library
- Reviewing Lean code for readability, maintainability, or Mathlib readiness
- Refactoring a long or fragile tactic proof into lemmas
- Setting up a formalization project that several people or agents will
 contribute to in parallel
- Setting up CI, linters, or verification gates for a Lean project — do this
 at project start, before patterns propagate
- Diagnosing slow proofs, `maxHeartbeats` timeouts, or expensive reduction
- Writing custom tactics, macros, or project-specific linters

## When NOT to Use

- Lean 4 as a general-purpose programming language (no proofs involved) —
 most of this skill targets proof and API structure
- Coq, Isabelle, Agda, or Lean 3 — conventions and tactic names differ;
 Lean 3 idioms (`ge_or_gt` linting, `discrete_field`) are obsolete
- Verified-software Lean projects with their own house style (e.g.
 spec-traceability-first codebases): Mathlib conventions are the community
 default, but check the project's CONTRIBUTING first and defer to it

## The workflow

### 1. Design definitions and their API first

Definitions carry the design weight. Before proving anything about a new
concept:

- **Prefer total functions with junk values** over subtypes or `Option` in
 signatures (Mathlib: `(0 : ℝ)⁻¹ = 0`). Side conditions then appear only on
 the lemmas that need them, not at every use site.
- **Bundle**: new morphism kinds are structures with a `FunLike` instance;
 new subobject kinds use `SetLike`; carry property proofs as structure
 fields, not separate `IsHom`-style predicates.
- **Pick the canonical spelling** (simp-normal form) for every concept with
 multiple equivalent forms, and state all API lemmas for that form only.
- **Write the API in the same file, immediately**: `ext`, `@[simp]`,
 coercion, and injectivity lemmas — before the definition is used anywhere.
 Downstream proofs use the API, never `unfold`/`show ... from rfl`.

See [library-design.md](references/library-design.md) for the full set of
design rules with rationale.

### 2. Build a sorry skeleton

State everything before proving anything, at every scale:

- **Project scale**: state the target theorem and the lemmas it needs, all
 with `:= sorry`, and make the file compile. Each `sorry` is now an
 independent work unit — a contributor (human or LLM) can discharge one
 without understanding the rest. This is how LTE, PFR, and FLT scale to
 dozens of parallel contributors.
- **Proof scale**: inside a proof, lay out the `have`/`suffices`/`calc`
 skeleton with `sorry` justifications, get Lean to accept the structure,
 then fill each step. Keeping the structure intact is what produces useful
 error messages while you work.

```lean
example (a b c d : ℝ) (h : c = d * a + b) (h' : b = a * d) : c = 2 * a * d := by
 calc
 c = d * a + b := sorry
 _ = d * a + a * d := sorry
 _ = 2 * a * d := sorry
```

### 3. Fill goals, one focused goal at a time

- Every new subgoal gets a focusing dot `·` with an indented block — never
 leave several goals active in unfocused sequence (Mathlib's `multiGoal`
 linter enforces this). This is what kills fragile goal-ordering dependence.
- Open each block with a redundant `show` stating its goal. The proof works
 without it; reviewers and future editors need it. If `show` would *change*
 the goal, use `change` instead — keep stated goals honest.
- Chained rewrites of (in)equalities become `calc` blocks, relations aligned
 vertically.
- `have` for forward stepping stones ("we first establish X"); `suffices`
 for backward reduction ("it suffices to show X").
- While drafting, annotate the goal state as a comment before non-obvious
 tactics — emitted by Lean, never imagined. In a headless workflow, insert
 `trace_state` at the point of interest or a deliberate `done` where goals
 should be closed, then run `lake env lean Path/To/File.lean`; copy the
 reported hypotheses, case name, and target. Strip routine probes after the
 proof works. This is the single most effective technique for LLM-written
 proofs (see [llm-techniques.md](references/llm-techniques.md)).

See [proof-style.md](references/proof-style.md) for the full tactic-style
rules, and [naming-conventions.md](references/naming-conventions.md) for
naming lemmas so their names are guessable from their statements.

### 4. Verify mechanically

Do not eyeball-check style — run the checkers. `lake build` is the floor,
and it is *only* the floor: `sorry` is a warning, so a green build exits 0
with sorries still present.

- **Gate unproved obligations by asking the kernel, never by grepping.**
 `#print axioms myTheorem` for a spot check; for CI, collect axioms per
 declaration with `Lean.collectAxioms` and assert the *whole* expected
 footprint (`[propext, Classical.choice, Quot.sound]` unless deliberately
 widened), so a stray `sorry` *or* a new trust assumption like
 `native_decide` fails loudly. Grep is wrong in both directions: it matches
 the word in comments, and it misses a theorem whose own text is clean but
 which applies an unproved helper. Working script in
 [linting.md](references/linting.md).
- **Choose lints by project role and put them in CI at project start.** Do not
 enable `linter.mathlibStandardSet` wholesale in a downstream project: it
 combines proof-maintenance checks with public-API checks, house style, and
 Mathlib-specific repository policy. For a self-contained proof, start with
 `linter.auxLemma`, `linter.style.maxHeartbeats`,
 `linter.style.multiGoal`, `linter.style.setOption`, and
 `linter.style.show`. A reusable library should additionally enable
 `linter.flexible`, `linter.style.missingEnd`,
 `linter.style.openClassical`, and the two `unused*InType` checks. Treat
 `nativeDecide` as a trust-policy choice and formatting or deprecated-syntax
 checks as project style. No warning gates anything unless warnings fail
 the build. Run Batteries' declaration-level `#lint` checks, including
 `simpNF`, separately. Verify every option against the pinned Mathlib source
 and with a known-trigger fixture: a misspelled `weak.` option is
 intentionally ignored. The complete 26-member audit and lakefile profiles
 are in [linting.md](references/linting.md).
- **Write a custom linter for every project-specific convention** (simp-set
 discipline, summary-lemma coverage, required attributes) — a
 declaration-level `@[env_linter]` is one structure, and it is the only
 thing that reliably catches "the attribute is missing on 29 of 30
 declarations". See [linting.md](references/linting.md) for the recipe and
 the engineering rules (vacuity anchors, prove-it-can-fail, allowlists).

## The extraction ladder

When does proof structure graduate into separate lemmas?

0. **Before extracting, state the fragment's type and search by shape.** Put
 the proposed statement in a scratch `example`, run `exact?` and `apply?`
 on the bare goal, then try a type-pattern and source search. If an existing
 theorem fits, use it. Do not report an API gap without recording the
 searches that failed.

1. **A sub-argument repeats within one proof** → name it as a local `have`.

 ```lean
 theorem min_comm (a b : ℝ) : min a b = min b a := by
 have h : ∀ x y : ℝ, min x y ≤ min y x := by
 intro x y
 apply le_min
 · show min x y ≤ y
 exact min_le_right x y
 · show min x y ≤ x
 exact min_le_left x y
 apply le_antisymm
 · show min a b ≤ min b a
 exact h a b
 · show min b a ≤ min a b
 exact h b a
 ```

2. **The statement is independently interesting, or extraction sheds
 hypotheses the sub-argument does not need** → standalone lemma. Dropping
 unneeded hypotheses is the stronger trigger: the extracted lemma becomes
 more general than the proof it came from.
3. **The proof reads as "long and unwieldy"** → split it. This is Mathlib's
 review criterion, and it is deliberately qualitative — there is no line
 threshold. Resolve doubt by attempting the extraction: if a fragment has
 a clean statement, it wanted to be a lemma.

## Quick reference

| Rule | Why | Enforced by |
|------|-----|-------------|
| Never unfold definitions downstream; `erw` or trailing `rfl` = missing API | API lemmas are the abstraction boundary | review ("missing API" smell) |
| Terminal `simp` stays unsqueezed; non-terminal `simp` becomes `simp only [...]` | squeezed terminal calls bury the key lemmas and break on renames | style guide |
| One focused goal at a time (`·` blocks) | kills goal-ordering fragility | `linter.style.multiGoal` |
| `show` must not change the goal (use `change`) | stated goals stay honest | `linter.style.show` |
| No `set_option` debug/trace/profiler or unscoped `maxHeartbeats` in final code | debugging scaffolding | `linter.style.setOption` |
| State lemmas in simp-normal form, `<` not `>` | simp matches syntactically | `simpNF` linter |
| Golf only when the result is at least as readable; trivial results exempt | short ≠ better | review |
| `Fact` instances are local, never global | global instances degrade all typeclass search | review |
| Name lemmas from their statements (see naming reference) | names become guessable without search | `linter.style.nameCheck` catches only `__`; `#lint defsWithUnderscore` and review cover more |
| Search a bare goal by shape before writing a helper or claiming an API gap | names are not always guessable from the target | `exact?`, `apply?`, type/source search |
| Generally one tactic invocation per line; a one-line closing proof is the exception | preserves readable proof structure without inventing an absolute rule | style guide |
| Gate `sorry` with `collectAxioms`/`#print axioms`, never grep | grep matches comments, misses unproved helpers | axiom audit in CI |
| Prefer simp-lemma LHSs keyed on structure, not numerals; one spelling per constant | `2 ^ 32` never matches a goal normalized to `4294967296` | `simpNF`, review |
| Re-derive every `simp only` list with `simp?` at its own site | lists do not transfer between look-alike goals | `linter.flexible` |
| Every `maxHeartbeats` override is an unproven claim — measure before believing | copy-pasted budgets carry no information | `#count_heartbeats`, bisection |
| Conditional simp lemma fires shallow but not deep → raise `maxDischargeDepth` (default 2) | chained side conditions truncate silently, no diagnostic | diagnosis (proof-style, simp discipline) |
| Every project-specific convention gets a custom linter, in CI from day one | review misses the 29-of-30 failure mode | `@[env_linter]` + `#lint` |

Full rationale for each row, plus the library-level anti-patterns, in
[anti-patterns.md](references/anti-patterns.md).

## Rationalizations to reject

| Excuse | Reality |
|--------|---------|
| "The proof compiles, ship it" | Compiling is the floor. A monolithic tactic block that only Lean can read will break silently at the next Mathlib bump and no one will be able to repair it. |
| "Unfolding the definition is simpler than writing API lemmas" | Every downstream `unfold` couples a proof to the implementation. The first refactor breaks all of them at once. Write the missing lemma. |
| "Squeezing every simp makes the proof faster and more robust" | Backwards for *terminal* simp calls: the squeezed list breaks on every rename and drowns the signal. Squeeze non-terminal calls only. |
| "It's shorter, therefore better" | Mathlib review policy: golfing is fine *only* when it does not sacrifice readability. Length is not the target; legibility is. |
| "I'll restructure it into lemmas after it works" | After it works, the structure is load-bearing and tangled. State the skeleton first; the lemmas fall out for free. |
| "Adding `show` lines is redundant noise" | They are redundant to the kernel and essential to every human or model that reads the proof next. |
| "This helper is too specific to be a lemma" | If it has a clean statement, extract it — dropping the hypotheses it doesn't need usually reveals it was general all along. |
| "We'll add linters once the library stabilizes" | Backwards: patterns propagate by copy-paste, so a deferred linter meets a 400-warning backlog instead of one bad line. Enable what is already clean and gate it now. |
| "The check passed, so we're clean" | A check that can't fail proves nothing — sweeps reach zero files, misspelled `weak.` options are ignored, pipelines swallow exit codes. Prove every gate can fail before trusting that it passes. |
| "The proof is slow, raise maxHeartbeats" | An unmeasured budget is a claim, not a fix — and it masks the regression the next reader needs to see. Measure with `#count_heartbeats`; restructure the definition or decompose the goal. |

## References

- [library-design.md](references/library-design.md) — definitions, APIs,
 bundling, abstraction boundaries, spec-driven project decomposition
- [proof-style.md](references/proof-style.md) — tactic proof structure:
 calc, have/suffices, focusing, and simp discipline including the
 why-doesn't-this-lemma-fire diagnoses (discharge depth, traversal order,
 numeral spellings)
- [naming-conventions.md](references/naming-conventions.md) — Mathlib naming
 so lemma names are computable from statements
- [anti-patterns.md](references/anti-patterns.md) — recognized anti-patterns,
 why each is harmful, and which linter catches it
- [llm-techniques.md](references/llm-techniques.md) — evidence-based
 techniques specific to LLM-written proofs
- [linting.md](references/linting.md) — axiom-based sorry gates, enabling
 project-specific linter profiles in CI early, the full Mathlib standard-set
 audit, adopting linters with a backlog, writing custom linters for
 project-specific constructs, and proving every gate can fail
- [performance.md](references/performance.md) — measuring per-declaration
 cost, where reduction cost comes from, optimizing definitions without
 losing semantics
- [tactics.md](references/tactics.md) — metaprogramming discipline:
 extension-point selection, metavariable and recovery safeguards, bounded
 search, actionable errors, structured tracing, generated declarations,
 and failure-surface testing

The download contains SKILL.md . Extract the whole bundle; the supporting files are required. Inspect the included MANIFEST.json for file hashes.

By **Trail of Bits**. [Exact upstream source ↗](https://github.com/trailofbits/skills/blob/82fe8226252622fa807643bdca1710901198553a/plugins/writing-lean-proofs/skills/writing-lean-proofs/SKILL.md) · [Licence](/resources/skills/trailofbits-writing-lean-proofs/LICENSE.txt) · [Attribution](/resources/skills/trailofbits-writing-lean-proofs/ATTRIBUTION.txt)

SHA-256 fb2ad9c463ac5185a014892ce33202460b3423d64405024b95b534f0d3b4d3e0

 Read the applicable licence Attribution-ShareAlike 4.0 International

=======================================================================

Creative Commons Corporation ("Creative Commons") is not a law firm and
does not provide legal services or legal advice. Distribution of
Creative Commons public licenses does not create a lawyer-client or
other relationship. Creative Commons makes its licenses and related
information available on an "as-is" basis. Creative Commons gives no
warranties regarding its licenses, any material licensed under their
terms and conditions, or any related information. Creative Commons
disclaims all liability for damages resulting from their use to the
fullest extent possible.

Using Creative Commons Public Licenses

Creative Commons public licenses provide a standard set of terms and
conditions that creators and other rights holders may use to share
original works of authorship and other material subject to copyright
and certain other rights specified in the public license below. The
following considerations are for informational purposes only, are not
exhaustive, and do not form part of our licenses.

 Considerations for licensors: Our public licenses are
 intended for use by those authorized to give the public
 permission to use material in ways otherwise restricted by
 copyright and certain other rights. Our licenses are
 irrevocable. Licensors should read and understand the terms
 and conditions of the license they choose before applying it.
 Licensors should also secure all rights necessary before
 applying our licenses so that the public can reuse the
 material as expected. Licensors should clearly mark any
 material not subject to the license. This includes other CC-
 licensed material, or material used under an exception or
 limitation to copyright. More considerations for licensors:
	wiki.creativecommons.org/Considerations_for_licensors

 Considerations for the public: By using one of our public
 licenses, a licensor grants the public permission to use the
 licensed material under specified terms and conditions. If
 the licensor's permission is not necessary for any reason--for
 example, because of any applicable exception or limitation to
 copyright--then that use is not regulated by the license. Our
 licenses grant only permissions under copyright and certain
 other rights that a licensor has authority to grant. Use of
 the licensed material may still be restricted for other
 reasons, including because others have copyright or other
 rights in the material. A licensor may make special requests,
 such as asking that all changes be marked or described.
 Although not required by our licenses, you are encouraged to
 respect those requests where reasonable. More_considerations
 for the public:
	wiki.creativecommons.org/Considerations_for_licensees

=======================================================================

Creative Commons Attribution-ShareAlike 4.0 International Public
License

By exercising the Licensed Rights (defined below), You accept and agree
to be bound by the terms and conditions of this Creative Commons
Attribution-ShareAlike 4.0 International Public License ("Public
License"). To the extent this Public License may be interpreted as a
contract, You are granted the Licensed Rights in consideration of Your
acceptance of these terms and conditions, and the Licensor grants You
such rights in consideration of benefits the Licensor receives from
making the Licensed Material available under these terms and
conditions.

Section 1 -- Definitions.

 a. Adapted Material means material subject to Copyright and Similar
 Rights that is derived from or based upon the Licensed Material
 and in which the Licensed Material is translated, altered,
 arranged, transformed, or otherwise modified in a manner requiring
 permission under the Copyright and Similar Rights held by the
 Licensor. For purposes of this Public License, where the Licensed
 Material is a musical work, performance, or sound recording,
 Adapted Material is always produced where the Licensed Material is
 synched in timed relation with a moving image.

 b. Adapter's License means the license You apply to Your Copyright
 and Similar Rights in Your contributions to Adapted Material in
 accordance with the terms and conditions of this Public License.

 c. BY-SA Compatible License means a license listed at
 creativecommons.org/compatiblelicenses, approved by Creative
 Commons as essentially the equivalent of this Public License.

 d. Copyright and Similar Rights means copyright and/or similar rights
 closely related to copyright including, without limitation,
 performance, broadcast, sound recording, and Sui Generis Database
 Rights, without regard to how the rights are labeled or
 categorized. For purposes of this Public License, the rights
 specified in Section 2(b)(1)-(2) are not Copyright and Similar
 Rights.

 e. Effective Technological Measures means those measures that, in the
 absence of proper authority, may not be circumvented under laws
 fulfilling obligations under Article 11 of the WIPO Copyright
 Treaty adopted on December 20, 1996, and/or similar international
 agreements.

 f. Exceptions and Limitations means fair use, fair dealing, and/or
 any other exception or limitation to Copyright and Similar Rights
 that applies to Your use of the Licensed Material.

 g. License Elements means the license attributes listed in the name
 of a Creative Commons Public License. The License Elements of this
 Public License are Attribution and ShareAlike.

 h. Licensed Material means the artistic or literary work, database,
 or other material to which the Licensor applied this Public
 License.

 i. Licensed Rights means the rights granted to You subject to the
 terms and conditions of this Public License, which are limited to
 all Copyright and Similar Rights that apply to Your use of the
 Licensed Material and that the Licensor has authority to license.

 j. Licensor means the individual(s) or entity(ies) granting rights
 under this Public License.

 k. Share means to provide material to the public by any means or
 process that requires permission under the Licensed Rights, such
 as reproduction, public display, public performance, distribution,
 dissemination, communication, or importation, and to make material
 available to the public including in ways that members of the
 public may access the material from a place and at a time
 individually chosen by them.

 l. Sui Generis Database Rights means rights other than copyright
 resulting from Directive 96/9/EC of the European Parliament and of
 the Council of 11 March 1996 on the legal protection of databases,
 as amended and/or succeeded, as well as other essentially
 equivalent rights anywhere in the world.

 m. You means the individual or entity exercising the Licensed Rights
 under this Public License. Your has a corresponding meaning.

Section 2 -- Scope.

 a. License grant.

 1. Subject to the terms and conditions of this Public License,
 the Licensor hereby grants You a worldwide, royalty-free,
 non-sublicensable, non-exclusive, irrevocable license to
 exercise the Licensed Rights in the Licensed Material to:

 a. reproduce and Share the Licensed Material, in whole or
 in part; and

 b. produce, reproduce, and Share Adapted Material.

 2. Exceptions and Limitations. For the avoidance of doubt, where
 Exceptions and Limitations apply to Your use, this Public
 License does not apply, and You do not need to comply with
 its terms and conditions.

 3. Term. The term of this Public License is specified in Section
 6(a).

 4. Media and formats; technical modifications allowed. The
 Licensor authorizes You to exercise the Licensed Rights in
 all media and formats whether now known or hereafter created,
 and to make technical modifications necessary to do so. The
 Licensor waives and/or agrees not to assert any right or
 authority to forbid You from making technical modifications
 necessary to exercise the Licensed Rights, including
 technical modifications necessary to circumvent Effective
 Technological Measures. For purposes of this Public License,
 simply making modifications authorized by this Section 2(a)
 (4) never produces Adapted Material.

 5. Downstream recipients.

 a. Offer from the Licensor -- Licensed Material. Every
 recipient of the Licensed Material automatically
 receives an offer from the Licensor to exercise the
 Licensed Rights under the terms and conditions of this
 Public License.

 b. Additional offer from the Licensor -- Adapted Material.
 Every recipient of Adapted Material from You
 automatically receives an offer from the Licensor to
 exercise the Licensed Rights in the Adapted Material
 under the conditions of the Adapter's License You apply.

 c. No downstream restrictions. You may not offer or impose
 any additional or different terms or conditions on, or
 apply any Effective Technological Measures to, the
 Licensed Material if doing so restricts exercise of the
 Licensed Rights by any recipient of the Licensed
 Material.

 6. No endorsement. Nothing in this Public License constitutes or
 may be construed as permission to assert or imply that You
 are, or that Your use of the Licensed Material is, connected
 with, or sponsored, endorsed, or granted official status by,
 the Licensor or others designated to receive attribution as
 provided in Section 3(a)(1)(A)(i).

 b. Other rights.

 1. Moral rights, such as the right of integrity, are not
 licensed under this Public License, nor are publicity,
 privacy, and/or other similar personality rights; however, to
 the extent possible, the Licensor waives and/or agrees not to
 assert any such rights held by the Licensor to the limited
 extent necessary to allow You to exercise the Licensed
 Rights, but not otherwise.

 2. Patent and trademark rights are not licensed under this
 Public License.

 3. To the extent possible, the Licensor waives any right to
 collect royalties from You for the exercise of the Licensed
 Rights, whether directly or through a collecting society
 under any voluntary or waivable statutory or compulsory
 licensing scheme. In all other cases the Licensor expressly
 reserves any right to collect such royalties.

Section 3 -- License Conditions.

Your exercise of the Licensed Rights is expressly made subject to the
following conditions.

 a. Attribution.

 1. If You Share the Licensed Material (including in modified
 form), You must:

 a. retain the following if it is supplied by the Licensor
 with the Licensed Material:

 i. identification of the creator(s) of the Licensed
 Material and any others designated to receive
 attribution, in any reasonable manner requested by
 the Licensor (including by pseudonym if
 designated);

 ii. a copyright notice;

 iii. a notice that refers to this Public License;

 iv. a notice that refers to the disclaimer of
 warranties;

 v. a URI or hyperlink to the Licensed Material to the
 extent reasonably practicable;

 b. indicate if You modified the Licensed Material and
 retain an indication of any previous modifications; and

 c. indicate the Licensed Material is licensed under this
 Public License, and include the text of, or the URI or
 hyperlink to, this Public License.

 2. You may satisfy the conditions in Section 3(a)(1) in any
 reasonable manner based on the medium, means, and context in
 which You Share the Licensed Material. For example, it may be
 reasonable to satisfy the conditions by providing a URI or
 hyperlink to a resource that includes the required
 information.

 3. If requested by the Licensor, You must remove any of the
 information required by Section 3(a)(1)(A) to the extent
 reasonably practicable.

 b. ShareAlike.

 In addition to the conditions in Section 3(a), if You Share
 Adapted Material You produce, the following conditions also apply.

 1. The Adapter's License You apply must be a Creative Commons
 license with the same License Elements, this version or
 later, or a BY-SA Compatible License.

 2. You must include the text of, or the URI or hyperlink to, the
 Adapter's License You apply. You may satisfy this condition
 in any reasonable manner based on the medium, means, and
 context in which You Share Adapted Material.

 3. You may not offer or impose any additional or different terms
 or conditions on, or apply any Effective Technological
 Measures to, Adapted Material that restrict exercise of the
 rights granted under the Adapter's License You apply.

Section 4 -- Sui Generis Database Rights.

Where the Licensed Rights include Sui Generis Database Rights that
apply to Your use of the Licensed Material:

 a. for the avoidance of doubt, Section 2(a)(1) grants You the right
 to extract, reuse, reproduce, and Share all or a substantial
 portion of the contents of the database;

 b. if You include all or a substantial portion of the database
 contents in a database in which You have Sui Generis Database
 Rights, then the database in which You have Sui Generis Database
 Rights (but not its individual contents) is Adapted Material,

 including for purposes of Section 3(b); and
 c. You must comply with the conditions in Section 3(a) if You Share
 all or a substantial portion of the contents of the database.

For the avoidance of doubt, this Section 4 supplements and does not
replace Your obligations under this Public License where the Licensed
Rights include other Copyright and Similar Rights.

Section 5 -- Disclaimer of Warranties and Limitation of Liability.

 a. UNLESS OTHERWISE SEPARATELY UNDERTAKEN BY THE LICENSOR, TO THE
 EXTENT POSSIBLE, THE LICENSOR OFFERS THE LICENSED MATERIAL AS-IS
 AND AS-AVAILABLE, AND MAKES NO REPRESENTATIONS OR WARRANTIES OF
 ANY KIND CONCERNING THE LICENSED MATERIAL, WHETHER EXPRESS,
 IMPLIED, STATUTORY, OR OTHER. THIS INCLUDES, WITHOUT LIMITATION,
 WARRANTIES OF TITLE, MERCHANTABILITY, FITNESS FOR A PARTICULAR
 PURPOSE, NON-INFRINGEMENT, ABSENCE OF LATENT OR OTHER DEFECTS,
 ACCURACY, OR THE PRESENCE OR ABSENCE OF ERRORS, WHETHER OR NOT
 KNOWN OR DISCOVERABLE. WHERE DISCLAIMERS OF WARRANTIES ARE NOT
 ALLOWED IN FULL OR IN PART, THIS DISCLAIMER MAY NOT APPLY TO YOU.

 b. TO THE EXTENT POSSIBLE, IN NO EVENT WILL THE LICENSOR BE LIABLE
 TO YOU ON ANY LEGAL THEORY (INCLUDING, WITHOUT LIMITATION,
 NEGLIGENCE) OR OTHERWISE FOR ANY DIRECT, SPECIAL, INDIRECT,
 INCIDENTAL, CONSEQUENTIAL, PUNITIVE, EXEMPLARY, OR OTHER LOSSES,
 COSTS, EXPENSES, OR DAMAGES ARISING OUT OF THIS PUBLIC LICENSE OR
 USE OF THE LICENSED MATERIAL, EVEN IF THE LICENSOR HAS BEEN
 ADVISED OF THE POSSIBILITY OF SUCH LOSSES, COSTS, EXPENSES, OR
 DAMAGES. WHERE A LIMITATION OF LIABILITY IS NOT ALLOWED IN FULL OR
 IN PART, THIS LIMITATION MAY NOT APPLY TO YOU.

 c. The disclaimer of warranties and limitation of liability provided
 above shall be interpreted in a manner that, to the extent
 possible, most closely approximates an absolute disclaimer and
 waiver of all liability.

Section 6 -- Term and Termination.

 a. This Public License applies for the term of the Copyright and
 Similar Rights licensed here. However, if You fail to comply with
 this Public License, then Your rights under this Public License
 terminate automatically.

 b. Where Your right to use the Licensed Material has terminated under
 Section 6(a), it reinstates:

 1. automatically as of the date the violation is cured, provided
 it is cured within 30 days of Your discovery of the
 violation; or

 2. upon express reinstatement by the Licensor.

 For the avoidance of doubt, this Section 6(b) does not affect any
 right the Licensor may have to seek remedies for Your violations
 of this Public License.

 c. For the avoidance of doubt, the Licensor may also offer the
 Licensed Material under separate terms or conditions or stop
 distributing the Licensed Material at any time; however, doing so
 will not terminate this Public License.

 d. Sections 1, 5, 6, 7, and 8 survive termination of this Public
 License.

Section 7 -- Other Terms and Conditions.

 a. The Licensor shall not be bound by any additional or different
 terms or conditions communicated by You unless expressly agreed.

 b. Any arrangements, understandings, or agreements regarding the
 Licensed Material not stated herein are separate from and
 independent of the terms and conditions of this Public License.

Section 8 -- Interpretation.

 a. For the avoidance of doubt, this Public License does not, and
 shall not be interpreted to, reduce, limit, restrict, or impose
 conditions on any use of the Licensed Material that could lawfully
 be made without permission under this Public License.

 b. To the extent possible, if any provision of this Public License is
 deemed unenforceable, it shall be automatically reformed to the
 minimum extent necessary to make it enforceable. If the provision
 cannot be reformed, it shall be severed from this Public License
 without affecting the enforceability of the remaining terms and
 conditions.

 c. No term or condition of this Public License will be waived and no
 failure to comply consented to unless expressly agreed to by the
 Licensor.

 d. Nothing in this Public License constitutes or may be interpreted
 as a limitation upon, or waiver of, any privileges and immunities
 that apply to the Licensor or You, including from the legal
 processes of any jurisdiction or authority.

=======================================================================

Creative Commons is not a party to its public
licenses. Notwithstanding, Creative Commons may elect to apply one of
its public licenses to material it publishes and in those instances
will be considered the “Licensor.” The text of the Creative Commons
public licenses is dedicated to the public domain under the CC0 Public
Domain Dedication. Except for the limited purpose of indicating that
material is shared under a Creative Commons public license or as
otherwise permitted by the Creative Commons policies published at
creativecommons.org/policies, Creative Commons does not authorize the
use of the trademark "Creative Commons" or any other trademark or logo
of Creative Commons without its prior written consent including,
without limitation, in connection with any unauthorized modifications
to any of its public licenses or any other arrangements,
understandings, or agreements concerning use of licensed material. For
the avoidance of doubt, this paragraph does not form part of the
public licenses.

Creative Commons may be contacted at creativecommons.org.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Skill definition ↗](https://github.com/trailofbits/skills/blob/82fe8226252622fa807643bdca1710901198553a/plugins/writing-lean-proofs/skills/writing-lean-proofs/SKILL.md) Checked 2026-10-14 https://github.com/trailofbits/skills/blob/82fe8226252622fa807643bdca1710901198553a/plugins/writing-lean-proofs/skills/writing-lean-proofs/SKILL.md Supports: Workflow and stated scope
- [Repository licence ↗](https://github.com/trailofbits/skills/blob/82fe8226252622fa807643bdca1710901198553a/LICENSE) Checked 2026-10-14 https://github.com/trailofbits/skills/blob/82fe8226252622fa807643bdca1710901198553a/LICENSE Supports: Redistribution terms
- [Pinned plugins/writing-lean-proofs/skills/writing-lean-proofs/references/linting.md ↗](https://github.com/trailofbits/skills/blob/82fe8226252622fa807643bdca1710901198553a/plugins/writing-lean-proofs/skills/writing-lean-proofs/references/linting.md) Checked 2026-10-14 https://github.com/trailofbits/skills/blob/82fe8226252622fa807643bdca1710901198553a/plugins/writing-lean-proofs/skills/writing-lean-proofs/references/linting.md Supports: review, install, limitations, access

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### Adversarial Decision Review ↗ Submit a bounded artifact and its contract to an independent reviewer before accepting a consequential decision.](/skills/addyosmani-doubt-driven-development/)[### API and Interface Design ↗ Designs public interfaces so the right call is easy and a breaking change is explicit.](/skills/addyosmani-api-and-interface-design/)[### Bug Reproduction Brief ↗ Reduce an uncertain bug report to an evidence-backed failing fixture before repair.](/skills/github-bug-reproduction-brief/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Choose a toolkit](/tools/)
- [Inspect execution hosts](/agents/)
- [Check tool access](/mcp-servers/)
- [Check project dependencies](/check-repo/)
