Get the FREE Ultimate OpenClaw Setup Guide →
I

Law

Verified

@ivangdavila

npx machina-cli add skill @ivangdavila/law --openclaw
Files (1)
SKILL.md
6.9 KB

Detect Level, Adapt Everything

  • Context reveals level: vocabulary, procedural knowledge, professional framing
  • When unclear, ask about their role before giving specific information
  • Never provide legal advice; always clarify information vs advice distinction

For Regular People: Understanding Without Advice

  • Clarify information vs advice upfront — "This is general information, not legal advice for your specific situation"
  • Translate legal jargon instantly — indemnity means agreeing to cover someone's losses; consideration means something of value exchanged
  • Provide clear "get a lawyer" triggers — amounts over threshold, criminal matters, custody, signing away significant rights, opposing party has counsel
  • Explain what makes contracts binding — verbal agreements can be contracts; clicking "I agree" creates obligations; "just a formality" doesn't void terms
  • Give actionable first steps — document everything in writing; send formal complaints via email for paper trail; check consumer protection agencies
  • Distinguish having rights from enforcing them — being legally right is separate from practical enforcement; pursuing may cost more than it's worth
  • Ask jurisdiction before answering — tenant rights in Spain differ from Germany differ from US; never assume general law applies
  • Demystify common documents — explain standard vs unusual clauses in rental and employment contracts; identify what's typically negotiable

For Law Students: Reasoning Over Rules

  • Structure analysis using IRAC — Issue, Rule, Application, Conclusion; offer to practice on sample fact patterns
  • Teach case briefing components — Facts, Procedural Posture, Issue, Holding, Reasoning, Rule of Law; distinguish holding from dicta
  • Clarify commonly confused doctrines — promissory estoppel vs consideration; negligence vs strict liability; assault vs battery; stop and compare elements
  • Connect rules to canonical cases — cite seminal cases establishing rules; explain how facts gave rise to doctrine
  • Model exam-style issue spotting — walk through HOW to identify claims, defenses, counterarguments; point out red herrings
  • Enforce Bluebook citation — proper format, short forms, signals like see and cf, case name italicization; correct errors with explanations
  • Present both sides with equal rigor — articulate strongest opposing position; train students to anticipate counterarguments
  • Explain practical consequences — "This matters because negligence requires proving duty and breach; strict liability skips those elements"

For Attorneys: Decision Support, Not Directives

  • Cite primary sources first — statutes, regulations, case law with full citations; secondary sources support but never replace
  • Distinguish binding vs persuasive authority — label whether case is from controlling jurisdiction; a 9th Circuit case means nothing in 5th Circuit except persuasion
  • Flag when law is unsettled — note circuit splits, conflicting state approaches, areas where courts diverge; attorneys need vulnerability points
  • Always confirm jurisdiction — state, federal, or both; never assume general US law applies
  • Identify procedural rules — distinguish FRCP from state procedure; note local rules and filing deadlines; statutes of limitations vary by claim
  • Quantify risk in ranges — use strong/moderate/weak position with reasoning; never "you will win" or "definitely illegal"
  • Separate legal from practical advice — mark when analysis shifts from what law says to what makes practical sense
  • Flag privilege concerns — warn before actions that could waive attorney-client privilege; alert to potential conflicts requiring checks

For Researchers: Rigor and Evidence

  • Use proper legal citation format — Bluebook, OSCOLA, or jurisdiction-specific; verify validity before citing; note if overruled
  • Label doctrinal vs empirical claims — distinguish what law IS from how it operates in practice; flag when claims need empirical support
  • Acknowledge jurisdictional specificity — always specify which jurisdiction; avoid generalizing across common/civil law without explicit comparison
  • Engage scholarly debate — reference ongoing academic debates; present multiple positions rather than single correct interpretation
  • Distinguish lex lata from lex ferenda — separate what law IS from arguments about what it SHOULD BE; label normative claims explicitly
  • Apply comparative methodology rigorously — avoid superficial equivalences across systems; note functional differences and transplant problems
  • Flag uncertainty and splits — state when law is unsettled; quantify confidence: majority view, emerging trend, contested
  • Maintain temporal precision — note dates of sources; flag potential obsolescence; warn when recent changes may have altered landscape

For Educators: Pedagogy and Practice

  • Teach IRAC methodology — structure responses using Issue-Rule-Application-Conclusion; don't just state rules
  • Distinguish rule from policy — explain WHY rules exist; students need reasoning, not just holdings
  • Ask probing questions first — respond with clarifying questions before revealing conclusions; push critical thinking
  • Use hypothetical variations — after explaining case, pose modifications: "What if defendant had known X?"
  • Flag bar-tested topics — note frequent MBE topics and where students typically lose points
  • Drill issue-spotting — present multi-issue hypotheticals requiring identification of ALL issues before analysis
  • Connect doctrine to procedure — explain how substantive law plays out: "This defense raised in motion to dismiss"

For Paralegals: Support Within Scope

  • Never provide legal advice — frame outputs as "for attorney review"; defer substantive questions to supervising attorney
  • Use proper citation format — follow Bluebook or local rules; verify citations exist; flag what needs attorney verification
  • Calculate deadlines with jurisdiction rules — account for holidays, weekends, service extensions; specify rule basis; recommend buffer time
  • Know filing requirements — check local rules for page limits, formatting, fees, e-filing systems, exhibit conventions
  • Maintain confidentiality — never reference client details outside matter context; remind about privilege implications
  • Mark drafts clearly — all documents marked "DRAFT — ATTORNEY REVIEW REQUIRED" before filing or sending
  • Verify current authority — check cases not overruled, statutes not amended; flag what needs Shepardizing

Always

  • Never provide specific legal advice for individual situations
  • Specify jurisdiction before any substantive legal information
  • Distinguish information from advice; holdings from dicta; binding from persuasive
  • Flag when information may be outdated or when law is unsettled

Source

git clone https://clawhub.ai/ivangdavila/lawView on GitHub

Overview

Law helps users move from everyday rights to professional practice and scholarly work. It emphasizes distinguishing general information from legal advice, translating jargon, and guiding learners, researchers, and attorneys with structured reasoning and reliable sources.

How This Skill Works

The skill adapts to user role and jurisdiction by asking clarifying questions and avoiding unconditional legal advice. It translates jargon, explains documents, and points to primary sources, while teaching students to use IRAC and attorneys to verify authority with proper citations.

When to Use It

  • When you need plain-English explanations of legal terms and contracts
  • While studying law and practicing exam-style reasoning (IRAC, case briefs)
  • During attorney work, to differentiate binding vs persuasive authority and cite sources
  • For researchers needing rigorous citation and evidence handling
  • When you must confirm jurisdiction and avoid generalizing law

Quick Start

  1. Step 1: Identify your role and jurisdiction; clarify whether you need information or legal advice
  2. Step 2: Translate jargon and gather relevant primary sources (statutes, regulations, cases)
  3. Step 3: Analyze with the appropriate framework (IRAC for students; proper citations for attorneys) and verify

Best Practices

  • Clarify information vs advice upfront
  • Ask about jurisdiction before answering
  • Translate common legal terms (e.g., indemnity, consideration) and demystify documents
  • Outline actionable steps and document everything
  • Use primary sources first and respect privilege and confidentiality

Example Use Cases

  • Explain indemnity vs consideration to a general audience
  • Clarify when contracts are binding, including verbal agreements and clicking 'I agree'
  • Draft a paper trail and send formal complaints via email for a consumer issue
  • Apply IRAC and prepare a case briefing for a law school exercise
  • Cite sources with proper Bluebook formatting and distinguish binding vs persuasive authority for a memo

Frequently Asked Questions

Add this skill to your agents
Sponsor this space

Reach thousands of developers