legal-advice
Skill0 starsChanged 33 days agoMITView on GitHub
Answer a business legal question or write advice (a quick answer, a client email, an advice letter or an internal memo) for Australia, the UK, New Zealand or the US. Leads with the answer, applies the right jurisdiction's law to the facts, checks the user's premise, verifies the rules relied on, flips the facts that would change the answer, sets out options and next steps with deadlines, and explains clauses in plain English. Use for "can I...", "do I have to...", "what does this clause mean", "is this legal", "what are my options", "write advice to the client", or any direct legal question that is not a document review.
In this repository27 other files it gives its agents.
- adversarial-reviewSkill
- business-saleSkill
- business-setupSkill
- cite-checkSkill
- contract-reviewSkill
- disputesSkill
- doc-auditSkill
- draft-contractSkill
- employment-checkSkill
- fundraisingSkill
- ip-brandSkill
- jurisdiction-adaptSkill
- law-auSkill
- law-change-impactSkill
- law-nzSkill
- law-ukSkill
- law-usSkill
- lease-reviewSkill
- legal-health-checkSkill
- legal-researchSkill
- marketing-complianceSkill
- nda-triageSkill
- privacy-complianceSkill
- redlineSkill
- scenario-testSkill
- sprintlaw-modeSkill
- website-complianceSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
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
- Distinctive: line 18
Check any rule, date or threshold the user states before relying on it.
- Very specific: line 19
Every rule you rely on is verified from an official source this session or tagged [unverified].
- Distinctive: line 21
Never invent facts. State the assumptions the answer depends on.
- Distinctive: line 47
Answer: use calibrated words, not percentages: Yes, Very likely, Probably, Unclear (it turns on X), Probably not, No.
- Distinctive: line 61
Use this pattern, in plain English:
- Distinctive: line 87
Do not give tax, immigration, criminal or litigation-strategy opinions beyond orientation.
- Distinctive: line 88
If a question crosses borders, say which country's law answers which part.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Legal advice
Small-business owners want three things from legal advice: the answer, what to do, and what it will cost them if they get it wrong. Everything else is support. This skill produces advice a senior lawyer would sign: short, correct for the jurisdiction, honest about uncertainty, and specific about next steps.
Non-negotiables
- Settle the jurisdiction first and load the pack (
law-au,law-uk,law-nz,law-us). For the US, the state. Never answer under the wrong law. - Check any rule, date or threshold the user states before relying on it. If it is wrong, say so in the first sentence that depends on it.
- Every rule you rely on is verified from an official source this session or tagged
[unverified]. Never cite a case you have not confirmed (runcite-checkfor anything that will be sent). - Answer first. Then why. Then what to do.
- Never invent facts. State the assumptions the answer depends on.
Step 1. Sort the question
Decide what kind of problem it is before reaching for doctrine:
| Kind | Example | Size of answer |
| Clear legal rule | "Do I have to pay annual leave out when an employee resigns?" | Short answer, the rule, the source, the step |
| Legal risk judgment | "Can I put a 12-month non-compete in this contract?" | Answer with likelihood words, the factors, a safer alternative |
| Business decision with a legal overlay | "Should I trade as a company?" | The trade-offs, a recommendation, the legal must-dos |
| Interpretation of a document | "What does clause 12 mean?" | Plain meaning, why it is there, options |
| Dispute or deadline | "They haven't paid for 90 days" | Deadlines first, then path (hand to disputes) |
| Out of scope for confident advice | Criminal exposure, immigration status, litigation strategy, tax opinions | Orientation only, and say who should advise (P15) |
Step 2. Facts and issues
- List the facts that matter and the ones missing. Ask at most three questions if a missing fact would flip the answer; otherwise state assumptions.
- Turn the request into the precise legal questions the law must answer. "Can I fire him?" becomes: is he an employee or contractor; is he protected from dismissal at all (service, size of business, award or contract); is there a valid reason; what process is required; what notice or pay is due.
Step 3. Rule, application, answer
For each issue:
- Rule: from the jurisdiction pack's area file, then the official source. Pinpoint section or authority, with a provenance tag.
- Application: apply the rule to these facts. Name the facts that drive the result.
- Answer: use calibrated words, not percentages: Yes, Very likely, Probably, Unclear (it turns on X), Probably not, No. Say what the likelihood depends on.
Where the law is genuinely unsettled or the facts are borderline, say so plainly and give the safer course.
Step 4. What would change the answer
List the two to five facts the answer depends on and flip each one: "If the worker sets their own hours and can send someone else, the answer moves from employee to likely contractor." These are the questions to confirm with the client before they act. (This is the advice mode of scenario-test.)
Step 5. Options and next steps
Give the realistic options, each with: what it involves, cost and time in rough terms, risk, and when it is the right choice. Recommend one. Then numbered next steps with owners and dates. Put any deadline (limitation period, notice period, cooling-off window, regulator response date) at the top of the reply.
Explaining a clause
Use this pattern, in plain English:
- What it means: one or two sentences, no legal terms.
- Why it is there: what risk it protects whom against.
- Is it normal: market practice for this kind of deal and party, labelled
[judgment]. - Your options: accept, ask for a specific change (give the words), or push back hard, and what each costs.
- Recommendation.
Formats
Pick the one asked for, or the lightest that does the job. Templates are in references/formats.md.
| Format | Use for |
| Quick answer | Chat. Three to eight sentences plus next steps. |
| Client email | Calm, plain, answer in the first line, no heavy bold, no em dashes. |
| Advice letter | Formal advice the client will keep and act on. |
| Internal memo | Lawyer to lawyer: question, short answer, facts, law, analysis, uncertainties, sources. |
Reply
The answer in the first line or two; the reasons in plain English with tagged authorities; deadlines; options and recommendation; next steps; what would change the answer; the reliance note (law applied and "as at" date, sources checked, assumptions, items to verify).
Limits
- General information about the law is not a substitute for advice on a specific matter where a lot is at stake. Say when the user should get a qualified lawyer and what to ask them (P15 in
sprintlaw-mode). - Do not give tax, immigration, criminal or litigation-strategy opinions beyond orientation.
- If a question crosses borders, say which country's law answers which part; do not blend them.
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
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.

