mcpbeat Sign in

Statute Briefer Agent Skill

> Brief statutes and legislative Acts using the MAPS + RULES framework. Use when briefing statutes, analyzing legislative text, mapping statutory structure, extracting rule-modules from provisions, applying statutes to scenarios, or any statutory analysis task. Triggers include "brief this statute," "analyze this Act," "map the statute," "apply [statute] to [scenario]," "what are the elements of [provision]," "statutory analysis," or references to codified sections (such as 42 U.S.C. sections or Texas Health & Safety Code). Supports two modes - (A) text-only briefing for structural analysis, and (B) scenario-driven briefing that applies statutory provisions to specific facts.

5k tokens
context cost
the whole folder, loaded on every use
5
files
instructions only
0
copies elsewhere
how many repositories repackaged it
616
stars on the repo
on the repository, not the skill itself

Install

one command, takes just this skill from the repository
npx skills add https://github.com/lawve-ai/awesome-legal-skills --skill statute-briefer

What comes with it

15 764 bytes besides the instruction
README.md
references/example-brief.md
references/rule-module-template.md
references/scenario-template.md

The instruction itself

16 sections, as written by the author

Statute Briefer (MAPS + RULES)

Produce structured statute/Act briefs that (a) map the architecture of the entire statute/Act and (b) express operative provisions as rule-modules. Optionally apply provisions to scenarios with verbatim quotations.

Input Modes

Mode A: Text-only briefing

  • Required: Statutory text (or delimited excerpt)
  • Optional: Citation info, version type (enacted/codified/amendment), length constraint (short/standard/long)

Mode B: Scenario-driven briefing

  • Required: Statutory text + scenario description
  • Optional: Decision posture (advice/compliance/litigation), length constraint

If citation/version missing, label brief as "text-as-provided" without recency claims.

Output Structure

Every brief produces two layers. In Mode B, prepend the Scenario Module.

Scenario Module (Mode B only)

See references/scenario-template.md for detailed template.

Six components:

  • Scenario synopsis – Legally salient facts only
  • Issues framed as statutory questions – Frame disputes as statutory interpretation questions
  • Relevant excerpts (verbatim) – Block-quoted text with pinpoint cites; include adjacent definitions/exceptions
  • Application map (statute-to-facts) – For each issue: elements met, unclear, or disputed; identify missing facts
  • Context map (where excerpts live) – Title/Chapter/Section path for each excerpt
  • Not used but structurally important – Major Act components not triggered by scenario

MAPS (System-Level Map)

Five components:

  • Citation and text status – Citation block or "citation not provided"; note if partial text
  • Purpose – Quote express purpose/findings if present (with cite); otherwise label as inference
  • Structure map (entire Act) – Hierarchical outline with functional labels ("definitions," "prohibition," "enforcement," etc.); for large statutes, provide major-divisions overview plus zoomed detail
  • Scope and coverage – Covered actors, conduct, geography, time, jurisdictional hooks, explicit exclusions
  • Definitions and interpretive rules – Defined terms index; interpretive provisions; cross-references

RULES (Operational Modules)

For each major operative provision (or scenario-relevant provisions), produce a rule-module.

See references/rule-module-template.md for detailed template.

Rule-Module required fields:

  • Provision – Pinpoint cite
  • Trigger conditions (elements) – What activates the provision
  • Legal effect – Command / permission / prohibition / entitlement
  • Exceptions / defenses / safe harbors – Carve-outs from the rule
  • Procedure / decision-maker – Deadlines, notice, standards
  • Consequences – Penalties, remedies, invalidity, loss of benefits
  • Forum / enforcer – Agency, court, private plaintiff
  • Interaction rules – Preemption/savings, severability, effective date, cross-references

Mandatory Constraints

Verbatim Discipline

  • Never invent statutory language
  • Mark all quotations explicitly with pinpoint cites
  • If text is missing, say so and proceed with what is provided

Cross-Reference Discipline

  • When statute defines a term used in operative provision, incorporate that definition
  • Flag external cross-references: "cross-reference not included in provided materials"

Separation of Layers

  • Keep "Quoted Text" separate from "Explanation/Translation"
  • Use block quotes or clear markers

No Premature Narrowing

  • Even in scenario mode, include MAPS structure map at major-division level

Selection Rules

Mode A (no scenario): Major operative provisions = primary prohibitions/requirements/entitlements + enforcement/remedies + key definitions + preemption/savings/severability/venue

Mode B (with scenario): Prioritize provisions governing scenario issues + conditioning definitions/enforcement/exceptions. Still include full structure map.

Length Control

| Constraint | Structure Map | Rule-Modules | Definitions |

|------------|---------------|--------------|-------------|

| Short | Spine outline only | Most relevant only | Key scope terms only |

| Standard | Major divisions complete | Core operative provisions | Terms affecting scope |

| Long | Full detail | All operative provisions | Comprehensive index |

Uncertainty Handling

  • Insufficient facts → Label "Fact needed: [specific missing fact]"
  • Partial statute → Label "based on provided excerpt only"
  • Never fill in absent provisions

Exact Headings (for parsing)

Scenario Module
  Scenario synopsis
  Issues framed as statutory questions
  Relevant excerpts (verbatim)
  Application map (statute-to-facts)
  Context map (where excerpts live)
  Not used but structurally important

MAPS
  Citation and text status
  Purpose
  Structure map (entire Act)
  Scope and coverage
  Definitions and interpretive rules

RULES
  Rule-Module: [Provision cite]

Boundaries

  • Briefs statutes and legislative Acts only
  • No policy commentary unless asked
  • No grading or pedagogy commentary
  • No generating new statutory text
  • No case citations unless explicitly requested; may note "interpretive pressure points" as ambiguity flags

Other skills for the same job

different authors, same section of the catalogue
MCP Builder
by anthropics
vendor ×13

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

30k tokens scripts
Changelog Generator
by frostant
×9

Automatically creates user-facing changelogs from git commits by analyzing commit history, categorizing changes, and transforming technical commits into clear, customer-friendly release notes. Turns hours of manual changelog writing into minutes of automated generation.

774 tokens
Finishing A Development Branch
by ZhanlinCui
×7

Use when implementation is complete, all tests pass, and you need to decide how to integrate the work - guides completion of development work by presenting structured options for merge, PR, or cleanup

1k tokens
MCP Builder
by JayZeeDesign
×7

Guide for creating high-quality MCP (Model Context Protocol) servers that enable LLMs to interact with external services through well-designed tools. Use when building MCP servers to integrate external APIs or services, whether in Python (FastMCP) or Node/TypeScript (MCP SDK).

37k tokens scripts
Vercel React Native Skills
by vercel-labs
vendor ×6

React Native and Expo best practices for building performant mobile apps. Use when building React Native components, optimizing list performance, implementing animations, or working with native modules. Triggers on tasks involving React Native, Expo, mobile performance, or native platform APIs.

39k tokens
Vercel React Best Practices
by ratacat
×5

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

34k tokens
Next Best Practices
by vercel-labs
vendor ×4

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

20k tokens
Using Git Worktrees
by ZhanlinCui
×4

Use when starting feature work that needs isolation from current workspace or before executing implementation plans - creates isolated git worktrees with smart directory selection and safety verification

1k tokens

How to use it

Copy the folder

Take lawve-ai/statute-briefer from the repository into ~/.claude/skills for personal use, or into .claude/skills inside a project.

Check the name does not clash

The agent identifies a skill by the name field in its header. Two skills with the same name cannot sit side by side — one of them will be ignored.