Skip to content

ThomasMoreAI/legal-skills-open / au/real-estate/skills/nsw-tenant-support-strayharp

nsw-tenant-support-strayharp

Verified

Guide renters in New South Wales, Australia through tenancy problems — repairs not being done, agent or landlord harassment, rent increases, bond disputes, termination notices, eviction threats, and NCAT or Fair Trading processes. Use this skill whenever a user mentions renting in NSW or Sydney and any dispute, notice, repair issue, or landlord/agent conflict, even if they don't name a specific law or agency. Also use it when a NSW renter asks who to call, how to complain, how to write to their agent, or what their rights are. Do not use for other Australian states, for landlords seeking advice against tenants, or for purchase/strata-owner matters.

FileKindSize
LICENSEother1.0 KB
SKILL.mdskill md9.5 KB
references/legislation.mdmarkdown13.4 KB
references/letters.mdmarkdown3.4 KB
references/resources.mdmarkdown7.2 KB

references/letters.md

View on GitHub
# Letter and email drafting patterns

## Anatomy of an effective request letter

The Tenants' Union templates (resources.md § Stage 1) all share a structure worth preserving when adapting:

1. **Subject/heading naming the property** — "Re: Repairs to [address]"
2. **Reference to the earlier request** — "As previously advised on [date]…" (establishes the pattern of inaction)
3. **Itemised defects, tradesperson-quotable** — "The tap in the bathroom needs a washer replaced", one line each. Never "the bathroom has issues". This specificity is what satisfies the s 65C(2)(b) "particulars" requirement and keeps the Fair Trading pathway open
4. **A deadline** — "within the next week" for non-urgent. A request without a deadline can't later be characterised as *refused*, and refusal-without-reasonable-excuse is the s 65C trigger
5. **The consequence** — "If not attended to by [date], I will apply to the NSW Civil and Administrative Tribunal"
6. **Practical cooperation** — contact details for arranging access (shows reasonableness)

## The confirming email (after any significant phone call)

Send same-day. Purpose: convert an unwitnessed call into evidence, and change behaviour (people speak differently once on the record).

> Confirming our call today at [time]. You stated [X and Y — near-verbatim for anything threatening or legally wrong]. I do not accept that characterisation / that is not correct under the Residential Tenancies Act. Going forward, please put all communication in writing to this address.

State facts about the user's own experience ("we found the manner and content of the call distressing") — unfalsifiable — rather than characterisations the other side will dispute ("you threatened us"). Name both co-tenants.

## Responding to an incorrect assertion from an agent

Three-variant pattern; offer the choice and explain the trade-off:

- **Hold the line (minimal):** state the correct legal position with the section, confirm the operative date/position stands, request written-only contact. Preserves maximum flexibility; creates no new commitments.
- **Put the conduct on record (default for conduct issues):** the above, plus a factual contemporaneous record of the calls/incidents and their effect. Without this, raising the conduct months later at NCAT invites "why didn't you say anything at the time?"
- **Full position:** the above, plus the complete legal argument with sections. Use only when the position is settled and advice has been taken — committing early to a framing means being stuck with it.

General rules: short, factual, no rhetoric; one clearly wrong assertion corrected beats five arguments advanced; never mention deadlines that help the other side (if their window to challenge has lapsed, silence; if it hasn't, don't remind them); avoid overstatement that invites easy rebuttal.

## Evidence pack (assemble alongside any letter)

- Emails exported to PDF **with headers**, stored off-platform
- File notes of calls: date, time, participants, duration, near-verbatim content — written same day
- Ingoing condition report + lease (proves inclusions)
- A one-page timeline: date → event → evidence pointer. This is the single most useful document for a TAAS call, a Fair Trading complaint, and an NCAT application alike — offer to build it from the user's account
- At move-out: photographs matched against the ingoing report; tenant initiates the bond claim
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 196kUpdated Claude CodeCodexVerifiedInstall