@wonsukchoi/crondex 0.20.1 → 0.22.0

package/jobs/publishing/royalty-statement-due-check.yaml

@@ -0,0 +1,33 @@
+id: royalty-statement-due-check
+version: 1
+name: Royalty Statement Due Check
+description: >
+  Warns you before a royalty statement and payment is due to an author or
+  co-author. Use this if a royalty statement has ever gone out late (or
+  didn't go out at all) because the payout schedule wasn't tracked anywhere.
+category: publishing
+tags: [publishing, royalties, authors, payments]
+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 \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline due_ts; close(cmd);
+      days_left = int((due_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: royalty statement for \"" $1 "\" due in " days_left " days (" $2 ")";
+    }
+  ' "{{royalty_schedule_csv}}"
+variables:
+  royalty_schedule_csv:
+    default: "./royalty-schedule.csv"
+    description: "CSV with header row, columns: author_or_title,statement_due_date(YYYY-MM-DD)."
+  warn_days:
+    default: 14
+    description: Days before a statement due date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Most contracts pay semiannually or quarterly on fixed dates — keep
+  royalty-schedule.csv in sync with each contract's payout cadence.

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.

package/jobs/realestate/tenant-renters-insurance-compliance-check.yaml

@@ -0,0 +1,35 @@
+id: tenant-renters-insurance-compliance-check
+version: 1
+name: Tenant Renters Insurance Compliance Check
+description: >
+  Checks tenants required by their lease to carry renters insurance
+  against their certificate's expiration date and flags anyone lapsed or
+  about to lapse. Use this if a tenant's coverage has ever quietly
+  expired mid-lease, leaving the landlord exposed on a liability claim
+  the lease was supposed to cover.
+category: realestate
+tags: [realestate, renters-insurance, compliance, tenant]
+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 < 0) printf "LAPSED: %s (unit %s) renters insurance expired %d day(s) ago\n", $1, $2, -days_left;
+      else if (days_left <= warn) printf "EXPIRING SOON: %s (unit %s) renters insurance expires in %d day(s)\n", $1, $2, days_left;
+    }
+  ' "{{renters_coi_csv}}"
+variables:
+  renters_coi_csv:
+    default: "./tenant-renters-insurance.csv"
+    description: "CSV with header row, columns: tenant_name,unit,coverage_expiration_date(YYYY-MM-DD)."
+  warn_days:
+    default: 14
+    description: Days before expiration to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Distinct from subcontractor-insurance-expiry-check in jobs/construction (which tracks contractor COIs on a job site) — this tracks tenant renters-insurance compliance required by the lease, only useful where the lease actually mandates coverage.

package/jobs/realestate/utility-billback-reconciliation-check.yaml

@@ -0,0 +1,41 @@
+id: utility-billback-reconciliation-check
+version: 1
+name: Utility Bill-Back Reconciliation Check
+description: >
+  Compares submetered tenant utility charges against the property's
+  master utility bill and flags a mismatch beyond a set tolerance. Use
+  this if tenant bill-backs have ever quietly drifted from the actual
+  master bill, either undercharging the owner or overcharging tenants.
+category: realestate
+tags: [realestate, utilities, billing, reconciliation]
+schedule: "0 8 3 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v tol="{{tolerance_pct}}" '
+    NR==1 {next}
+    {
+      billed_total += $3;
+      master = $2;
+      property = $1;
+    }
+    END {
+      diff = billed_total - master;
+      pct = (master > 0) ? (diff / master * 100) : 0;
+      if (pct < 0) pct = -pct;
+      if (pct >= tol) {
+        printf "RECONCILIATION MISMATCH: %s — tenant bill-backs total $%.2f vs master bill $%.2f (%.1f%% variance)\n", property, billed_total, master, pct;
+      } else {
+        printf "OK: %s bill-backs reconcile within tolerance ($%.2f vs $%.2f)\n", property, billed_total, master;
+      }
+    }
+  ' "{{billback_csv}}"
+variables:
+  billback_csv:
+    default: "./utility-billback-ledger.csv"
+    description: "CSV with header row, columns: property_name,master_bill_amount,tenant_billed_amount — one row per submetered unit for the current billing period, master_bill_amount repeated per row for the property."
+  tolerance_pct:
+    default: 5
+    description: Allowed percentage variance between total tenant bill-backs and the master bill before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a per-period export of submeter charges alongside the master bill amount — adjust the CSV shape to match your submetering vendor or utility management software's export.

package/jobs/sales/champion-departure-watch.yaml

@@ -0,0 +1,44 @@
+id: champion-departure-watch
+version: 1
+name: Champion Departure Watch
+description: >
+  Checks whether your champion or economic-buyer contact at open or
+  recently-closed accounts has left the company, using bounce signals or
+  a job-change lookup, and drafts a plan to find the new point of contact.
+  Use this if a deal has ever gone quiet for weeks before you found out
+  your one internal advocate had already left the company.
+category: sales
+tags: [sales, champion, contact-departure, account-risk]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review the champion/decision-maker contacts listed in {{contacts_source}}
+  for accounts with an open deal or a contract within
+  {{renewal_lookback_days}} days of renewal.
+  1. For each contact, check for signs they've left the company: a bounced
+     email address, an outdated title, or a job-change signal on
+     {{signal_source}} (e.g. LinkedIn).
+  2. List any contact flagged as likely departed, with the account name,
+     deal/contract at risk, and what signal triggered the flag.
+  3. For each flagged account, suggest the most likely replacement contact
+     if one is visible in the account (another named stakeholder, or a
+     generic role like "VP of [department]"), and draft a short
+     re-introduction email to that person or a warm-intro request to
+     another contact at the account.
+  4. If no departures are found, say so in one line.
+variables:
+  contacts_source:
+    default: "your CRM's contact list, or a champions.csv with columns: account,contact_name,contact_email,title,deal_or_contract"
+    description: Where champion/decision-maker contacts and the account/deal they're tied to are recorded.
+  signal_source:
+    default: "LinkedIn, or email bounce logs from your email platform"
+    description: Where to check for a job-change or departure signal.
+  renewal_lookback_days:
+    default: 90
+    description: How far ahead to include upcoming renewals when scoping which accounts' champions to check.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: >
+  Draft-only — review the suggested replacement contact and re-intro email
+  before sending. Respect LinkedIn's terms of use; a manual check or a
+  licensed data provider is safer than scraping.

package/jobs/sales/closed-lost-reason-audit.yaml

@@ -0,0 +1,42 @@
+id: closed-lost-reason-audit
+version: 1
+name: Closed-Lost Reason Audit
+description: >
+  Finds recently closed-lost deals with no loss reason recorded, and
+  summarizes the reasons that were captured into a short pattern report.
+  Use this if closed-lost deals have ever piled up with a blank reason
+  field, making it impossible to tell whether you're losing to a
+  competitor, on price, or on missing features.
+category: sales
+tags: [sales, closed-lost, win-loss, reporting]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: hybrid
+command: >
+  psql "{{database_url}}" -t -c "select name, owner, amount, loss_reason from deals where stage = 'closed_lost' and closed_at > now() - interval '{{lookback_days}} days' order by closed_at desc;"
+prompt: |
+  Review closed-lost deals from the last {{lookback_days}} days (from the
+  script output above, or by querying {{database_url}} directly).
+  1. List every deal with a blank/missing loss_reason — these need a rep
+     follow-up to fill in before the data is usable.
+  2. For deals that do have a loss_reason, group them into a short summary
+     of the top 3-5 recurring themes (e.g. "price", "lost to [competitor]",
+     "missing feature X", "no budget/timing").
+  3. Note if one theme is trending upward compared to what you'd normally
+     expect, so it can be raised with product/pricing.
+script_note: >
+  `command` lists closed-lost deals and their recorded (or missing) loss
+  reason with zero tokens. `prompt` adds the missing-reason follow-up list
+  and the qualitative theme summary across free-text reasons.
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the CRM/deals database.
+  lookback_days:
+    default: 30
+    description: How many days of closed-lost deals to review.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: >
+  Assumes a `deals` table with `stage`, `closed_at`, and a free-text
+  `loss_reason` column — adjust to your CRM's schema and loss-reason
+  taxonomy if it uses a fixed picklist instead of free text.

package/jobs/sales/commission-payout-tracker.yaml

@@ -0,0 +1,32 @@
+id: commission-payout-tracker
+version: 1
+name: Commission Payout Tracker
+description: >
+  Finds closed-won deals whose sales commission hasn't been marked as paid
+  even though the payout grace period has passed, and totals what's owed
+  per rep. Use this if a rep has ever had to chase finance to find out why
+  a commission from weeks ago never showed up in their paycheck.
+category: sales
+tags: [sales, commission, payroll-adjacent, compensation]
+schedule: "0 8 1,15 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  psql "{{database_url}}" -t -c "select owner, count(*) as unpaid_deals, sum(amount) as unpaid_revenue, round(sum(amount) * {{commission_rate_pct}} / 100.0, 2) as commission_owed from deals where stage = 'closed_won' and commission_paid = false and closed_at < now() - interval '{{grace_days}} days' group by owner order by commission_owed desc;"
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the CRM/deals database.
+  commission_rate_pct:
+    default: 10
+    description: Flat commission rate percent applied to closed-won revenue, for the estimate.
+  grace_days:
+    default: 15
+    description: Days after close before an unpaid commission counts as overdue for payout.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Assumes a `deals` table with a `commission_paid` boolean column and a
+  flat commission rate — replace the flat-rate math with your real
+  commission plan (tiers, accelerators, clawbacks) if it's more complex.
+  This is separate from any HR payroll job — it only flags CRM-side deal
+  data, it does not run payroll.