applied-legal-reasoning
Skill3 starsChanged 26 days agoApache-2.0View on GitHub
USE FOR: Legal reasoning formalization: statutory interpretation, case-based reasoning, argumentation frameworks. DO NOT USE FOR: formalising those legal models in Lean (@lean-applied-reasoning). TRIGGERS: statutory interpretation, case-based reasoning.
In this repository65 other files it gives its agents.
- AGENTS.mdAGENTS.md
- ai-guard-judge-evalSkill
- applied-data-information-securitySkill
- applied-engineering-disciplinesSkill
- epistemic-discovery-engineSkill
- epistemic-mappingSkill
- hol-metamath-adapterSkill
- isabelle-isar-adapterSkill
- itp-cross-portingSkill
- lean-ai-formalizationSkill
- lean-applied-reasoningSkill
- 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
3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 50
STOP if the question is about pure deontic logic — delegate to @lean-causal-reasoning.
- Very specific: line 51
STOP if the legal regime is jurisdiction-specific and not in the body — escalate to @research-council.
- Very specific: line 52
STOP if security/privacy policy dominates — delegate to @applied-data-information-security.
≈ “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
Legal Reasoning
Formal frameworks for legal analysis, argumentation, normative reasoning, and their intersection with formal verification and AI governance.
Routing
- USE FOR: Legal reasoning formalization — statutory interpretation, case-based reasoning, argumentation frameworks, defeasible rules, deontic norms, regulatory compliance, and their connection to provenance chains, governance structures, and formal verification for legal-adjacent AI systems.
- DO NOT USE FOR: formalising those legal models in Lean (use @lean-applied-reasoning); deontic reasoning specifically (use @lean-causal-reasoning); security policy (use @applied-data-information-security).
- TRIGGERS: statutory interpretation, case-based reasoning, argumentation framework, defeasible rule, deontic norm, legal reasoning, regulatory.
Workflow
- Classify the legal task: statutory interpretation, case-based reasoning, argumentation, or deontic-norm modelling.
- Pick the matching framework (ASPIC+, Carneades, defeasible-logic, deontic-action) from the body.
- Apply the framework; document the argument structure + defeaters.
- Hand off: to
@lean-causal-reasoningfor deontic-logic encoding, to@lean-applied-reasoningfor Lean formalisation, to@lean-zettelkasten.
Recovery & STOP
- STOP if the question is about pure deontic logic — delegate to
@lean-causal-reasoning. - STOP if the legal regime is jurisdiction-specific and not in the body — escalate to
@research-council. - STOP if security/privacy policy dominates — delegate to
@applied-data-information-security.
Handoffs
- Predecessors:
agent:gateway,skill:lean-research. - Successors:
skill:lean-applied-reasoning,skill:lean-causal-reasoning,skill:lean-knowledge-formalization.
Detailed reference
Full content for applied-legal-reasoning lives in
references/applied-legal-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 | Legal Reasoning Paradigms |
| Part 2 | Argumentation Frameworks |
| Part 3 | Defeasible Legal Rules |
| Part 4 | Statutory Interpretation |
| Part 5 | Case-Based Reasoning (CBR) |
| Part 6 | Regulatory Compliance Formalization |
| Part 7 | AI & Legal Reasoning |
| Part 8 | Cross-References |
See also
../../references/applied-legal-reasoning-handbook.md— Full handbook (extracted from this skill)../lean-applied-reasoning/SKILL.md— Successor../lean-causal-reasoning/SKILL.md— Successor../lean-knowledge-formalization/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.