@wonsukchoi/crondex 0.18.0 → 0.19.0

package/jobs/agriculture/grain-storage-temperature-check.yaml

@@ -0,0 +1,34 @@
+id: grain-storage-temperature-check
+version: 1
+name: Grain Storage Temperature Check
+description: >
+  Checks logged grain bin temperature and moisture readings against safe
+  storage thresholds and flags any bin trending toward spoilage. Use this
+  if you've ever caught hot spots or mold in stored grain only after the
+  smell gave it away.
+category: agriculture
+tags: [agriculture, grain, storage, spoilage]
+schedule: "0 6 * * *"
+timezone: "America/Chicago"
+runner: shell
+command: >
+  awk -F',' -v maxtemp="{{max_temp_f}}" -v maxmoist="{{max_moisture_pct}}" '
+    NR==1 {next}
+    {
+      if ($2+0 > maxtemp+0 || $3+0 > maxmoist+0) {
+        printf "ALERT: bin %s — %.1f°F, %.1f%% moisture (limits %s°F / %s%%)\n", $1, $2, $3, maxtemp, maxmoist;
+      }
+    }
+  ' "{{bin_readings_csv_path}}"
+variables:
+  bin_readings_csv_path:
+    default: "./grain-bin-readings.csv"
+    description: "Path to a CSV with columns: bin_id,temperature_f,moisture_pct."
+  max_temp_f:
+    default: 70
+    description: Temperature (F) above which a bin is flagged as a spoilage risk.
+  max_moisture_pct:
+    default: 15
+    description: Moisture percentage above which a bin is flagged as a spoilage risk.
+compatible_agents: [generic, claude, codex]
+notes: Reads whatever your bin sensor system exports to CSV — point bin_readings_csv_path at that export. Safe thresholds vary by grain type; adjust the defaults accordingly.

package/jobs/automotive/warranty-claim-deadline-check.yaml

@@ -0,0 +1,35 @@
+id: warranty-claim-deadline-check
+version: 1
+name: Warranty Claim Deadline Check
+description: >
+  Checks open warranty claims against the manufacturer's submission
+  deadline and flags any about to expire unfiled. Use this if a claim has
+  ever gone unpaid because it was submitted a day past the manufacturer's
+  filing window.
+category: automotive
+tags: [automotive, warranty, claims, deadline]
+schedule: "0 8 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v warn="{{warn_days_before}}" '
+    NR==1 {next}
+    $4 == "open" {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline deadline_epoch; close(cmd);
+      days_left = (deadline_epoch - today) / 86400;
+      if (days_left <= warn) {
+        printf "DEADLINE: claim %s for RO %s — due %s (%d days left)\n", $1, $2, $3, days_left;
+      }
+    }
+  ' "{{warranty_claims_csv_path}}"
+variables:
+  warranty_claims_csv_path:
+    default: "./warranty-claims.csv"
+    description: "Path to a CSV with columns: claim_id,ro_number,filing_deadline (YYYY-MM-DD),status (open/submitted)."
+  warn_days_before:
+    default: 5
+    description: Days before the filing deadline to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Filing deadlines vary by manufacturer — keep warranty-claims.csv current from your DMS/warranty system export.

package/jobs/childcare/allergy-action-plan-expiry-check.yaml

@@ -0,0 +1,34 @@
+id: allergy-action-plan-expiry-check
+version: 1
+name: Allergy Action Plan Expiry Check
+description: >
+  Checks each child's allergy action plan against its annual renewal date
+  and warns before it lapses. Use this if a plan has ever gone stale
+  without anyone noticing until an incident made it obvious.
+category: childcare
+tags: [childcare, allergy, health, compliance]
+schedule: "0 8 * * 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 expiry_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (expiry_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "EXPIRING: %s — allergy action plan expires %s (%d days)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{allergy_plans_csv_path}}"
+variables:
+  allergy_plans_csv_path:
+    default: "./allergy-action-plans.csv"
+    description: "Path to a CSV with columns: child_name,plan_expiry_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 30
+    description: How many days before a plan expires to start warning.
+compatible_agents: [generic, claude, codex]
+notes: A lapsed plan means staff no longer have a current, doctor-signed protocol on file — treat this as a same-week fix, not a queue item.

package/jobs/construction/material-delivery-delay-check.yaml

@@ -0,0 +1,32 @@
+id: material-delivery-delay-check
+version: 1
+name: Material Delivery Delay Check
+description: >
+  Checks ordered construction materials against their expected delivery
+  date and flags anything overdue from the supplier. Use this if a crew
+  has ever stood idle on site because a material delivery was quietly
+  late and nobody chased it up.
+category: construction
+tags: [construction, materials, delivery, supplier]
+schedule: "0 7 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" '
+    NR==1 {next}
+    $4 == "pending" {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline expected_epoch; close(cmd);
+      if (today > expected_epoch) {
+        overdue_days = (today - expected_epoch) / 86400;
+        printf "OVERDUE: %s for job %s — expected %s (%d days late)\n", $1, $2, $3, overdue_days;
+      }
+    }
+  ' "{{material_orders_csv_path}}"
+variables:
+  material_orders_csv_path:
+    default: "./material-orders.csv"
+    description: "Path to a CSV with columns: material_name,job_site,expected_delivery_date (YYYY-MM-DD),status (pending/delivered)."
+compatible_agents: [generic, claude, codex]
+notes: Follow up directly with the supplier once flagged overdue — this job only surfaces the gap, it doesn't contact anyone.

package/jobs/creator/brand-deal-payment-followup-check.yaml

@@ -0,0 +1,32 @@
+id: brand-deal-payment-followup-check
+version: 1
+name: Brand Deal Payment Followup Check
+description: >
+  Checks sponsor invoices against their agreed payment due date and flags
+  anything overdue and unpaid. Use this if a sponsor has ever gone quiet
+  on an invoice and you only noticed the payment never showed up weeks
+  later.
+category: creator
+tags: [creator, sponsorship, invoicing, payment]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" '
+    NR==1 {next}
+    $4 == "unpaid" {
+      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);
+      if (today > due_epoch) {
+        overdue_days = (today - due_epoch) / 86400;
+        printf "OVERDUE: invoice %s to %s — due %s (%d days late)\n", $1, $2, $3, overdue_days;
+      }
+    }
+  ' "{{sponsor_invoices_csv_path}}"
+variables:
+  sponsor_invoices_csv_path:
+    default: "./sponsor-invoices.csv"
+    description: "Path to a CSV with columns: invoice_id,sponsor_name,due_date (YYYY-MM-DD),status (unpaid/paid)."
+compatible_agents: [generic, claude, codex]
+notes: Send the actual follow-up email yourself once flagged — this job only surfaces which invoices are overdue.

package/jobs/crypto/stablecoin-peg-deviation-watch.yaml

@@ -0,0 +1,33 @@
+id: stablecoin-peg-deviation-watch
+version: 1
+name: Stablecoin Peg Deviation Watch
+description: >
+  Checks a stablecoin's market price against its $1 peg and alerts when it
+  drifts beyond your threshold. Use this if you've ever held a "stable"
+  balance through a depeg event because nothing was watching the price.
+category: crypto
+tags: [crypto, stablecoin, peg, price]
+schedule: "*/30 * * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  price=$(curl -s "https://api.coingecko.com/api/v3/simple/price?ids={{coingecko_id}}&vs_currencies=usd" |
+    grep -o '"usd":[0-9.]*' | grep -o '[0-9.]*$');
+  if [ -n "$price" ]; then
+    awk -v p="$price" -v dev="{{deviation_pct}}" 'BEGIN{
+      diff = (p-1)*100; if (diff < 0) diff = -diff;
+      printf "Current price: $%.4f\n", p;
+      if (diff >= dev+0) printf "DEPEG ALERT: %.2f%% off $1 peg\n", diff;
+    }';
+  else
+    echo "Could not fetch price — check coingecko_id.";
+  fi
+variables:
+  coingecko_id:
+    default: "usd-coin"
+    description: CoinGecko API id for the stablecoin to track (e.g. "usd-coin", "tether").
+  deviation_pct:
+    default: 1
+    description: Percentage deviation from the $1 peg that triggers an alert.
+compatible_agents: [generic, claude, codex]
+notes: Uses CoinGecko's free public API — no key required, but rate limits apply if you increase the schedule frequency.

package/jobs/ecommerce/shipping-delay-check.yaml

@@ -0,0 +1,31 @@
+id: shipping-delay-check
+version: 1
+name: Shipping Delay Check
+description: >
+  Checks shipped orders against their expected delivery date and flags
+  anything running late. Use this if a customer has ever emailed asking
+  "where's my order" before you had any idea it was already late.
+category: ecommerce
+tags: [ecommerce, shipping, fulfillment, delivery]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" '
+    NR==1 {next}
+    $4 == "in_transit" {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline expected_epoch; close(cmd);
+      if (today > expected_epoch) {
+        overdue_days = (today - expected_epoch) / 86400;
+        printf "LATE: order %s — expected %s (%d days late), tracking %s\n", $1, $3, overdue_days, $2;
+      }
+    }
+  ' "{{shipments_csv_path}}"
+variables:
+  shipments_csv_path:
+    default: "./shipments.csv"
+    description: "Path to a CSV with columns: order_id,tracking_number,expected_delivery_date (YYYY-MM-DD),status (in_transit/delivered)."
+compatible_agents: [generic, claude, codex]
+notes: Reads whatever your fulfillment platform exports to CSV — point shipments_csv_path at that export.

package/jobs/education/overdue-library-materials-check.yaml

@@ -0,0 +1,34 @@
+id: overdue-library-materials-check
+version: 1
+name: Overdue Library Materials Check
+description: >
+  Scans checked-out library items and flags anything past its due date by
+  more than a grace period. Use this if overdue textbooks or library books
+  have ever piled up unnoticed until inventory time.
+category: education
+tags: [education, library, overdue]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v graceDays="{{grace_days}}" '
+    NR==1 {next}
+    $3 == "no" {
+      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 = (now_epoch - due_epoch) / 86400;
+      if (diff_days >= graceDays) {
+        printf "OVERDUE: %s — due %s (%d days overdue)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{checkouts_csv_path}}"
+variables:
+  checkouts_csv_path:
+    default: "./library-checkouts.csv"
+    description: "Path to a CSV with columns: item_title,due_date (YYYY-MM-DD),returned (yes/no)."
+  grace_days:
+    default: 3
+    description: Days past the due date before an item is flagged as overdue.
+compatible_agents: [generic, claude, codex]
+notes: Update the returned column as soon as items come back, or every returned item will keep showing up as overdue.

package/jobs/events/speaker-confirmation-deadline-check.yaml

@@ -0,0 +1,35 @@
+id: speaker-confirmation-deadline-check
+version: 1
+name: Speaker Confirmation Deadline Check
+description: >
+  Checks the speaker/presenter list against each person's confirm-by date
+  and flags anyone who hasn't confirmed yet. Use this if an event has ever
+  gotten close with a session slot still unconfirmed and nobody noticed
+  until the program had to go to print.
+category: events
+tags: [events, speakers, confirmation]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    $3 == "no" {
+      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 "UNCONFIRMED: %s — confirm by %s (%d days)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{speakers_csv_path}}"
+variables:
+  speakers_csv_path:
+    default: "./event-speakers.csv"
+    description: "Path to a CSV with columns: speaker_name,confirm_by_date (YYYY-MM-DD),confirmed (yes/no)."
+  warn_days_before:
+    default: 7
+    description: How many days before the confirm-by date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Chase unconfirmed speakers early — an empty session slot is much harder to fill a few days out than a few weeks out.

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/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/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/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/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/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.