legal-notice-handling
Skill27 starsChanged 11 days agoApache-2.0View on GitHub
Draft, reply to, or analyse a legal notice (rent or service-charge demand, forfeiture or breach notice, statutory notice, letter before action). Every deadline is a calendar date with its arithmetic; every threatened consequence is confirmed and lawfully available; an admitted fact never concedes a legal conclusion. Triggers on "draft a demand", "reply to this notice". Does not fire on a whole-contract review (contract-review) or the output file's integrity (deliverable-integrity).
In this repository59 other files it gives its agents.
- ai-surface-disciplineSkill
- blast-radius-grepSkill
- checkpoint-logSkill
- commission-the-rosterSkill
- committee-reviewSkill
- confirm-before-pushSkill
- constant-time-secret-compareSkill
- context-economySkill
- contract-reviewSkill
- cross-agent-reviewSkill
- date-parse-utc-safeSkill
- db-migration-verificationSkill
- deliverable-integritySkill
- dependency-upgrade-verificationSkill
- earn-every-lineSkill
- email-delivery-verificationSkill
- enforce-invariants-in-buildSkill
- enumerate-the-setSkill
- env-change-verificationSkill
- findings-are-evidenceSkill
- fixtures-from-realitySkill
- flag-deferred-itemsSkill
- guard-the-spend-pathsSkill
- handoverSkill
- honest-failure-surfacingSkill
- instrument-reports-itselfSkill
- legal-citation-integritySkill
- live-data-surgerySkill
- live-state-firstSkill
- lock-at-the-chokepointSkill
- mass-red-triageSkill
- measure-per-routeSkill
- no-silent-data-dropSkill
- one-real-rideSkill
- outbound-side-effect-idempotencySkill
- parallel-work-reconSkill
- pin-to-what-was-seenSkill
- plan-firstSkill
- price-the-spendSkill
- prove-it-can-failSkill
- prove-it-can-passSkill
- reproduce-the-real-buildSkill
- rerun-before-verdictSkill
- safe-smokesSkill
- secrets-in-outputSkill
- server-side-authoritySkill
- skill-library-builderSkill
- spawn-from-declared-stateSkill
- statute-to-obligations-registerSkill
- substantiate-outward-claimsSkill
- team-loopSkill
- tool-layer-bytesSkill
- trace-one-recordSkill
- unordered-eventsSkill
- unslop-codeSkill
- unslop-textSkill
- unslop-uiSkill
- verified-citationsSkill
- verify-the-effectSkill
The file
We split this skill into the rules it gives an agent
8 rules. About 0 are common, 7 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈7
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
- Very specific: line 42
Every deadline in a notice you draft, and every deadline found in a notice received, gets a row.
- Distinctive: line 85
Silence is a decision: If the client wants an allegation left unanswered, flag the risk that silence may be read as acceptance and record …
- Distinctive: line 180
Do not write a deadline as a period without its calendar date.
- Distinctive: line 181
Do not threaten a step the client has not confirmed, or one the law does not allow yet.
- Distinctive: line 182
Do not let an admission of fact carry a legal conclusion.
- Distinctive: line 183
Do not invent a fact, a defence, a clause or a statute to fill a gap in instructions.
- Distinctive: line 184
Do not assert that a notice meets a statutory form, content or service requirement you did not read this session.
- Distinctive: line 186
Do not soften a firm demand into a negotiable one, or harden it beyond instructions.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 notice handling
A notice is evidence of what was demanded and by when. Every date in it is a calendar date, every consequence is one the sender will carry out and is allowed to, and every admission is of fact only.
Why this exists
Notices fail on the details a reader checks later, usually in front of a tribunal:
- The soft deadline. "Within 14 days" or "promptly" leaves the recipient to choose the start date and the counting rule, and a statutory notice with a date outside its permitted window can be invalid.
- The empty threat. A consequence the client will not pursue, or cannot lawfully pursue yet, weakens the notice and can be used against the sender. In residential leasehold this is common: forfeiture threatened over a service charge that has been neither determined nor admitted (see the worked examples).
- The careless concession. "Yes, the payment was late" written so it also reads as "we are in breach". The fact can be conceded; the legal conclusion the other side draws from it is a separate question.
The rule that does the work
Build the tables the mode requires (see Modes) before writing prose. Print the result line with a part for each of those tables and no other; any failure is red. The counts below are illustrations.
- Draft:
Deadlines 3 (3 with calendar date and arithmetic) | Consequences asked 3, kept 2 (2 confirmed, 2 with basis, 2 available now), cut 1 (reported to the client) - Reply or analysis:
Deadlines 2 (2 with calendar date and arithmetic) | Allegations 6 in notice, 6 answered (0 admissions without a characterisation entry)
Count in notice from the notice itself, not from your table, and asked from the client's
instructions; asked must equal kept plus cut, so a dropped consequence shows as a gap
rather than vanishing.
- Deadline table.
Deadline | Source of the period (notice, lease clause, or statute read this session with URL and date, with the words quoted) | Start event and its date | Counting convention | Calendar date | Margin. Every deadline in a notice you draft, and every deadline found in a notice received, gets a row. Red output:Deadline 2 ("within 21 days"): no calendar date. Search your draft forwithin,days,weeks,months,promptly,forthwith,immediately,reasonable,on demand,by return,without delayandas soon as; each hit maps to a row or is rewritten. - Consequence table (drafting).
Stated consequence | Client confirmed they will pursue it (who, when) | Basis (lease clause quoted, or statute read this session with URL and date) | Available now? (yes, with the provisions checked, or the step that must come first). Red output:Consequence 1 ("we will forfeit the lease"): not confirmed,basis not retrieved, orAvailable now? not established. A lease clause giving the right is a basis; it does not answerAvailable now?, which needs the statutory restrictions on that step read this session. A consequence that fails any of the three is cut, not softened, and the cut is reported to the client with the cell that failed, since they asked for it. - Allegation table (replying or analysing). Count the allegations in the notice and
number them in the notice's own order.
No. | Allegation as stated | Fact: admitted / denied with the client's account / not known / admitted in part | Legal characterisation: not admitted / denied / conceded on instruction | Client's own words (source). Red output:Allegations 6 in notice, 5 answeredorAllegation 3: fact admitted, characterisation blank.
Supporting rules
- Choose the date with margin. Where a statute or lease sets a window, pick a date that is valid under any plausible counting convention and any plausible date of giving. When a posted notice counts as given depends on the lease's notice clause or the statute's service provision; read it, or treat the date as uncertain and widen the margin. State the convention you used. verified-citations owns the counting rule.
- Facts are particularised from the user, never supplied. Who, what, when, with dates and document references. No invented fact, legal basis, clause or statute. If no legal basis was given, draft on the facts and say no basis is named.
- Money is shown with its arithmetic. Principal, each charge, any interest with its rate and the clause or provision it rests on, and the sum. A figure you worked by hand, with no calculation run this session to check it, carries the word "unverified" beside it, so the client recomputes it before the notice goes out.
- Formal requirements are a verification list, not an assertion. Prescribed form, required content, method of service, minimum periods: cite what you read this session, or list it as open. Never state that a notice satisfies a statutory requirement you did not read. Open rows go above the draft, not after it, so the client sees what was not checked before the notice goes out.
- Service note on every drafted notice. How it is to be served, to which address, and what to keep as proof of the date and method.
- Global points first in a reply. A defective notice, wrong party, limitation, or a missing pre-condition can dispose of several allegations at once. State it before the allegation-by-allegation answers, as a point to raise rather than a settled defence.
- Silence is a decision. If the client wants an allegation left unanswered, flag the risk that silence may be read as acceptance and record the client's instruction.
- Analysis does not draft. In analysis mode, produce the tables, the evidence needed per allegation, the admissions to avoid, and the urgency (does any deadline need a holding reply first). Draft the reply only when asked.
Modes
| Mode | Blocking inputs | Tables required | Output adds |
| Draft a demand or notice | The facts, the exact sum or action demanded, the client's instruction on consequences, the governing law | Deadline, consequence | The notice, a service note, a verification list |
| Reply to a notice received | The notice in full, the client's position on each allegation | Deadline, allegation | Global points, numbered answers, the client's own position, reservation of rights, verification list |
| Analyse a notice received | The notice in full, which side you advise | Deadline, allegation | Evidence per allegation, admissions to avoid, procedural points to consider, recommended posture pending instructions |
Worked examples: England and Wales residential leasehold
Each provision below was read on legislation.gov.uk on 2026-10-03 (latest available revised text) unless another date is given. Several carry prospective changes; re-read before relying on any of them. They show what the tables catch; they are not advice on a file, and they are not a retrieval for one: a basis cell, or a deadline row whose period comes from a statute, needs the provision read in your session, with your own URL and date, and a line copied from here fails that table.
- Ground rent on a long lease of a dwelling. The tenant is not liable to pay unless the landlord has given a notice, and the payment date in it must be neither less than 30 days nor more than 60 days "after the day on which the notice is given", nor earlier than the date the lease itself makes it payable (CLRA 2002 s.166(1), (3)). The notice must be in the prescribed form (s.166(5)(a)); read the regulations before drafting. A posted notice goes to the dwelling unless the tenant has notified another address in England and Wales in writing (s.166(6)). "Rent" here excludes service charges and administration charges (s.166(7)). Deadline table: the start event is the day the notice is given, so the margin column matters.
- Any written demand for rent or other sums under a tenancy. It must contain the landlord's name and address, and an address in England and Wales for notices if the landlord's address is elsewhere; without that, the service-charge or administration-charge part is treated as not due until the information is given by notice (LTA 1987 s.47(1)-(2), with an exception in s.47(3) while a tribunal- or court-appointed receiver or manager collects those charges; a new s.47(3A) is prospectively inserted by the Leasehold and Freehold Reform Act 2024 s.55(4)(a)). For "premises in Wales which consist of or include a dwelling in a regulated building", a new s.47B, "Building safety information to be contained in demands for rent etc: Wales", is prospectively inserted by the Building Safety (Wales) Act 2026 s.74 (read 2026-10-04). Separately, until the landlord has given notice of an address in England and Wales for service, rent, service charges and administration charges are treated as not due (s.48(1)-(2)), again except while a court- or tribunal-appointed receiver or manager collects them (s.48(3)). Part VI applies to premises consisting of or including a dwelling, not held on a business tenancy under Part II of the Landlord and Tenant Act 1954, and not to a dwelling in Wales subject to an occupation contract (s.46(1), (1A)). Consequence table: interest or a late-payment charge running on a sum not yet due has no basis.
- A service-charge or administration-charge demand. A service-charge demand must be accompanied by the summary of tenants' rights and obligations, or the tenant may withhold and the lease's late-payment provisions do not apply for that period (LTA 1985 s.21B(1), (3)-(4); the whole section is prospectively omitted by the Leasehold and Freehold Reform Act 2024 s.55(2)(c)). An administration-charge demand needs its own summary, with the same right to withhold (CLRA 2002 Sch.11 para 4; prospectively omitted by the 2024 Act s.61(a)). Costs incurred more than 18 months before the demand is served are irrecoverable unless the tenant was notified in writing within the period in LTA 1985 s.20B(2) (see statute-to-obligations-register for that row). In draft mode each of these is a row on the verification list (supporting rule 4): read this session and checked against the demand, or marked open above the draft.
- Threatening forfeiture over service charges. For premises let as a dwelling, a landlord may not exercise a right of re-entry or forfeiture for failure to pay a service charge or administration charge unless it is finally determined by a tribunal, court or post-dispute arbitral tribunal that the amount is payable by the tenant, or the tenant has admitted that it is so payable (HA 1996 s.81(1)). "Finally determined" has its own meaning: only once the time for an appeal or other challenge has run out, or any appeal or challenge has been disposed of (s.81(3), (3A)). Even then, not "until after the end of the period of 14 days beginning with the day after that on which the final determination is made" (s.81(2)). Serving a notice under section 146(1) of the Law of Property Act 1925 counts as exercising that right (s.81(4A)). Business tenancies under Part II of the 1954 Act, agricultural holdings and farm business tenancies are outside it (s.81(4)).
- Threatening forfeiture on a long lease of a dwelling for small or recent arrears, or for
another breach. A landlord may not forfeit for unpaid rent, service charges or
administration charges (or a mix) unless the unpaid amount exceeds the prescribed sum or
includes an amount payable for more than the prescribed period; the prescribed sum may not
exceed £500, and a default charge is left out when testing the sum (not the period)
(CLRA 2002 s.167(1)-(3)). £500 is
the ceiling, not the test: the sum and period are set by regulations, which on 2026-10-04
prescribed £350 and three years in England
(SI 2004/3086 reg 2) and in
Wales (SI 2005/1352 reg 2); read
the one for the dwelling's nation (words in s.167(1) and
(5) are prospectively substituted by the Leasehold and Freehold Reform Act 2024 s.53(11)). For a breach of a
covenant or condition in the lease, no section 146 notice may be served until the breach is
finally determined or admitted, and after a determination not until the 14-day period in
s.168(3) has ended (s.168(1)-(3)).
Consequence table: a threat of forfeiture, or of a section 146 notice, not checked against
s.81, s.167 and s.168 fails
Available now? not establishedand is cut.
Do not
- Do not write a deadline as a period without its calendar date.
- Do not threaten a step the client has not confirmed, or one the law does not allow yet.
- Do not let an admission of fact carry a legal conclusion; fill both columns.
- Do not invent a fact, a defence, a clause or a statute to fill a gap in instructions.
- Do not assert that a notice meets a statutory form, content or service requirement you did not read this session.
- Do not soften a firm demand into a negotiable one, or harden it beyond instructions.
Routes and scope
- Reviewing the lease or contract the notice arises under → contract-review.
- Mapping every duty a statute imposes, as a register → statute-to-obligations-register.
- Counting a statutory period ("beginning with", "after") → verified-citations.
- Checking the citations in a notice received → legal-citation-integrity.
- The generated document's own integrity (placeholders, re-extraction) → deliverable-integrity.
- Sending the notice by email and proving delivery → email-delivery-verification.
Provenance: forked from rohasnagpal/legal-ai-skills (three upstream skills consolidated), see UPSTREAM.md.
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.

