AF lean4-theorem-proving
Use when working with Lean 4 (.lean files), writing mathematical proofs, seeing "failed to synthesize instance" errors, managing sorry/axiom elimination, or searching mathlib for lemmas - provides build-first workflow, haveI/letI patterns, compiler-guided repair, and LSP integration
As a process F 28/100 · Will not run — References files that are not bundled: ../../COMMANDS.md, ../../scripts/README.md
How to improve
- The text references files that are not there: add them or drop the references.
- Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
- A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.
Guard findings · 0
✓ No critical or high findings
Files scanned: 22. Evidence is masked. Grey chips explain why severity was lowered.
Against the Agent Skills spec
- warning
missing-refreference to a missing file: ../../COMMANDS.md - warning
missing-refreference to a missing file: ../../scripts/README.md
Process rating: all ten parameters 28/100
- 0Tools and files. 2 referenced file(s) missing: ../../COMMANDS.md, ../../scripts/README.md
- 0Result and completion. Does not say what the result is
- 0Inputs and preconditions. Does not say what the process needs to start
- 0Failures and branches. Linear process with no failure handling
- 0Progress reporting. Says nothing while it works
- 20When it triggers. No condition that starts the skill
- 30Running it twice. 4 mutating operations with no state check
- 40Consistency. Frontmatter name (lean4-theorem-proving) differs from the folder (lean4-proof-lean4-theorem-proving)
- 100Steps. 27 steps
- 100Execution cost. Instruction body is 2162 tokens
- low 15 top-level sections: this looks like several domains in one skill
Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.
Quality signals
- +5Description has no quoted example phrases that should trigger the skill
- +4Description does not say when NOT to use the skill (false activations)
- +3Output format is not stated: the model decides each time
- +4No input/output examples
- +1No license
- +2Single-language instructions
- +3Description length 283: enough signal without eating the budget
- +4Structure: 16 headings
- +3Step-by-step instructions: 27 items
- +4Reference files are cited in the instructions (18 of 20)
Quality base 70; lint remarks subtract, signals add up to 100. Result: 75.