lean-applied-reasoning
Skill3 starsChanged 24 days agoApache-2.0View on GitHub
USE FOR: Applied reasoning for intelligence analysis, strategy creation and analysis, brainstorming methodologies. DO NOT USE FOR: pure intelligence-analysis methodology (@lean-applied-reasoning). TRIGGERS: applied reasoning, intelligence formalisation.
In this repository65 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-guard-judge-evalSkill
- applied-data-information-securitySkill
- applied-engineering-disciplinesSkill
- applied-legal-reasoningSkill
- epistemic-discovery-engineSkill
- epistemic-mappingSkill
- hol-metamath-adapterSkill
- isabelle-isar-adapterSkill
- itp-cross-portingSkill
- lean-ai-formalizationSkill
- lean-axiom-closureSkill
- lean-bigraph-modelingSkill
- lean-bisectSkill
- lean-blueprintSkill
- lean-buildSkill
- lean-causal-reasoningSkill
- lean-competitive-mathSkill
- lean-convergence-verificationSkill
- lean-core-onlySkill
- lean-dag-visualizerSkill
- lean-deep-auditSkill
- lean-doc-feedbackSkill
- lean-doc-improvementSkill
- lean-doc-requirementsSkill
- lean-enforcementSkill
- lean-formalization-breakdownSkill
- lean-gatewaySkill
- lean-integration-protocolSkill
- lean-knowledge-formalizationSkill
- lean-math-analysisSkill
- lean-math-discreteSkill
- lean-math-dynamicalSkill
- lean-math-foundationsSkill
- lean-math-optimizationSkill
- lean-math-stochasticSkill
- lean-mweSkill
- lean-nested-learningSkill
- lean-package-researchSkill
- lean-pedagogical-expositionSkill
- lean-proof-refactorSkill
- lean-proof-repairSkill
- lean-proof-reviewSkill
- lean-proofSkill
- lean-prSkill
- lean-quality-engineSkill
- lean-replay-verificationSkill
- lean-reportSkill
- lean-researchSkill
- lean-retroactive-auditSkill
- lean-retro-methodologySkill
- lean-review-councilSkill
- lean-security-formalizationSkill
- lean-setupSkill
- lean-specificationSkill
- lean-tautology-triageSkill
- lean-upstream-portingSkill
- lean-vendor-substrateSkill
- lean-zettelkastenSkill
- math-product-managementSkill
- The first 60 shown.
The file
We split this skill into the rules it gives an agent
4 rules. About 0 are common, 2 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 47
Write the Lean encoding; verify Mathlib primitives exist at the current pin.
- Distinctive: line 50
STOP if the question is purely methodological (no Lean) — delegate to the matching applied-* skill.
- Very specific: line 51
STOP if Mathlib primitives are missing — escalate to @lean-research.
- Very specific: line 52
STOP if the spec is informal — delegate to @lean-specification first.
≈ “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 4 Applied Reasoning & Strategy
Guide to formalizing applied reasoning — from intelligence analysis to strategic decision-making — in Lean 4.
Routing
- USE FOR: Applied reasoning for intelligence analysis, strategy creation and analysis, brainstorming methodologies, investigative reasoning, and domain-specific decision-making. Use when formalizing strategic frameworks, situational analysis, hypothesis generation workflows, decision-under-uncertainty models, or when connecting theoretical formalization to practical operational contexts. Bridges mathematical formalization to real-world application domains.
- DO NOT USE FOR: pure intelligence-analysis methodology (use @lean-applied-reasoning); strategy analysis methodology (use @lean-applied-reasoning); legal reasoning methodology (use @applied-legal-reasoning).
- TRIGGERS: applied reasoning, intelligence formalisation, strategy formalisation, investigative reasoning, domain-specific reasoning.
Workflow
- Classify the applied-reasoning task: intelligence-formalisation, strategy-formalisation, investigative-reasoning, or domain-specific reasoning.
- Pick the corresponding body section; identify the Lean primitives + Mathlib lemmas it depends on.
- Write the Lean encoding; verify Mathlib primitives exist at the current pin.
- Hand off: to
@lean-proof-reviewfor review, to@lean-enforcementfor CI, to@lean-zettelkasten.
Recovery & STOP
- STOP if the question is purely methodological (no Lean) — delegate to the matching applied-* skill.
- STOP if Mathlib primitives are missing — escalate to
@lean-research. - STOP if the spec is informal — delegate to
@lean-specificationfirst.
Handoffs
- Predecessors:
agent:gateway,skill:lean-research. - Successors:
skill:lean-proof-review,skill:lean-enforcement,skill:lean-zettelkasten.
Detailed reference
Full content for lean-applied-reasoning lives in
references/lean-applied-reasoning-handbook.md.
Load that file when the skill is convened; the SKILL.md only carries
the dispatch contract and the parts index.
| Section | Topic |
| Part 1 | Intelligence Analysis Formalization |
| Part 2 | Strategy Formalization |
| Part 3 | Brainstorming Methodology |
| Part 4 | Investigative Reasoning (Project Core Domain) |
| Part 5 | Decision Under Uncertainty |
| Part 6 | Project & Product Management for Mathematics |
| Part 7 | Research Council Integration |
See also
../../references/lean-applied-reasoning-handbook.md— Full handbook (extracted from this skill)../lean-proof-review/SKILL.md— Successor../lean-enforcement/SKILL.md— Successor../lean-zettelkasten/SKILL.md— Successor
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.