@wonsukchoi/crondex 0.18.0 → 0.20.0

package/jobs/fitness/class-waitlist-overflow-check.yaml

@@ -0,0 +1,31 @@
+id: class-waitlist-overflow-check
+version: 1
+name: Class Waitlist Overflow Check
+description: >
+  Checks upcoming classes for waitlists that have grown past a threshold,
+  a sign there's enough demand to justify adding another session. Use
+  this if a popular class has ever kept a long waitlist for months
+  without anyone noticing there was room to add a second time slot.
+category: fitness
+tags: [fitness, classes, waitlist, demand]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v min_wait="{{min_waitlist_size}}" '
+    NR==1 {next}
+    {
+      if ($3 >= min_wait) {
+        printf "WAITLIST OVERFLOW: %s on %s — %d people waiting\n", $1, $4, $3;
+      }
+    }
+  ' "{{classes_csv_path}}"
+variables:
+  classes_csv_path:
+    default: "./upcoming-classes.csv"
+    description: "Path to a CSV with columns: class_name,capacity,waitlist_count,class_date."
+  min_waitlist_size:
+    default: 5
+    description: Minimum number of people on a waitlist before the class is flagged as overflowing.
+compatible_agents: [generic, claude, codex]
+notes: A class that overflows the same slot week after week is a stronger signal to add a session than a single busy day.

package/jobs/fitness/locker-rental-expiry-check.yaml

@@ -0,0 +1,35 @@
+id: locker-rental-expiry-check
+version: 1
+name: Locker Rental Expiry Check
+description: >
+  Checks rented lockers against their expiry date and flags the ones
+  coming due soon. Use this if a member's belongings have ever been
+  cleared out of a locker without warning because the rental quietly
+  lapsed.
+category: fitness
+tags: [fitness, lockers, membership]
+schedule: "0 6 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (due_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "LOCKER EXPIRING: %s (locker %s) — expires %s (%d days)\n", $1, $2, $3, diff_days;
+      }
+    }
+  ' "{{lockers_csv_path}}"
+variables:
+  lockers_csv_path:
+    default: "./locker-rentals.csv"
+    description: "Path to a CSV with columns: member_name,locker_number,expiry_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 7
+    description: How many days before expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Give members a heads-up before clearing out an expired locker — a courtesy notice avoids losing personal items to a lapsed rental.

package/jobs/fleet/fleet-insurance-expiry-check.yaml

@@ -0,0 +1,34 @@
+id: fleet-insurance-expiry-check
+version: 1
+name: Fleet Insurance Policy Expiry Check
+description: >
+  Checks each vehicle's insurance policy against its expiry date and flags
+  coverage that's about to lapse. Use this if a vehicle has ever been
+  driven on an expired policy because renewal paperwork got missed.
+category: fleet
+tags: [fleet, insurance, compliance]
+schedule: "0 7 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (due_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "POLICY EXPIRING: vehicle %s, policy %s — expires %s (%d days)\n", $1, $2, $3, diff_days;
+      }
+    }
+  ' "{{policies_csv_path}}"
+variables:
+  policies_csv_path:
+    default: "./fleet-insurance-policies.csv"
+    description: "Path to a CSV with columns: vehicle_id,policy_number,expiry_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 14
+    description: How many days before expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Driving an uninsured vehicle is a legal and financial liability — treat a flag here as urgent, not routine.

package/jobs/fleet/vehicle-idle-time-check.yaml

@@ -0,0 +1,31 @@
+id: vehicle-idle-time-check
+version: 1
+name: Vehicle Idle Time Check
+description: >
+  Checks each vehicle's daily engine idle time against a threshold and
+  flags the ones burning excess fuel sitting still. Use this if a
+  telematics report has ever shown a surprise fuel bill and nobody could
+  tell how much of it came from vehicles just left running.
+category: fleet
+tags: [fleet, fuel, idling, telematics]
+schedule: "0 7 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v max_min="{{max_idle_minutes}}" '
+    NR==1 {next}
+    {
+      if ($3 > max_min) {
+        printf "EXCESS IDLE: vehicle %s on %s — %d idle minutes (limit %d)\n", $1, $2, $3, max_min;
+      }
+    }
+  ' "{{idle_report_csv_path}}"
+variables:
+  idle_report_csv_path:
+    default: "./vehicle-idle-report.csv"
+    description: "Path to a daily telematics export CSV with columns: vehicle_id,report_date (YYYY-MM-DD),idle_minutes."
+  max_idle_minutes:
+    default: 60
+    description: Maximum idle minutes per day before a vehicle is flagged for excess idling.
+compatible_agents: [generic, claude, codex]
+notes: Requires a telematics/GPS provider that exports a daily idle-minutes-per-vehicle report to CSV; format varies by provider so you may need to reshape the export first.

package/jobs/gaming/game-server-disk-space-check.yaml

@@ -0,0 +1,34 @@
+id: game-server-disk-space-check
+version: 1
+name: Game Server Disk Space Check
+description: >
+  Checks free disk space on your self-hosted game server's world/save
+  data volume and warns before it fills up. Use this if a server has
+  ever stopped saving the world (or crashed outright) because the disk
+  quietly filled up overnight.
+category: gaming
+tags: [gaming, server, disk-space, hosting]
+schedule: "*/30 * * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  usage=$(df -P "{{server_data_path}}" 2>/dev/null | awk 'NR==2 {gsub("%","",$5); print $5}');
+  if [ -z "$usage" ]; then
+    echo "ERROR: could not read disk usage for {{server_data_path}}";
+    exit 1;
+  fi;
+  if [ "$usage" -ge "{{warn_pct}}" ]; then
+    echo "WARNING: disk usage at ${usage}% for {{server_data_path}} — world saves may fail soon";
+    exit 1;
+  else
+    echo "OK: disk usage at ${usage}% for {{server_data_path}}";
+  fi
+variables:
+  server_data_path:
+    default: "/srv/gameserver"
+    description: Path to the game server's world/save data directory (or its mount point).
+  warn_pct:
+    default: 85
+    description: Disk usage percent that triggers a warning.
+compatible_agents: [generic, claude, codex]
+notes: Run this on the same host as the game server (or via an ssh wrapper) — it reads local disk usage with `df`, not a remote API.

package/jobs/gaming/player-contract-renewal-check.yaml

@@ -0,0 +1,35 @@
+id: player-contract-renewal-check
+version: 1
+name: Esports Player Contract Renewal Check
+description: >
+  Warns you before a roster player's or staff member's contract expires.
+  Use this if a player has ever gone unsigned mid-season because a
+  contract end date slipped past without anyone flagging it in time to
+  negotiate a renewal.
+category: gaming
+tags: [gaming, esports, roster, contracts]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline exp_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (exp_epoch - now_epoch) / 86400;
+      if (diff_days <= days && diff_days >= 0) {
+        printf "CONTRACT EXPIRING: %s (%s) — expires %s (%d days)\n", $1, $3, $2, diff_days;
+      }
+    }
+  ' "{{roster_contracts_csv_path}}"
+variables:
+  roster_contracts_csv_path:
+    default: "./roster-contracts.csv"
+    description: "Path to a CSV with columns: person_name,contract_end_date (YYYY-MM-DD),role."
+  warn_days_before:
+    default: 30
+    description: How many days before contract expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Start renewal talks well before the warning window closes — a starting player benched by an expired contract is a roster gap, not just paperwork.

package/jobs/government/public-comment-period-closing-check.yaml

@@ -0,0 +1,35 @@
+id: public-comment-period-closing-check
+version: 1
+name: Public Comment Period Closing Check
+description: >
+  Checks open public comment periods for pending rules or proposals
+  against their close date and flags the ones closing soon. Use this if
+  a comment period has ever expired with barely any public input logged
+  because nobody was tracking the closing date.
+category: government
+tags: [government, public-comment, compliance, deadline]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    $3 == "open" {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (due_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "COMMENT PERIOD CLOSING: %s — closes %s (%d days)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{comment_periods_csv_path}}"
+variables:
+  comment_periods_csv_path:
+    default: "./public-comment-periods.csv"
+    description: "Path to a CSV with columns: proposal_name,close_date (YYYY-MM-DD),status (open/closed)."
+  warn_days_before:
+    default: 7
+    description: How many days before the close date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: This tracks comment windows on proposals/rules specifically — for meeting notice timing use public-meeting-notice-compliance-check instead.

package/jobs/government/public-records-retention-purge-check.yaml

@@ -0,0 +1,32 @@
+id: public-records-retention-purge-check
+version: 1
+name: Public Records Retention Purge Check
+description: >
+  Checks records against their retention schedule and flags anything past
+  its retention period as eligible for archival review or purge. Use this
+  if a records room has ever quietly kept documents years past their
+  legally required retention window simply because nobody was tracking
+  expiry dates.
+category: government
+tags: [government, records, retention, compliance]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" '
+    NR==1 {next}
+    $4 == "no" {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline exp_epoch; close(cmd);
+      if (today >= exp_epoch) {
+        printf "RETENTION EXPIRED: %s (%s) — retention ended %s\n", $1, $2, $3;
+      }
+    }
+  ' "{{records_csv_path}}"
+variables:
+  records_csv_path:
+    default: "./records-retention-schedule.csv"
+    description: "Path to a CSV with columns: record_id,record_type,retention_end_date (YYYY-MM-DD),reviewed (yes/no)."
+compatible_agents: [generic, claude, codex]
+notes: This flags records as eligible for review, not for automatic deletion — always confirm against your jurisdiction's retention schedule and any legal hold before purging anything.

package/jobs/growth/onboarding-completion-stall-check.yaml

@@ -0,0 +1,38 @@
+id: onboarding-completion-stall-check
+version: 1
+name: Onboarding Completion Stall Check
+description: >
+  Checks new users against your onboarding checklist and flags anyone
+  who's been stuck on the same step for too long. Use this if new users
+  have ever quietly abandoned setup partway through and nobody reached
+  out until they'd already churned.
+category: growth
+tags: [growth, onboarding, activation, retention]
+schedule: "0 10 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v stall_days="{{stall_days}}" -v last_step="{{final_step}}" '
+    NR==1 {next}
+    $2 != last_step {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline step_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (now_epoch - step_epoch) / 86400;
+      if (diff_days >= stall_days) {
+        printf "STALLED: %s — stuck on \"%s\" for %d day(s)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{onboarding_status_csv_path}}"
+variables:
+  onboarding_status_csv_path:
+    default: "./onboarding-status.csv"
+    description: "Path to a CSV with columns: user_email,current_step,step_reached_date (YYYY-MM-DD)."
+  final_step:
+    default: "complete"
+    description: The value in current_step that marks onboarding as finished (users at this step are never flagged).
+  stall_days:
+    default: 3
+    description: Days a user can sit on the same non-final step before being flagged as stalled.
+compatible_agents: [generic, claude, codex]
+notes: You maintain onboarding-status.csv yourself (update current_step and step_reached_date as your product tracks progress) — doesn't integrate with any analytics platform directly.

package/jobs/growth/seat-utilization-upsell-check.yaml

@@ -0,0 +1,34 @@
+id: seat-utilization-upsell-check
+version: 1
+name: Seat Utilization Upsell Check
+description: >
+  Flags accounts that are using most or all of their purchased seats, a
+  strong signal they're about to hit a limit. Use this if you've ever
+  found out an account outgrew its plan only after they complained about
+  being locked out of adding a new user.
+category: growth
+tags: [growth, upsell, seats, expansion]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v threshold="{{utilization_threshold_pct}}" '
+    NR==1 {next}
+    {
+      if ($2 > 0) {
+        pct = ($3 / $2) * 100;
+        if (pct >= threshold) {
+          printf "UPSELL OPPORTUNITY: %s — %d/%d seats used (%.0f%%)\n", $1, $3, $2, pct;
+        }
+      }
+    }
+  ' "{{accounts_csv_path}}"
+variables:
+  accounts_csv_path:
+    default: "./account-seats.csv"
+    description: "Path to a CSV with columns: account_name,seats_purchased,seats_used."
+  utilization_threshold_pct:
+    default: 90
+    description: Seat utilization percent that flags an account as an upsell opportunity.
+compatible_agents: [generic, claude, codex]
+notes: High seat utilization is a strong signal to reach out about expanding the plan before the account hits a hard limit.

package/jobs/healthcare/medical-equipment-calibration-check.yaml

@@ -0,0 +1,35 @@
+id: medical-equipment-calibration-check
+version: 1
+name: Medical Equipment Calibration Check
+description: >
+  Checks a tracked list of medical equipment (blood pressure cuffs,
+  glucometers, defibrillators, scales) against calibration due dates and
+  warns before any lapse. Use this if a piece of equipment has ever been
+  found overdue for calibration only when an inspector or auditor flagged it.
+category: healthcare
+tags: [compliance, equipment, calibration, healthcare]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (due_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "CALIBRATION DUE: %s (%s) — due %s (%d days)\n", $1, $2, $3, diff_days;
+      }
+    }
+  ' "{{equipment_csv_path}}"
+variables:
+  equipment_csv_path:
+    default: "./equipment-calibration.csv"
+    description: "Path to a CSV of tracked equipment with columns: equipment_name,equipment_id,calibration_due_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 30
+    description: How many days before the calibration due date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a maintained CSV export from your biomedical equipment tracking system, updated whenever a unit is calibrated or newly deployed.

package/jobs/healthcare/referral-pending-followup-check.yaml

@@ -0,0 +1,36 @@
+id: referral-pending-followup-check
+version: 1
+name: Pending Referral Follow-up Check
+description: >
+  Checks outbound specialist referrals that haven't been scheduled or
+  completed within a set window and flags them for follow-up. Use this
+  if a patient has ever fallen through the cracks after being referred
+  out, with nobody confirming they actually got the appointment.
+category: healthcare
+tags: [referrals, follow-up, care-coordination, compliance]
+schedule: "0 8 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v days="{{stale_days}}" '
+    NR==1 {next}
+    $4 != "" {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline sent_epoch; close(cmd);
+      pending_days = (today - sent_epoch) / 86400;
+      if (pending_days >= days) {
+        printf "STALE REFERRAL: %s -> %s sent %s (%d days pending, no scheduled date)\n", $1, $2, $3, pending_days;
+      }
+    }
+  ' "{{referrals_csv_path}}"
+variables:
+  referrals_csv_path:
+    default: "./referrals.csv"
+    description: "Path to a CSV with columns: patient_name,specialist_name,referral_sent_date (YYYY-MM-DD),scheduled_date (blank if not yet scheduled)."
+  stale_days:
+    default: 14
+    description: Days since a referral was sent, with no scheduled date, before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a maintained CSV export of outbound referrals from your EHR or referral-tracking system; adjust columns to match your export.

package/jobs/hiring/job-posting-expiry-check.yaml

@@ -0,0 +1,41 @@
+id: job-posting-expiry-check
+version: 1
+name: Job Posting Expiry Check
+description: >
+  Checks open job postings against their planned expiry or repost date and
+  flags any that have gone stale on a job board. Use this if a posting has
+  ever sat expired for weeks before anyone noticed applications had quietly
+  stopped coming in.
+category: hiring
+tags: [hiring, recruiting, job-postings]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v stale="{{stale_days}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $4 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $4 "\" +%s 2>/dev/null";
+      cmd | getline expiry_epoch; close(cmd);
+      if (expiry_epoch != "" && expiry_epoch <= today) {
+        printf "EXPIRED: %s on %s — expired %s\n", $1, $2, $4;
+        next;
+      }
+      cmd2 = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd2 | getline posted_epoch; close(cmd2);
+      posted_days = (today - posted_epoch) / 86400;
+      if (posted_days >= stale) {
+        printf "STALE: %s on %s — posted %d days ago (%s)\n", $1, $2, posted_days, $3;
+      }
+    }
+  ' "{{postings_csv_path}}"
+variables:
+  postings_csv_path:
+    default: "./job-postings.csv"
+    description: "Path to a CSV of active postings with columns: posting_title,job_board,posted_date,expiry_date (YYYY-MM-DD, expiry_date may be blank)."
+  stale_days:
+    default: 30
+    description: Days since posting before a posting with no expiry date is flagged as stale.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a CSV export of active postings from your ATS or job board account; re-posting requirements vary by board (LinkedIn, Indeed) so confirm before reposting.

package/jobs/hiring/reference-check-overdue-reminder.yaml

@@ -0,0 +1,36 @@
+id: reference-check-overdue-reminder
+version: 1
+name: Reference Check Overdue Reminder
+description: >
+  Checks candidates whose reference checks were requested but never came
+  back within a set window and flags them so recruiters can chase them
+  down. Use this if an offer has ever stalled because a reference check
+  quietly sat unanswered for weeks.
+category: hiring
+tags: [hiring, recruiting, references, follow-up]
+schedule: "0 9 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v days="{{overdue_days}}" '
+    NR==1 {next}
+    $4 != "" {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline requested_epoch; close(cmd);
+      pending_days = (today - requested_epoch) / 86400;
+      if (pending_days >= days) {
+        printf "OVERDUE: %s — reference from %s requested %s (%d days, no response)\n", $1, $2, $3, pending_days;
+      }
+    }
+  ' "{{reference_checks_csv_path}}"
+variables:
+  reference_checks_csv_path:
+    default: "./reference-checks.csv"
+    description: "Path to a CSV with columns: candidate_name,referrer_name,requested_date (YYYY-MM-DD),completed_date (blank if not yet received)."
+  overdue_days:
+    default: 7
+    description: Days since a reference check was requested, with no completion date, before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a CSV export of reference-check requests from your ATS; distinct from background-check-status-check, which tracks third-party background screening rather than personal/professional references.

package/jobs/home/gutter-cleaning-reminder.yaml

@@ -0,0 +1,30 @@
+id: gutter-cleaning-reminder
+version: 1
+name: Gutter Cleaning Reminder
+description: >
+  Reminds you to clean out your gutters based on how long it's been
+  since the last cleaning. Use this if you've ever noticed water
+  overflowing or plants sprouting in your gutters because it had been
+  way longer than you thought.
+category: home
+tags: [home, maintenance, gutters, seasonal]
+schedule: "0 9 1 * *"
+timezone: "America/Los_Angeles"
+runner: shell
+command: >
+  last={{last_cleaned_date}}; interval={{interval_months}};
+  last_epoch=$(date -j -f %Y-%m-%d "$last" +%s 2>/dev/null || date -d "$last" +%s);
+  today_epoch=$(date +%s);
+  days_since=$(( (today_epoch-last_epoch)/86400 ));
+  interval_days=$(( interval * 30 ));
+  if [ "$days_since" -ge "$interval_days" ]; then echo "REMINDER: gutters last cleaned $days_since day(s) ago (every ${interval} months) — clean them.";
+  else echo "OK: gutters cleaned $days_since day(s) ago, due again around day $interval_days."; fi
+variables:
+  last_cleaned_date:
+    default: "2026-01-01"
+    description: Date (YYYY-MM-DD) you last cleaned the gutters — update this yourself.
+  interval_months:
+    default: 6
+    description: How often to clean the gutters, in months.
+compatible_agents: [generic, claude, codex]
+notes: Zero-token. You update last_cleaned_date yourself each time you actually clean them; adjust interval_months if you have heavy tree cover.

package/jobs/home/utility-bill-anomaly-check.yaml

@@ -0,0 +1,36 @@
+id: utility-bill-anomaly-check
+version: 1
+name: Utility Bill Anomaly Check
+description: >
+  Compares each newly logged utility bill against your recent average for
+  that utility and flags a reading that spikes well beyond normal. Use this
+  if a bill has ever jumped because of a hidden leak or a device left
+  running, and you only found out once the bill arrived.
+category: home
+tags: [home, utilities, budgeting, anomaly]
+schedule: "0 9 5 * *"
+timezone: "America/Los_Angeles"
+runner: shell
+command: >
+  awk -F',' -v threshold="{{spike_threshold_pct}}" '
+    NR==1 {next}
+    { util=$2; amt=$3+0; count[util]++; sum[util]+=amt; last[util]=amt; lastdate[util]=$1; }
+    END {
+      for (u in count) {
+        if (count[u] < 2) continue;
+        avg = (sum[u] - last[u]) / (count[u] - 1);
+        if (avg > 0 && last[u] >= avg * (1 + threshold / 100)) {
+          printf "SPIKE: %s bill on %s was %.2f, vs recent average %.2f\n", u, lastdate[u], last[u], avg;
+        }
+      }
+    }
+  ' "{{utility_bills_csv}}"
+variables:
+  utility_bills_csv:
+    default: "utility-bills.csv"
+    description: "CSV with header row, columns: date(YYYY-MM-DD),utility,amount. Rows must be in chronological order per utility."
+  spike_threshold_pct:
+    default: 25
+    description: Percent above the recent average that counts as a spike.
+compatible_agents: [generic, claude, codex]
+notes: Add a row to utility-bills.csv each time a bill arrives; needs at least a few months of history per utility before the average is meaningful.

package/jobs/hospitality/housekeeping-turnover-time-check.yaml

@@ -0,0 +1,41 @@
+id: housekeeping-turnover-time-check
+version: 1
+name: Housekeeping Turnover Time Check
+description: >
+  Checks logged checkout and room-ready timestamps and flags any room whose
+  turnover took longer than your target window, or is still missing a
+  ready time. Use this if a room has ever still been mid-clean when the
+  next guest arrived because nobody was tracking turnover times.
+category: hospitality
+tags: [hospitality, housekeeping, operations]
+schedule: "0 */2 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  now=$(date +%s);
+  awk -F',' -v now="$now" -v max="{{max_turnover_minutes}}" '
+    NR==1 {next}
+    {
+      room=$1; checkout=$2; ready=$3;
+      cmd = "date -d \"" checkout "\" +%s 2>/dev/null || date -j -f \"%Y-%m-%d %H:%M\" \"" checkout "\" +%s 2>/dev/null";
+      cmd | getline checkout_epoch; close(cmd);
+      if (ready == "") {
+        elapsed = (now - checkout_epoch) / 60;
+        if (elapsed >= max) printf "OVERDUE: room %s checked out %s, still not marked ready (%d min)\n", room, checkout, elapsed;
+        next;
+      }
+      cmd2 = "date -d \"" ready "\" +%s 2>/dev/null || date -j -f \"%Y-%m-%d %H:%M\" \"" ready "\" +%s 2>/dev/null";
+      cmd2 | getline ready_epoch; close(cmd2);
+      turnover = (ready_epoch - checkout_epoch) / 60;
+      if (turnover > max) printf "SLOW TURNOVER: room %s took %d min (checkout %s, ready %s)\n", room, turnover, checkout, ready;
+    }
+  ' "{{turnover_log_csv}}"
+variables:
+  turnover_log_csv:
+    default: "turnover-log.csv"
+    description: "CSV with header row, columns: room_number,checkout_time,ready_time (YYYY-MM-DD HH:MM, ready_time blank if not yet marked ready)."
+  max_turnover_minutes:
+    default: 45
+    description: Target minutes from checkout to room-ready before a room is flagged.
+compatible_agents: [generic, claude, codex]
+notes: Assumes housekeeping logs checkout_time and ready_time per room to a shared CSV or PMS export throughout the day.

package/jobs/hospitality/lost-and-found-item-aging-check.yaml

@@ -0,0 +1,36 @@
+id: lost-and-found-item-aging-check
+version: 1
+name: Lost and Found Item Aging Check
+description: >
+  Checks logged lost-and-found items against your retention policy and
+  flags any that are old enough to donate, discard, or ship back to a
+  guest. Use this if a lost-and-found closet has ever turned into a pile
+  nobody knows what to do with because items just sat there indefinitely.
+category: hospitality
+tags: [hospitality, lost-and-found, guest-services, compliance]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v days="{{retention_days}}" '
+    NR==1 {next}
+    $4 != "" {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline found_epoch; close(cmd);
+      age_days = (today - found_epoch) / 86400;
+      if (age_days >= days) {
+        printf "AGED OUT: %s (room %s) found %s (%d days, unclaimed) — dispose or donate per policy\n", $1, $2, $3, age_days;
+      }
+    }
+  ' "{{lost_found_csv_path}}"
+variables:
+  lost_found_csv_path:
+    default: "./lost-and-found.csv"
+    description: "Path to a CSV with columns: item_description,room_or_area,found_date (YYYY-MM-DD),claimed_date (blank if still unclaimed)."
+  retention_days:
+    default: 90
+    description: Days an item can sit unclaimed before it's flagged as past your retention policy.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a maintained CSV log of found items from front desk/housekeeping; check local law on retention periods for items of value (cash, electronics, IDs) before disposing.