@wonsukchoi/crondex 0.21.0 → 0.22.0

package/jobs/legal/non-compete-expiry-tracker.yaml

@@ -0,0 +1,37 @@
+id: non-compete-expiry-tracker
+version: 1
+name: Non-Compete / Non-Solicit Expiry Tracker
+description: >
+  Tracks the restricted-period end date of non-compete and non-solicit
+  agreements for departed employees and warns as each one is about to
+  expire. Use this if you've ever needed to know exactly when a former
+  employee's restrictive covenant runs out — before deciding whether to
+  act on a suspected violation, or before it's too late to.
+category: legal
+tags: [legal, non-compete, non-solicit, restrictive-covenants, employment]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v warn={{warn_days}} '
+    NR>1 {
+      cmd="date -d \"" $3 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $3 "\" +%s";
+      cmd | getline exp_ts; close(cmd);
+      days_left = int((exp_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: " $2 " covenant for " $1 " expires in " days_left " days (" $3 ")";
+    }
+  ' {{covenants_csv}}
+variables:
+  covenants_csv:
+    default: "non-compete-covenants.csv"
+    description: "CSV with header row, columns: former_employee_name,covenant_type (non-compete/non-solicit),restricted_period_end_date(YYYY-MM-DD)."
+  warn_days:
+    default: 30
+    description: Days before the restricted period ends to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Enforceability of these covenants varies a lot by state/country and has
+  been narrowing in many jurisdictions — confirm with counsel before
+  relying on any covenant as still enforceable. Update the CSV whenever
+  an employee with a covenant departs.

package/jobs/legal/outside-counsel-invoice-budget-check.yaml

@@ -0,0 +1,37 @@
+id: outside-counsel-invoice-budget-check
+version: 1
+name: Outside Counsel Invoice Budget Check
+description: >
+  Compares outside counsel invoices billed to date against each matter's
+  approved budget and flags matters approaching or over budget. Use this
+  if a matter budget has ever been blown through silently because
+  invoices got approved one at a time without anyone tracking the
+  running total against the budget set at intake.
+category: legal
+tags: [legal, outside-counsel, billing, budget]
+schedule: "0 9 1,15 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v warn_pct="{{warn_at_percent}}" '
+    NR==1 {next}
+    {
+      budget = $3 + 0;
+      billed = $4 + 0;
+      if (budget > 0) {
+        pct = (billed / budget) * 100;
+        if (pct >= warn_pct) {
+          printf "BUDGET ALERT: %s (firm: %s) — billed $%.2f of $%.2f budget (%.0f%%)\n", $1, $2, billed, budget, pct;
+        }
+      }
+    }
+  ' "{{matter_budgets_csv_path}}"
+variables:
+  matter_budgets_csv_path:
+    default: "./outside-counsel-matter-budgets.csv"
+    description: "Path to a CSV with columns: matter_name,firm_name,approved_budget,billed_to_date. One row per matter with active outside counsel."
+  warn_at_percent:
+    default: 80
+    description: Percent of approved budget billed at which a matter gets flagged.
+compatible_agents: [generic, claude, codex]
+notes: Update billed_to_date from approved invoices (e.g. e-billing/LEDES exports) before each run — this only compares numbers you supply, it doesn't parse invoices itself.

package/jobs/legal/settlement-payment-schedule-tracker.yaml

@@ -0,0 +1,34 @@
+id: settlement-payment-schedule-tracker
+version: 1
+name: Settlement Payment Schedule Tracker
+description: >
+  Checks scheduled settlement agreement installment payments — both
+  owed and owed to you — and flags anything due soon or missed. Use this
+  if a settlement installment has ever been paid late (risking default
+  terms kicking back in) or received late without anyone noticing until
+  the next reconciliation.
+category: legal
+tags: [legal, settlement, payment-schedule, litigation]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v warn={{warn_days}} '
+    NR>1 && $5 == "unpaid" {
+      cmd="date -d \"" $4 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $4 "\" +%s";
+      cmd | getline due_ts; close(cmd);
+      days_left = int((due_ts - today) / 86400);
+      if (days_left < 0) print "MISSED: " $1 " installment #" $2 " ($" $3 ") was due " $4 " (" (days_left*-1) " days overdue)";
+      else if (days_left <= warn) print "DUE SOON: " $1 " installment #" $2 " ($" $3 ") due " $4 " (" days_left " days)";
+    }
+  ' {{settlements_csv}}
+variables:
+  settlements_csv:
+    default: "settlement-payment-schedule.csv"
+    description: "CSV with header row, columns: matter_or_counterparty,installment_number,amount,due_date(YYYY-MM-DD),status(paid/unpaid)."
+  warn_days:
+    default: 7
+    description: Days before an installment's due date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Update the status column as each installment clears — this only reads dates and status you supply, it doesn't confirm receipt/disbursement of funds itself.

package/jobs/legal/timekeeper-billable-hours-compliance-check.yaml

@@ -0,0 +1,39 @@
+id: timekeeper-billable-hours-compliance-check
+version: 1
+name: Timekeeper Billable Hours Compliance Check
+description: >
+  Checks attorneys and paralegals against their weekly timesheet
+  submission and minimum billable-hour targets, and flags anyone missing
+  or short. Use this if unbilled time has ever quietly leaked out of a
+  matter because a timekeeper fell behind on entering hours and nobody
+  caught it before the billing cycle closed.
+category: legal
+tags: [legal, timekeeping, billable-hours, compliance]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v target="{{min_weekly_hours}}" '
+    NR==1 {next}
+    {
+      hours = $3 + 0;
+      if ($3 == "" ) {
+        printf "MISSING TIMESHEET: %s — week of %s not submitted\n", $1, $2;
+      } else if (hours < target) {
+        printf "SHORT OF TARGET: %s — week of %s logged %.1f hrs (target %s)\n", $1, $2, hours, target;
+      }
+    }
+  ' "{{timesheets_csv_path}}"
+variables:
+  timesheets_csv_path:
+    default: "./timekeeper-hours.csv"
+    description: "Path to a CSV with columns: timekeeper_name,week_start_date (YYYY-MM-DD),billable_hours_logged (blank if not yet submitted). One row per timekeeper per week."
+  min_weekly_hours:
+    default: 30
+    description: Minimum billable hours expected per timekeeper per week before flagging a shortfall.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Distinct from any HR timesheet/payroll job — this checks billable-hour
+  compliance for legal timekeepers against matter-billing targets, not
+  hourly payroll attendance. Export the CSV from your time & billing
+  system before each run.

package/jobs/legal/trademark-infringement-watch.yaml

@@ -0,0 +1,43 @@
+id: trademark-infringement-watch
+version: 1
+name: Trademark Infringement Watch
+description: >
+  Searches for new trademark applications, domain registrations, and
+  marketplace listings that look like they could infringe on your
+  registered marks, and summarizes anything worth a closer look. Use
+  this if you've ever found out about a confusingly similar competitor
+  mark or copycat domain months after it started causing customer
+  confusion, instead of when it first appeared.
+category: legal
+tags: [legal, trademark, ip, infringement-watch]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check for potential infringement of these registered marks:
+  {{marks_to_watch}} (owned in classes/goods: {{goods_or_classes}}).
+  1. Search recent trademark application filings (e.g. via the relevant
+     trademark office's public search/TESS-style database) for new marks
+     confusingly similar in name or logo, filed in overlapping
+     goods/services classes.
+  2. Search for newly registered domain names that are close
+     misspellings or lookalikes of {{marks_to_watch}}.
+  3. Spot-check major marketplaces/app stores for listings using the mark
+     or a confusing variant without authorization.
+  4. For each hit, summarize: what was found, how similar it is, and
+     whether it looks like routine noise or worth flagging to counsel.
+  5. This is a monitoring aid, not legal advice on whether infringement
+     exists — say so, and recommend counsel review anything flagged.
+variables:
+  marks_to_watch:
+    default: "list your registered trademark(s) here"
+    description: The registered mark(s)/brand name(s) to watch for lookalikes.
+  goods_or_classes:
+    default: "your registered goods/services classes"
+    description: The goods/services or trademark classes your registration covers, to judge overlap.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: >
+  Distinct from `trademark-renewal-reminder`, which tracks renewing your
+  own registration — this watches for others potentially infringing it.
+  Search coverage depends on what databases/tools the agent can actually
+  reach; a paid watch service will catch more than open search alone.

package/jobs/legal/vendor-coi-expiry-tracker.yaml

@@ -0,0 +1,37 @@
+id: vendor-coi-expiry-tracker
+version: 1
+name: Vendor Certificate of Insurance Expiry Tracker
+description: >
+  Checks certificates of insurance you've collected from vendors and
+  contractors and warns before any expire, so a lapsed COI doesn't sit
+  unnoticed in the file. Use this if a vendor's insurance has ever lapsed
+  mid-contract and nobody found out until a claim needed it.
+category: legal
+tags: [legal, vendor-management, coi, contractor-compliance]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" -v warn={{warn_days}} '
+    NR>1 {
+      cmd="date -d \"" $3 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $3 "\" +%s";
+      cmd | getline exp_ts; close(cmd);
+      days_left = int((exp_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: COI for \"" $1 "\" (" $2 ") expires in " days_left " days (" $3 ")";
+    }
+  ' {{vendor_cois_csv}}
+variables:
+  vendor_cois_csv:
+    default: "vendor-certificates-of-insurance.csv"
+    description: "CSV with header row, columns: vendor_name,coverage_type (e.g. general-liability, workers-comp),expiry_date(YYYY-MM-DD)."
+  warn_days:
+    default: 30
+    description: Days before a vendor's COI expires to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Opposite direction from insurance's `certificate-of-insurance-request-check`
+  (which tracks fulfilling requests for your own COI) — this tracks
+  certificates other parties gave you, as a contract-compliance/vendor-risk
+  check rather than an insurance-desk workflow. Update the CSV whenever a
+  vendor sends a new or renewed COI.

package/jobs/realestate/capital-reserve-fund-threshold-check.yaml

@@ -0,0 +1,32 @@
+id: capital-reserve-fund-threshold-check
+version: 1
+name: Capital Reserve Fund Threshold Check
+description: >
+  Compares each property's or HOA's capital reserve fund balance against
+  its target minimum and flags any that have dropped below threshold.
+  Use this if a roof or elevator replacement has ever turned into a
+  surprise special assessment because nobody was watching the reserve
+  balance drift down over time.
+category: realestate
+tags: [realestate, reserve-fund, capex, budgeting]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' '
+    NR==1 {next}
+    {
+      pct_of_target = ($3 > 0) ? ($2 / $3 * 100) : 0;
+      if ($2 < $3) {
+        printf "BELOW TARGET: %s reserve fund $%.2f is %.1f%% of target $%.2f (short $%.2f)\n", $1, $2, pct_of_target, $3, $3 - $2;
+      } else {
+        printf "OK: %s reserve fund $%.2f meets target $%.2f\n", $1, $2, $3;
+      }
+    }
+  ' "{{reserve_fund_csv}}"
+variables:
+  reserve_fund_csv:
+    default: "./capital-reserve-fund.csv"
+    description: "CSV with header row, columns: property_name,current_balance,target_balance."
+compatible_agents: [generic, claude, codex]
+notes: Target balance should come from a reserve study or capital plan, not a guess — update target_balance when major capital items age closer to replacement.

package/jobs/realestate/eviction-notice-deadline-tracker.yaml

@@ -0,0 +1,37 @@
+id: eviction-notice-deadline-tracker
+version: 1
+name: Eviction / Notice-to-Quit Deadline Tracker
+description: >
+  Tracks active notice-to-quit and eviction filings against their next
+  legal deadline (cure period expiry, court date, response window) and
+  flags anything coming up. Use this if a case has ever stalled or been
+  dismissed on a technicality because a filing or hearing deadline was
+  missed.
+category: realestate
+tags: [realestate, eviction, legal, deadline, compliance]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v warn="{{warn_days}}" '
+    NR==1 {next}
+    $4 == "open" {
+      cmd="date -d \"" $3 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $3 "\" +%s";
+      cmd | getline deadline_ts; close(cmd);
+      days_left = int((deadline_ts - today) / 86400);
+      if (days_left <= warn) {
+        status = (days_left < 0) ? "PAST DEADLINE" : "DEADLINE APPROACHING";
+        printf "%s: unit %s — %s deadline %s (%d day(s))\n", status, $1, $2, $3, days_left;
+      }
+    }
+  ' "{{eviction_cases_csv}}"
+variables:
+  eviction_cases_csv:
+    default: "./eviction-case-tracker.csv"
+    description: "CSV with header row, columns: unit,next_deadline_type(cure_period/response_window/court_date),next_deadline_date(YYYY-MM-DD),case_status(open/closed)."
+  warn_days:
+    default: 5
+    description: Days before an upcoming legal deadline to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Eviction procedure and timelines are highly jurisdiction-specific and often require an attorney — this only tracks dates you've already entered, it does not calculate legal deadlines for you.

package/jobs/realestate/landlord-insurance-claim-status-check.yaml

@@ -0,0 +1,35 @@
+id: landlord-insurance-claim-status-check
+version: 1
+name: Landlord Insurance Claim Status Check
+description: >
+  Tracks open property insurance claims and flags any that haven't had a
+  status update within a set number of days. Use this if a claim has ever
+  gone quiet for weeks with the adjuster because nobody was following up
+  on where it stood.
+category: realestate
+tags: [realestate, insurance, claims, follow-up]
+schedule: "0 8 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v stale="{{stale_days}}" '
+    NR==1 {next}
+    $5 == "open" {
+      cmd="date -d \"" $4 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $4 "\" +%s";
+      cmd | getline update_ts; close(cmd);
+      days_stale = int((today - update_ts) / 86400);
+      if (days_stale >= stale) {
+        printf "CLAIM NEEDS FOLLOW-UP: %s — claim #%s (%s), last update %d day(s) ago\n", $1, $2, $3, days_stale;
+      }
+    }
+  ' "{{insurance_claims_csv}}"
+variables:
+  insurance_claims_csv:
+    default: "./insurance-claims-tracker.csv"
+    description: "CSV with header row, columns: property_name,claim_number,claim_type,last_update_date(YYYY-MM-DD),status(open/closed)."
+  stale_days:
+    default: 14
+    description: Days without a status update before an open claim is flagged for follow-up.
+compatible_agents: [generic, claude, codex]
+notes: Distinct from insurance-policy-renewal-reminder, which only watches policy renewal dates — this tracks the lifecycle of active claims after a loss, from filing to settlement.

package/jobs/realestate/lease-renewal-offer-window-check.yaml

@@ -0,0 +1,35 @@
+id: lease-renewal-offer-window-check
+version: 1
+name: Lease Renewal Offer Window Check
+description: >
+  Flags leases approaching expiry where no renewal offer has been sent
+  yet, so tenants get a decision window before they start apartment
+  hunting elsewhere. Use this if a good tenant has ever given notice to
+  leave simply because nobody proactively offered them a renewal in time.
+category: realestate
+tags: [realestate, lease-renewal, retention]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v lead="{{offer_lead_days}}" '
+    NR==1 {next}
+    $3 == "no" {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline end_ts; close(cmd);
+      days_left = int((end_ts - today) / 86400);
+      if (days_left <= lead && days_left >= 0) {
+        printf "SEND RENEWAL OFFER: %s (unit %s) lease ends in %d day(s), no offer sent yet\n", $1, $4, days_left;
+      }
+    }
+  ' "{{leases_csv}}"
+variables:
+  leases_csv:
+    default: "./lease-renewal-status.csv"
+    description: "CSV with header row, columns: tenant_name,lease_end_date(YYYY-MM-DD),renewal_offer_sent(yes/no),unit."
+  offer_lead_days:
+    default: 90
+    description: Days before lease end by which a renewal offer should have been sent.
+compatible_agents: [generic, claude, codex]
+notes: Distinct from lease-expiry-reminder, which just warns that an end date is approaching — this tracks whether the renewal-offer action itself has been taken, flip renewal_offer_sent to "yes" once the offer goes out.

package/jobs/realestate/maintenance-request-sla-check.yaml

@@ -0,0 +1,39 @@
+id: maintenance-request-sla-check
+version: 1
+name: Maintenance Request SLA Check
+description: >
+  Scans open tenant maintenance requests and flags any that have blown
+  past your response or resolution SLA. Use this if a leaky faucet or
+  broken heater has ever sat unaddressed for weeks because the request
+  got logged and then forgotten.
+category: realestate
+tags: [realestate, maintenance, sla, tenant-requests]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v sla_normal="{{sla_hours_normal}}" -v sla_urgent="{{sla_hours_urgent}}" '
+    NR==1 {next}
+    $4 == "open" {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d %H:%M\" \"" $2 "\" +%s";
+      cmd | getline opened_ts; close(cmd);
+      hours_open = (today - opened_ts) / 3600;
+      sla = ($3 == "urgent") ? sla_urgent : sla_normal;
+      if (hours_open >= sla) {
+        printf "SLA BREACH: unit %s — \"%s\" open %.0f hrs (priority: %s, SLA: %s hrs)\n", $1, $5, hours_open, $3, sla;
+      }
+    }
+  ' "{{maintenance_requests_csv}}"
+variables:
+  maintenance_requests_csv:
+    default: "./maintenance-requests.csv"
+    description: "CSV with header row, columns: unit,opened_at(YYYY-MM-DD HH:MM),priority(normal/urgent),status(open/closed),description."
+  sla_hours_normal:
+    default: 72
+    description: Hours allowed to resolve a normal-priority request before it counts as an SLA breach.
+  sla_hours_urgent:
+    default: 12
+    description: Hours allowed to resolve an urgent-priority request (e.g. no heat, active leak) before it counts as an SLA breach.
+compatible_agents: [generic, claude, codex]
+notes: Distinct from the routine walkthrough tracked by property-maintenance-inspection-reminder — this watches tenant-initiated repair tickets against a response/resolution clock, not scheduled inspections.

package/jobs/realestate/move-in-move-out-inspection-tracker.yaml

@@ -0,0 +1,35 @@
+id: move-in-move-out-inspection-tracker
+version: 1
+name: Move-In/Move-Out Inspection Checklist Tracker
+description: >
+  Flags move-ins and move-outs where the condition inspection checklist
+  hasn't been completed within a set number of days of the move date. Use
+  this if a deposit dispute has ever fallen apart because there was no
+  signed move-in or move-out condition report to point to.
+category: realestate
+tags: [realestate, inspection, move-in, move-out, documentation]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v grace="{{grace_days}}" '
+    NR==1 {next}
+    $4 == "incomplete" {
+      cmd="date -d \"" $3 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $3 "\" +%s";
+      cmd | getline move_ts; close(cmd);
+      days_since = int((today - move_ts) / 86400);
+      if (days_since >= grace) {
+        printf "MISSING CHECKLIST: %s unit %s — %s inspection incomplete, %d day(s) since move date %s\n", $1, $2, $5, days_since, $3;
+      }
+    }
+  ' "{{inspections_csv}}"
+variables:
+  inspections_csv:
+    default: "./move-inspection-tracker.csv"
+    description: "CSV with header row, columns: tenant_name,unit,move_date(YYYY-MM-DD),checklist_status(complete/incomplete),move_type(move_in/move_out)."
+  grace_days:
+    default: 3
+    description: Days after the move date before an incomplete checklist gets flagged.
+compatible_agents: [generic, claude, codex]
+notes: A completed, signed checklist with photos is usually the single biggest factor in winning a security deposit dispute — mark checklist_status complete only once it's actually signed and filed.

package/jobs/realestate/rent-increase-notice-deadline-check.yaml

@@ -0,0 +1,54 @@
+id: rent-increase-notice-deadline-check
+version: 1
+name: Rent Increase Notice Deadline Check
+description: >
+  Checks upcoming lease anniversaries against the legally required notice
+  period for a rent increase, and drafts the increase notice once one is
+  due. Use this if you've ever missed the window to raise rent at renewal
+  because the required notice lead time (30/60/90 days, depending on
+  jurisdiction) quietly passed.
+category: realestate
+tags: [realestate, rent, rent-increase, notice, compliance]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: hybrid
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v lead="{{notice_lead_days}}" '
+    NR==1 {next}
+    {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline anniv_ts; close(cmd);
+      days_out = int((anniv_ts - today) / 86400);
+      notice_deadline_days = days_out - lead;
+      if (days_out >= 0 && notice_deadline_days <= 7) {
+        printf "NOTICE DUE SOON: %s renews %s — send rent increase notice within %d day(s) to meet the %d-day requirement\n", $1, $2, lead, notice_deadline_days;
+      }
+    }
+  ' "{{leases_csv}}"
+prompt: >
+  A property manager needs rent increase notices drafted for leases flagged
+  by the attached check as needing notice within the next 7 days. For each
+  flagged tenant/unit, draft a short, compliant rent increase notice letter
+  stating the current rent, new rent (using {{increase_pct}}% as the default
+  increase unless a specific figure is provided), effective date, and the
+  jurisdiction's required minimum notice period ({{notice_lead_days}} days).
+  Keep tone professional and neutral, and flag if the requested effective
+  date does not leave the full required notice period.
+script_note: >
+  The shell command flags which leases need a notice sent this week using
+  static date math; it does not draft the actual notice letter or account
+  for jurisdiction-specific required legal language, both of which the
+  prompt pass adds.
+variables:
+  leases_csv:
+    default: "./lease-anniversaries.csv"
+    description: "CSV with header row, columns: tenant_name,anniversary_date(YYYY-MM-DD)."
+  notice_lead_days:
+    default: 60
+    description: Minimum days of advance notice required before a rent increase takes effect (check local law).
+  increase_pct:
+    default: 3
+    description: Default percentage rent increase to propose when drafting a notice.
+compatible_agents: [claude, codex, generic]
+notes: Required notice periods vary widely by state/city and by increase size — verify local rules before sending; this job does not know your jurisdiction's specific statute.

package/jobs/realestate/rent-roll-vacancy-loss-report.yaml

@@ -0,0 +1,32 @@
+id: rent-roll-vacancy-loss-report
+version: 1
+name: Rent Roll Vacancy Loss Report
+description: >
+  Rolls up the whole portfolio's rent ledger to calculate total dollar
+  vacancy loss (market rent for every vacant unit, summed) for the
+  period. Use this if you've ever known "a few units are empty" without
+  knowing what that's actually costing you in dollars this month.
+category: realestate
+tags: [realestate, vacancy, rent-roll, reporting]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' '
+    NR==1 {next}
+    {
+      total_units++;
+      total_market_rent += $3;
+      if ($4 == "vacant") { vacant_units++; vacancy_loss += $3; }
+    }
+    END {
+      vacancy_rate = (total_units > 0) ? (vacant_units / total_units * 100) : 0;
+      printf "VACANCY LOSS REPORT: %d of %d unit(s) vacant (%.1f%%), lost market rent = $%.2f of $%.2f total portfolio potential\n", vacant_units, total_units, vacancy_rate, vacancy_loss, total_market_rent;
+    }
+  ' "{{rent_roll_csv}}"
+variables:
+  rent_roll_csv:
+    default: "./rent-roll.csv"
+    description: "CSV with header row, columns: unit,tenant_name,market_rent,occupancy_status(occupied/vacant)."
+compatible_agents: [generic, claude, codex]
+notes: Distinct from rental-vacancy-check, which watches a single listing's days-vacant clock — this rolls up the whole rent roll into a dollar vacancy-loss figure for the period, useful for owner reporting.

package/jobs/realestate/rental-license-renewal-check.yaml

@@ -0,0 +1,35 @@
+id: rental-license-renewal-check
+version: 1
+name: Rental License / Registration Renewal Check
+description: >
+  Warns before a municipal rental license, landlord registration, or
+  certificate of occupancy for rental use is due to expire. Use this if
+  a city has ever fined you, or blocked a new lease, because a rental
+  registration lapsed and nobody was tracking its renewal cycle.
+category: realestate
+tags: [realestate, rental-license, municipal, compliance]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v warn="{{warn_days}}" '
+    NR==1 {next}
+    {
+      cmd="date -d \"" $3 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $3 "\" +%s";
+      cmd | getline exp_ts; close(cmd);
+      days_left = int((exp_ts - today) / 86400);
+      if (days_left <= warn) {
+        printf "LICENSE RENEWAL DUE: %s — %s license (#%s) expires in %d day(s)\n", $1, $2, $4, days_left;
+      }
+    }
+  ' "{{rental_licenses_csv}}"
+variables:
+  rental_licenses_csv:
+    default: "./rental-licenses.csv"
+    description: "CSV with header row, columns: property_name,license_type,expiration_date(YYYY-MM-DD),license_number."
+  warn_days:
+    default: 45
+    description: Days before expiration to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Distinct from property-maintenance-inspection-reminder (routine walkthroughs) and construction/permit-expiry-check (building permits during construction) — this tracks the ongoing municipal license/registration a unit needs to be legally rented, not a build-phase permit.

package/jobs/realestate/security-deposit-return-deadline-check.yaml

@@ -0,0 +1,38 @@
+id: security-deposit-return-deadline-check
+version: 1
+name: Security Deposit Return Deadline Check
+description: >
+  Flags move-outs where the statutory deadline to return the security
+  deposit (or an itemized deduction statement) is approaching or has
+  passed. Use this if a deposit has ever gone back late and triggered a
+  penalty claim or small-claims dispute because nobody was tracking the
+  move-out date against the legal return window.
+category: realestate
+tags: [realestate, security-deposit, move-out, compliance]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v deadline_days="{{return_deadline_days}}" '
+    NR==1 {next}
+    {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline moveout_ts; close(cmd);
+      days_since = int((today - moveout_ts) / 86400);
+      days_left = deadline_days - days_since;
+      if ($3 == "not_returned") {
+        if (days_left < 0) printf "OVERDUE: %s deposit is %d day(s) past the %d-day return deadline (moved out %s)\n", $1, -days_left, deadline_days, $2;
+        else if (days_left <= 5) printf "DUE SOON: %s deposit return/itemization due within %d day(s) (moved out %s)\n", $1, days_left, $2;
+      }
+    }
+  ' "{{moveouts_csv}}"
+variables:
+  moveouts_csv:
+    default: "./security-deposit-tracker.csv"
+    description: "CSV with header row, columns: tenant_name,moveout_date(YYYY-MM-DD),status(returned/not_returned)."
+  return_deadline_days:
+    default: 21
+    description: Statutory number of days to return the deposit or send an itemized deduction statement (varies by state, commonly 14-30).
+compatible_agents: [generic, claude, codex]
+notes: Update status to "returned" the moment a deposit is sent back or an itemized statement is mailed — the statutory deadline and whether interest is owed vary by jurisdiction, so confirm your local rule.

package/jobs/realestate/tenant-application-review-backlog-check.yaml

@@ -0,0 +1,35 @@
+id: tenant-application-review-backlog-check
+version: 1
+name: Tenant Application Review Backlog Check
+description: >
+  Flags rental applications that have been sitting in review too long
+  without a decision. Use this if a good applicant has ever gone with a
+  different landlord because your screening process sat on their
+  application for a week before anyone looked at it.
+category: realestate
+tags: [realestate, tenant-screening, applications, backlog]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v max_days="{{max_review_days}}" '
+    NR==1 {next}
+    $3 == "pending" {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline sub_ts; close(cmd);
+      days_pending = int((today - sub_ts) / 86400);
+      if (days_pending >= max_days) {
+        printf "STALE APPLICATION: %s applied for unit %s %d day(s) ago, still pending review\n", $1, $4, days_pending;
+      }
+    }
+  ' "{{applications_csv}}"
+variables:
+  applications_csv:
+    default: "./tenant-applications.csv"
+    description: "CSV with header row, columns: applicant_name,submitted_date(YYYY-MM-DD),status(pending/approved/denied),unit."
+  max_review_days:
+    default: 3
+    description: Days an application can sit pending before it's flagged as backlogged.
+compatible_agents: [generic, claude, codex]
+notes: Keep status updated to approved/denied as decisions are made so this only ever flags genuinely stalled applications, not ones already actioned.