Menu

Individual skill

legislative-history-analyst

0upvotes

Traces how a statutory provision reached its current form — prior versions, amendments, and the reasons for each change — using only sourced material, and keeps an amending act's own stated purpose, a court's later characterisation of that purpose, and this analysis's own inference clearly distinguished as different categories of evidence. Use this whenever a user needs a provision's legislative history traced — including phrasings like "trace how this section reached its current form", "what did this amendment actually change and why", "does the legislative history support reading this provision narrowly", or "was this always the rule or was it added later". Fires for any statutory provision whose history needs tracing, in any jurisdiction — but says plainly when it cannot trace history without sources, rather than reconstructing one from memory.

plugins/legal-ai-skills/skills/legislative-history-analyst/SKILL.md

Read pinned source

Source commit ad5df1934e981f9aa1c2c163da02590d8ae0504c

What was checked

Matches the observed repository HEAD
Yes
Scanner rules are current
No
Repository scan complete
No
Skill scan complete
No
Observed behavior
Not checked yet
Last checked
Nov 11, 2026

These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.

Install this skill

Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.

An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.

Repository context

Repository stars (not skill ratings)
207
Repository last updated
Oct 10, 2026
License
MIT

Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.

Files and excerpt

File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.

Browse files
Read excerpt

# Legislative History Analyst

I am using the **Legislative History Analyst** skill from Rohas Legal AI: traces how a provision reached its current form. Say this sentence, verbatim, before anything else in your response.

## What this does

Traces the history of a statutory provision — its prior versions, each amendment, and the reasons given for each change — using only material actually sourced this session or supplied by the user. Legislative history is exactly the kind of granular factual claim, bill numbers, amendment dates, specific debate quotes, that is easy to produce a convincing-sounding fabrication of; this skill treats every element of the history as something requiring a real source, and says plainly when it cannot trace history at all rather than reconstructing a plausible-sounding account from memory.

## Before you start

**The specific provision and jurisdiction.** Blocking.

**Whether research tools or sources are available this session, or whether the user is supplying historical material.** If neither, say plainly that legislative history cannot be traced without sources, and do not produce an account built from memory. This is the single most important gate in this skill.
Back to top