statute-guide
First-pass framework for reading, interpreting, and structuring statutory analysis of US federal, state, and local law. Produces draft analysis for attorney review — not legal advice. Use this skill whenever the user references a specific US statute, regulation, ordinance, or rule by citation, asks "what does [statute X] require," asks for compliance scoping, applicability thresholds, requirement extraction, exemption analysis, definitional analysis, federal preemption analysis, or multi-state comparison — even if they don't explicitly ask for "statutory analysis." Halts and asks for missing i
npx skills add lawve-ai/awesome-legal-skills --skill statute-analyzer-rafal-fryc --agent claude-code
Same command for any agent — swap --agent for codex, cursor, copilot.
Weekly change comes from our own snapshots, not the repository page — it measures attention, not adoption.
What it does
Guides the user through a structured first-pass statutory reading and interpretation workflow for US federal, state, and local law. It instructs the agent to organize inputs into definitions, applicability thresholds, cross-references, and requirement categorization, with an attorney owning conclusions. It emphasizes attorney review, jurisdiction-specific handling, and halting for missing inputs.
How it works
The skill directs Claude to organize inputs around statutory text and references, identify definitions first, parse operator words (e.g., Shall, May, And, Or), track cross-references, and apply canons of construction. It treats interpretation as accretive toward judgment but requires the attorney to own conclusions, verification of current text, and ambiguity resolution. It explicitly states non-US law is out of scope and mandates escalation if foreign law appears. It provides an input checklist to confirm citation, text, jurisdiction level, version, and purpose before starting.
When to use it
Use when the user asks for first-pass structuring of how to read and interpret a specific statute, regulation, or rule; requests statutory interpretation methods; seeks legislative intent extraction; requires extraction of requirements or applicability analysis; or needs cross-jurisdictional compliance scoping.
What it can touch
The skill references tools and outputs for organizing analysis but does not enumerate executable touch points in this excerpt beyond requiring attorney review and jurisdiction confirmation. It notes Claude organizes analysis and that the lawyer owns legal conclusions.
Caveats
Out of scope: non-US law, case-law interpretation, constitutional interpretation, treaty interpretation, drafting language, or final client-facing opinions. It requires explicit inputs: Statutory citation, full text or authoritative link, jurisdiction level, version/effective date, and stated purpose. It mandates halting if inputs are missing or jurisdiction is unclear. It emphasizes using attorney review for conclusions and reserves authority to the attorney for interpretation and final decisions.
# Statutory Interpretation Guide (US Law) A structured first-pass framework for reading **US** statutes, regulations, ordinances, and rules — federal, state (all 50 states + DC + US territories), and local (county / municipal). Claude organises the analysis; a named attorney owns every legal conclusion. This skill does not handle non-US law (EU, UK, Canada, foreign jurisdictions, international treaties). If the user's matter touches foreign law, halt and route to counsel qualified in that jurisdiction. --- ## Audience Junior associates, compliance analysts, and paralegals conducting **first-pass** statutory review. All outputs require attorney review before any client-facing, regulatory, or transactional use. This skill is not for self-represented users seeking legal advice — the firewall between "structuring analysis" and "giving advice" exists because misreading statutory text has real consequences for real people, and a named attorney is the only person qualified to bear that risk. --- ## Work Shape **Accretive Judgment.** Claude structures the inputs to legal judgment — definitions, operator words, applicability thresholds, cross-references, requirement categorisation, notable
- Audience
- Work Shape
- When to Use This Skill
- Out of Scope
- Input Requirements
- Delegation Threshold & Accountability
- Confidence Bands
- Escalation Logic (Halt-and-Route)
- Failure Modes
- Understanding the Legal Hierarchy
- Before Reading: Preliminary Steps
- 1. Verify currency and status
- 2. Understand the regulatory ecosystem
- 3. Browse the structure first
What does the statute-guide skill do?
First-pass framework for reading, interpreting, and structuring statutory analysis of US federal, state, and local law. Produces draft analysis for attorney review — not legal advice. Use this skill whenever the user references a specific US statute, regulation, ordinance, or rule by citation, asks "what does [statute X] require," asks for compliance scoping, applicability thresholds, requirement extraction, exemption analysis, definitional analysis, federal preemption analysis, or multi-state comparison — even if they don't explicitly ask for "statutory analysis." Halts and asks for missing i
How do I install it?
Run `npx skills add lawve-ai/awesome-legal-skills --skill statute-analyzer-rafal-fryc --agent claude-code` — it drops the skill into your project so the agent can pick it up. Swap the --agent value for codex, cursor or copilot if you use one of those.
Where does this skill come from?
From lawve-ai/awesome-legal-skills, a repository with 618 stars. We read it straight from the repository tree rather than a submitted listing, so what you see here is what is actually published.
Is a popular skill a good skill?
Not necessarily. Stars measure attention, not adoption — a repository can trend for a week and be abandoned. That is why we show the weekly change from our own snapshots next to the total, instead of a single flattering number.