agentleFS
SprintlawSprintlaw/legal-skills/skills/legal-research/SKILL.md

legal-research

Skill0 starsChanged 33 days agoMITView on GitHub

Research a point of law properly for Australia, the UK, New Zealand or the US. Frames the precise question, fixes the jurisdiction and the date the law must be applied at, writes a research plan, works through primary sources before secondary ones, reads sections in context (definitions, exceptions, commencement, transitional rules), checks currency and how cases have been treated, handles state-by-state surveys, keeps a research log with dates, and writes a research memo with pinpoint citations. Use for "research", "find the law on", "what's the authority for", "survey the states", "has this changed", or when an answer will be relied on and must be sourced.

9 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

10 rules. 0 are common, 9 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 3 edited versions we read keep these.

  • 9

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Every source you rely on is opened and read this session, with the date checked.

    line 18
  2. Distinctive:

    Never cite a case you have not located on an official or reputable case database.

    line 19
  3. Distinctive:

    Write down, before searching:

    line 24
  4. Distinctive:

    Read the operative section and the definitions section, the application or scope provisions (who and what it covers), exceptions and …

    line 39
  5. Distinctive:

    Check the version: the "as at", "compilation" or "point in time" date on the official site, and any amendments not yet in force.

    line 40
  6. Distinctive:

    Look for regulations or rules made under the Act that fill in detail.

    line 41
  7. Distinctive:

    Check later treatment as far as open sources allow (cited, followed, distinguished, overruled).

    line 47
  8. Distinctive:

    When the question is "what is the rule in each state":

    line 57
  9. Distinctive:

    Keep a running log while you work (in the reply for short tasks, in a file for long ones):

    line 66
  10. Distinctive:

    Use the jurisdiction's citation style where the reader expects it (for example AGLC in Australia, OSCOLA in the UK, the Bluebook in the …

    line 86

“Common” is measured: kept by at least 6 in 10 of the 3 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Legal research

Good legal research is mostly discipline: the right question, the right jurisdiction, the right date, primary sources before commentary, and a written trail of what was checked. Models fail research in predictable ways: they answer a nearby question, blend jurisdictions, cite from memory, and miss the amendment that commenced last month. This skill blocks each of those.

Non-negotiables

  • Primary sources (legislation, regulations, judgments) are the authority. Commentary, blogs and AI answers are leads, never authority.
  • Every source you rely on is opened and read this session, with the date checked. Everything else is [unverified].
  • Never cite a case you have not located on an official or reputable case database.
  • Separate jurisdictions completely. In federal systems (Australia, the US) separate federal and state law, and each state from the others.

Step 1. Frame

Write down, before searching:

  1. The precise question, as a lawyer would ask it. Not "can I fire someone", but "is an employee of a business with 12 employees, employed for 5 months, protected from unfair dismissal under the federal regime in Australia?"
  2. Jurisdiction(s) and level (federal, state, both).
  3. The relevant date. Law as at today, or as at the date of the facts (a contract signed in 2023, a dismissal last March). Transitional provisions often decide which version applies.
  4. What the answer is for (a decision, a document, a dispute) and how deep it needs to go.

Step 2. Plan

List: the likely sources (the Act, regulations, regulator guidance, leading cases), search terms, and the stop rule (when you have enough). Load the jurisdiction pack and read references/sources.md plus the area file for the starting statute list. For high-stakes research, show the plan to the user before running it.

Step 3. Primary sources, read in context

For each statute or regulation:

  • Read the operative section and the definitions section, the application or scope provisions (who and what it covers), exceptions and exemptions, penalties, and commencement and transitional provisions.
  • Check the version: the "as at", "compilation" or "point in time" date on the official site, and any amendments not yet in force.
  • Look for regulations or rules made under the Act that fill in detail.

For cases:

  • Find the judgment on an official or reputable database. Note the court and its place in the hierarchy (binding or persuasive here?).
  • Identify the holding on the point, as distinct from dicta.
  • Check later treatment as far as open sources allow (cited, followed, distinguished, overruled). Say if you could not check treatment.

Regulator guidance shows how the law is enforced in practice. Cite it as guidance, not as law.

Step 4. Currency

Before finishing, check specifically for: amendments since the version you read, bills or reforms announced with commencement dates, recent cases on the point, rules struck down or vacated by courts, and annually indexed figures. The jurisdiction pack's currency-watch.md lists the known moving parts as at its date; search for anything newer.

Step 5. Surveys across states or countries

When the question is "what is the rule in each state":

JurisdictionRule in one lineAuthority (pinpoint)Verified onNotes

Fill a row only from a source you opened. Leave a row as [unverified] rather than guessing from a neighbouring state. Surveys are where models fail most: be slow here.

Step 6. Research log

Keep a running log while you work (in the reply for short tasks, in a file for long ones):

| # | Source (URL) | Version or date | What it says (pinpoint) | Relevance |

Step 7. Memo

Question:
Short answer:
Jurisdiction and date of law applied:
Facts assumed:
Law: <statutes, regulations and cases with pinpoint citations and provenance tags>
Analysis: <application; strongest counter-argument; how a court or regulator would likely see it>
Currency: <recent or pending changes and their effect>
Open questions and conflicting authority:
Sources checked: <list with dates>

Use the jurisdiction's citation style where the reader expects it (for example AGLC in Australia, OSCOLA in the UK, the Bluebook in the US), but accuracy matters more than format.

Reply

Short answer first; then the memo or the parts asked for; then the reliance note. If the research found that the user's premise was wrong, that goes in the first line.

Limits

  • Open sources do not always show complete case treatment. If the conclusion depends on whether a case is still good law and you could not confirm it, say so.
  • Research is not advice. Hand the result to legal-advice to apply it to the client's situation.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.