landlord-tenant-ops
Generate a landlord-tenant notice timeline template (pay-or-quit, cure-or-quit, no-cause) for a named state, with [X DAYS — VERIFY] placeholders instead of day counts — the tool never asserts a notice period as universal. Practice-management tooling, not legal advice.
$ skillbank install landlord-tenant-ops@1.0.0 # pins exactly 1.0.0 · README + changelog included
Landlord-Tenant Ops
Overview
Practice-management tooling, not legal advice. Verify all deadlines, fees, and procedures against your jurisdiction's current rules.
Notice periods, accepted service methods, required notice content, and filing fees vary by state, by tenancy type, and over time — a template that bakes in "3 days" or "30 days" as universal is a malpractice-shaped object. This skill generates a step-by-step notice timeline template (draft → serve → wait → next step) where every day count is a [X DAYS — VERIFY] placeholder and every section carries an explicit **VERIFY YOUR STATE'S CURRENT NOTICE PERIODS** warning. It never asserts a specific day count as universal. Fill in each placeholder from the state's current statutes before use. All data stays local — nothing is uploaded.
Installation
1. Copy the landlord-tenant-ops/ directory anywhere convenient. 2. Make the script executable (Unix):
chmod +x scripts/notice.py
No pip install needed — standard library only (Python 3.9+).
Configuration
No config files. The state name you pass is used for labeling only — the script applies no state-specific rules.
Inputs
| Command / flag | Arguments | Returns | |---|---|---| | notice.py --type <type> --state "Name" [--out timeline.md] | --type: pay-or-quit, cure-or-quit, or no-cause; --state: state name (labeling only) | Timeline template with VERIFY warnings throughout and [X DAYS — VERIFY] placeholders |
An unknown notice type or empty state name produces a clear stderr message and a nonzero exit — never a traceback.
Worked example
Practice-management tooling, not legal advice. Verify all deadlines, fees, and procedures against your jurisdiction's current rules.
Pay-or-quit notice, Pennsylvania (state used for labeling only — no Pennsylvania-specific periods are asserted):
$ ./scripts/notice.py --type pay-or-quit --state "Pennsylvania" --out /tmp/notice-pq.md
wrote pay-or-quit timeline template -> /tmp/notice-pq.md
No-cause termination, Texas:
$ ./scripts/notice.py --type no-cause --state "Texas" --out /tmp/notice-nc.md
wrote no-cause timeline template -> /tmp/notice-nc.md
Every section of the output looks like this — steps, then the warning, with day counts left as placeholders for you to fill in:
## Step 4: Wait out the cure period
The tenant has [X DAYS — VERIFY] to pay in full. Calendar the
deadline; note how your state counts days (calendar vs
business days, and whether day 0 counts).
**VERIFY YOUR STATE'S CURRENT NOTICE PERIODS**
The template ends with a final checklist (notice period counted per current state rules, service method accepted, proof of service kept, filing fee and court confirmed, no retaliation / fair-housing exposure) and a closing reminder that no day counts were asserted — every placeholder must be filled from the state's current statutes before use.
Version history
Changelog
1.0.0 — 2026-09-27
- Initial release: scripts/notice.py — notice timeline templates (pay-or-quit, cure-or-quit, no-cause) with [X DAYS — VERIFY] placeholders; no universal day counts asserted.