Now liveThe Skillselion MCP - thousands of ranked skills, loaded into your agent mid-task. No install.Get it →
borghei avatar

Statute Analysis

  • 45 installs
  • 451 repo stars
  • Updated July 21, 2026
  • borghei/claude-skills

Statute Analysis is a Claude skill that interprets statutes and regulations and maps them into classified compliance requirements using legal hierarchy, canons of construction and operative-keyword analysis.

About

Statute Analysis is a framework for reading, interpreting and applying statutes, regulations and rules. It walks the legal hierarchy, applies canons of construction, extracts operative keywords (shall/must/may), and classifies requirements into obligations, permissions, conditions and exemptions. Two Python tools scan statute text for operative keywords and classify requirements by type, implementation team, enforcement mechanism and penalty. It is used to map compliance obligations from legislative text and is explicitly marked experimental and not legal advice.

  • Interprets statutes and regulations: legal hierarchy, canons of construction, operative keywords
  • Classifies requirements by type, implementation team, enforcement and penalty
  • Maps compliance obligations from legislative text (marked experimental, not legal advice)

Statute Analysis by the numbers

  • 45 all-time installs (skills.sh)
  • Ranked #1,373 of 2,203 Security skills by installs in the Skillselion catalog
  • Data as of Aug 5, 2026 (Skillselion catalog sync)
At a glance

statute-analysis capabilities & compatibility

Free; runs local Python scripts on statute text, no API keys.

Use cases
security audit · research
Pricing
Free
From the docs

What statute-analysis says it does

Statute and regulation interpretation framework. Use when reading statutes, classifying requirements, analyzing operative keywords, applying canons of construction, or mapping compliance obligatio
SKILL.md
This skill is provided for educational and informational purposes only. It does NOT constitute legal advice.
SKILL.md
Classifies statutory requirements by type, implementation team, enforcement mechanism, and penalty.
SKILL.md
npx skills add https://github.com/borghei/claude-skills --skill statute-analysis

Add your badge

Show developers this skill is listed on Skillselion. Paste this into your README.

Listed on Skillselion
Installs45
repo stars451
Last updatedJuly 21, 2026
Repositoryborghei/claude-skills

What it does

Interpret statutes and map compliance obligations from legislative text into classified requirements.

Who is it for?

Reading statutes, classifying requirements, and mapping compliance obligations from legislative text.

Skip if: Producing legal advice; it is explicitly experimental and informational only.

When should I use this skill?

You are reading a statute, classifying requirements, analyzing operative keywords, or mapping compliance obligations from legislative text.

What you get

Classified statutory requirements (obligations, permissions, conditions, exemptions) with implementation team, enforcement mechanism and penalty mapped.

  • Operative-keyword analysis
  • Classified requirements
  • Implementation obligation matrix

By the numbers

  • 2 Python tools (statute keyword analyzer, requirement classifier)
  • 6-level legal hierarchy (Constitution to case law)

Files

SKILL.mdMarkdownGitHub ↗
⚠️ EXPERIMENTAL — This skill is provided for educational and informational purposes only. It does NOT constitute legal advice. All responsibility for usage rests with the user. Consult qualified legal professionals before acting on any output.

Statute Analysis

Production-ready framework for reading, interpreting, and applying statutes, regulations, and rules. Covers the full lifecycle from identifying the legal hierarchy through extracting actionable requirements and mapping implementation obligations.

---

Table of Contents

---

Legal Hierarchy

Understanding the source hierarchy is the foundation of statutory analysis.

SourceCreated ByAuthorityExample
ConstitutionSovereign/peopleSupremeU.S. Constitution, EU Treaties
StatuteLegislaturePrimary legislationGDPR, Clean Air Act, AI Act
RegulationExecutive agencyDelegated authorityFDA 21 CFR, FTC rules
RuleAgency or courtProcedural/interpretiveFederal Rules of Civil Procedure
GuidanceAgencyNon-binding, persuasiveFDA guidance documents, CNIL guides
Case lawCourtsBinding within jurisdictionSupreme Court precedent

Key principle: Higher sources override lower sources. Regulations cannot exceed statutory authority. Guidance cannot create new obligations not grounded in statute.

---

Preliminary Steps

Before interpreting any statutory provision, complete these checks:

1. Verify currency and status -- Is this the current, in-force version? Check for amendments, repeals, or sunset clauses. Use official sources (government gazettes, EUR-Lex, congress.gov). 2. Understand the regulatory ecosystem -- What regulations, rules, and guidance implement this statute? Map the full hierarchy. 3. Browse the full structure -- Read the table of contents, definitions section, scope provisions, and transitional articles before diving into specific sections. 4. Identify the definitions section -- Almost all statutes define key terms. These definitions override ordinary meaning. 5. Check effective dates -- Different provisions may have different effective dates. Map the compliance timeline. 6. Identify your role -- Statutes impose different obligations depending on the reader's role (e.g., "provider" vs "deployer" in the EU AI Act, "controller" vs "processor" in GDPR).

---

Tools

Statute Keyword Analyzer

Scans statute text for operative keywords and classifies obligations, permissions, conditions, and exemptions.

# Analyze a statute file
python scripts/statute_keyword_analyzer.py --input statute.txt

# Analyze with JSON output
python scripts/statute_keyword_analyzer.py --input regulation.txt --json

# Analyze inline text
python scripts/statute_keyword_analyzer.py --text "The controller shall implement appropriate technical measures..."

# Save analysis report
python scripts/statute_keyword_analyzer.py --input statute.txt --output analysis.json

Requirement Classifier

Classifies statutory requirements by type, implementation team, enforcement mechanism, and penalty.

# Classify requirements from a JSON list
python scripts/requirement_classifier.py --input requirements.json

# Classify with JSON output
python scripts/requirement_classifier.py --input requirements.json --json

# Classify inline requirement
python scripts/requirement_classifier.py --text "Controllers must provide data subjects with a privacy notice at the point of collection"

# Generate implementation matrix
python scripts/requirement_classifier.py --input requirements.json --output matrix.json

---

Core Interpretation Techniques

Definitions Analysis

Statutory definitions control meaning. Pay attention to the verb used:

VerbTypeMeaningExample
"means"ExhaustiveThe definition is complete; no other meaning applies"'Personal data' means any information relating to an identified or identifiable natural person"
"includes"IllustrativeThe definition provides examples but is not limited to them"'Processing' includes collection, recording, organization, structuring..."
"does not include"ExclusionExplicitly carves out items from scope"'Consumer' does not include a natural person acting in a commercial or employment context"
"refers to"PointerIncorporates an external definition"'Harmonised standard' refers to a European standard as defined in Regulation (EU) No 1025/2012"

Operative Keywords

KeywordClassificationLegal Effect
shallMandatoryCreates an obligation; must be done
mustMandatorySame as "shall" in modern drafting
mayPermissiveCreates permission; optional
may notProhibitiveCreates a prohibition
andConjunctiveAll listed items required
orDisjunctiveAny listed item sufficient
unlessExceptionNegates the rule when condition is met
exceptExceptionCarves out specific items from the rule
subject toConditionalRule applies but another provision modifies it
notwithstandingOverrideThis provision prevails over conflicting provisions
provided thatConditionAdds a requirement that must be satisfied
if...thenConditionalTrigger condition and consequence
uponTemporal triggerAction required when event occurs

Conjunctive vs Disjunctive Analysis

This distinction determines whether ALL conditions must be met or ANY single condition suffices.

PatternReadingPractical Impact
"A, B, and C"All three requiredMust satisfy every element
"A, B, or C"Any one sufficientSatisfy any single element
"A, B, and/or C"AmbiguousFlag for clarification; analyze context
"both A and B"Explicitly conjunctiveMust satisfy both
"either A or B"Explicitly disjunctiveSatisfy one
Serial comma ambiguityContext-dependentApply whole-act rule for consistency

---

Canons of Construction

See references/canons_of_construction.md for the complete 12-canon reference.

Quick Reference

CanonCore RuleWhen to Apply
General-Terms CanonGeneral terms get general meaningDefault interpretation
Expressio UniusExpressing one thing excludes othersSpecific lists without catchall
Whole-Act RuleInterpret provisions consistentlyApparent conflicts between sections
Consistent UsageSame term = same meaning throughoutTerm appears multiple times
Meaningful VariationDifferent terms = different meaningsSimilar but distinct terms used
Surplusage CanonEvery word has meaning; no redundancyTempted to treat words as surplus
Noscitur a SociisWords known by their associatesAmbiguous term in a list
Ejusdem GenerisGeneral follows specific = limited"...and other similar" patterns
Against IneffectivenessPrefer reading that gives effectTwo possible readings
Avoiding AbsurdityReject absurd outcomesLiteral reading produces nonsensical result
Remedial StatutesConstrue liberallyConsumer protection, safety statutes
Rule of LenityAmbiguity favors the regulated partyCriminal or penalty provisions

---

Interpretation Sources

When statutory text is ambiguous, consult sources in this order:

PrioritySourceWeightWhere to Find
1Statutory text itselfControllingOfficial gazette, codified law
2Definitions sectionControllingUsually first articles/sections
3Legislative purpose (recitals, preamble)StrongPreamble, "Whereas" clauses
4Canons of constructionStrongLegal treatises, case law
5Case law interpreting the provisionStrong-to-moderateCourt databases
6Agency regulations implementing statuteModerateAgency websites, CFR
7Agency guidance and FAQsPersuasive onlyAgency websites
8Legislative historyWeak (varies by jurisdiction)Congressional record, Hansard
9Academic commentaryPersuasive onlyLegal journals

---

Requirement Classification

Every statutory requirement maps to an implementation category:

TypeDescriptionTypical OwnerExample
DisclosureInformation must be provided to someoneLegal / CompliancePrivacy notice requirements
OperationalProcess or procedure must existOperations / ComplianceRecord-keeping obligations
TechnicalSystem capability or safeguard requiredEngineeringEncryption, access controls
UI/DesignUser interface must include specific elementsProduct / DesignConsent mechanisms, opt-out buttons
OrganizationalGovernance structure or role requiredManagement / HRAppointing a DPO, board oversight
DocumentationWritten records must be maintainedLegal / ComplianceImpact assessments, audit trails
ReportingInformation must be submitted to authorityLegal / ComplianceBreach notification, annual reports

---

Cross-Jurisdictional Analysis

When requirements from multiple jurisdictions apply:

1. Map applicable jurisdictions -- Where are your users, your entity, and your data? 2. Identify overlapping requirements -- Many frameworks share common obligations. 3. Find the highest common denominator -- Design for the strictest requirement that satisfies all jurisdictions. 4. Flag conflicts -- Where requirements genuinely conflict, document the conflict and seek legal advice. 5. Check preemption -- Federal law may preempt state law; EU regulations may preempt member state law.

---

Enforcement Analysis

For each statutory requirement, assess enforcement risk:

FactorAssessment Questions
Enforcement authorityWhich agency enforces? How active are they?
Penalty typesCivil fines, criminal penalties, administrative sanctions?
Penalty severityFixed amounts, percentage of turnover, per-violation?
Cure periodsIs there a right to cure before penalties apply?
Private right of actionCan individuals sue for violations?
Enforcement historyHas this provision been actively enforced?
Regulatory guidanceHas the agency clarified enforcement priorities?

---

Reference Guides

GuidePathDescription
Canons of Constructionreferences/canons_of_construction.md12 canons with definitions, examples, and misapplication warnings
Statutory Structurereferences/statutory_structure.mdHow statutes are organized, effective dates, preemption, enforcement

---

Workflows

Workflow 1: First Reading of a New Statute

1. Browse the full table of contents and structure. 2. Read the definitions section and scope provisions. 3. Check effective dates and transitional provisions. 4. Identify your role under the statute. 5. Run scripts/statute_keyword_analyzer.py on the full text. 6. Review the obligation/permission/exception map. 7. Identify provisions that apply to your role. 8. Validation: Definitions cataloged, role identified, key obligations listed.

Workflow 2: Requirement Extraction and Classification

1. Extract all provisions containing "shall," "must," or mandatory language. 2. For each requirement, identify: who (subject), what (action), when (trigger/deadline), how (standard). 3. Run scripts/requirement_classifier.py on the extracted requirements. 4. Review the implementation matrix. 5. Assign each requirement to an implementation team. 6. Prioritize by enforcement risk and deadline. 7. Validation: Every mandatory provision classified, assigned, and prioritized.

Workflow 3: Cross-Reference Resolution

1. Identify all cross-references in the target provision ("subject to Article X," "as defined in Section Y"). 2. Read each referenced provision in full. 3. Determine whether the cross-reference modifies, limits, or supplements the target provision. 4. Check for circular references or chains (A references B which references C). 5. Document the complete picture -- the target provision as modified by all cross-references. 6. Validation: All cross-references resolved; no orphan references.

---

Troubleshooting

ProblemLikely CauseResolution
Term not defined in statuteLegislature used ordinary meaningApply general-terms canon; check case law for judicial definitions
"And/or" ambiguityDrafting imprecisionCheck legislative history; apply whole-act rule; flag for legal review
Conflicting provisionsLater provision may override earlierCheck for "notwithstanding" clauses; apply later-in-time rule
Undefined thresholdDelegated to regulationCheck implementing regulations and agency guidance
Provision seems to have no effectMay be transitional or placeholderCheck effective dates and amendment history
Cross-reference to repealed sectionStatute not updated after amendmentCheck saving clauses; apply presumption against ineffectiveness

---

Success Criteria

CriterionTarget
All defined terms cataloged100% of definitions section mapped
Obligations extractedEvery "shall/must" provision identified
Requirements classifiedEach requirement has type, owner, enforcement, and priority
Cross-references resolvedNo unresolved references remain
Enforcement risk assessedEvery material obligation has enforcement analysis
Implementation matrix completeRequirements mapped to teams with timelines

---

Scope & Limitations

In scope: Reading and interpreting statutory text, extracting requirements, classifying obligations, applying canons of construction, mapping enforcement risk.

Out of scope: Providing legal advice, predicting court outcomes, drafting legislation, interpreting case law holdings, constitutional analysis.

Disclaimer: This skill provides a structured methodology for statutory analysis. It does not constitute legal advice. Always consult qualified legal counsel for binding interpretations.

---

Anti-Patterns

Anti-PatternWhy It FailsBetter Approach
Reading a section in isolationStatutes are interconnected; isolated reading misses cross-references, definitions, and scope limitationsAlways read definitions, scope, and cross-referenced provisions before interpreting
Treating guidance as lawAgency guidance is non-binding and can change; building compliance solely on guidance creates riskUse guidance to inform interpretation but anchor compliance to statutory text
Ignoring "what the statute doesn't say"Silence can mean permission, delegation, or an oversight; assuming the statute covers everything leads to compliance gapsAffirmatively check: does the statute address this scenario? If not, analyze why and what fills the gap
Applying one jurisdiction's interpretation to another"Personal data" in GDPR is not identical to "personal information" in CCPA; cross-pollinating definitions creates errorsAnalyze each statute independently using its own definitions and interpretive framework
Skipping the definitions sectionStatutory definitions override ordinary meaning; missing them leads to fundamental misreadingsAlways read the definitions section first, before any substantive analysis

---

Tool Reference

ToolInputOutputUse Case
statute_keyword_analyzer.pyStatute text file or inline textObligation/permission/exception mapFirst pass analysis of any legislative text
requirement_classifier.pyList of requirements (text or JSON)Implementation matrix with types, teams, enforcementConverting statutory obligations to actionable implementation tasks

Related skills

FAQ

Does this give legal advice?

No. It is marked experimental and for educational and informational purposes only, and users should consult qualified legal professionals.

What do the tools do?

One scans statute text for operative keywords and classifies obligations; the other classifies requirements by type, team, enforcement and penalty.

Securitycompliance

This week in AI coding

Five minutes, every Monday - the tools, releases and tactics for developers.

unsubscribe anytime.