@wonsukchoi/crondex 0.18.0 → 0.20.0

package/jobs/agriculture/field-soil-test-due-reminder.yaml

@@ -0,0 +1,35 @@
+id: field-soil-test-due-reminder
+version: 1
+name: Field Soil Test Due Reminder
+description: >
+  Checks each field's last soil test date against a retest interval and
+  flags any field that's overdue. Use this if you've ever applied
+  fertilizer off a soil test that was two years stale because nobody was
+  tracking when each field was last sampled.
+category: agriculture
+tags: [agriculture, soil, testing, fields]
+schedule: "0 7 1 * *"
+timezone: "America/Chicago"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v interval="{{retest_interval_days}}" -v today="$today" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline last_ts; close(cmd);
+      days_since = (today - last_ts) / 86400;
+      if (days_since > interval) {
+        printf "OVERDUE: %s — last tested %s (%d days ago)\n", $1, $2, days_since;
+      }
+    }
+  ' "{{fields_csv_path}}"
+variables:
+  fields_csv_path:
+    default: "./fields.csv"
+    description: "Path to a CSV with columns: field_name,last_soil_test_date (YYYY-MM-DD)."
+  retest_interval_days:
+    default: 730
+    description: Days allowed between soil tests before a field counts as overdue (default ~2 years).
+compatible_agents: [generic, claude, codex]
+notes: Keep fields.csv updated whenever a new soil sample comes back from the lab — one row per field.

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/fleet-inspection-expiry-check.yaml

@@ -0,0 +1,35 @@
+id: fleet-inspection-expiry-check
+version: 1
+name: Fleet Inspection Expiry Check
+description: >
+  Checks each fleet vehicle's state inspection or emissions sticker expiry
+  date and flags anything expiring soon. Use this if a shop or fleet
+  vehicle has ever gotten pulled over — or failed a customer handoff —
+  because its inspection quietly lapsed.
+category: automotive
+tags: [automotive, fleet, inspection, compliance]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v warn="{{warn_days}}" -v today="$today" '
+    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_ts; close(cmd);
+      days_left = (exp_ts - today) / 86400;
+      if (days_left <= warn) {
+        printf "WARNING: vehicle %s — inspection expires %s (%d days left)\n", $1, $2, days_left;
+      }
+    }
+  ' "{{fleet_csv_path}}"
+variables:
+  fleet_csv_path:
+    default: "./fleet-inspections.csv"
+    description: "Path to a CSV with columns: vehicle_id,inspection_expiry_date (YYYY-MM-DD)."
+  warn_days:
+    default: 21
+    description: Days before expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Update fleet-inspections.csv whenever a vehicle is re-inspected — one row per vehicle in the fleet.

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/childcare/classroom-supply-low-stock-check.yaml

@@ -0,0 +1,28 @@
+id: classroom-supply-low-stock-check
+version: 1
+name: Classroom Supply Low Stock Check
+description: >
+  Checks consumable classroom supplies like diapers, wipes, and formula
+  against a reorder threshold per item and flags anything running low.
+  Use this if a classroom has ever run out of diapers or wipes mid-day
+  because nobody noticed the shelf was nearly empty.
+category: childcare
+tags: [childcare, supplies, inventory, classroom]
+schedule: "0 7 * * 1,4"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' '
+    NR==1 {next}
+    {
+      if ($2+0 <= $3+0) {
+        printf "LOW STOCK: %s — %d on hand (reorder at %d)\n", $1, $2, $3;
+      }
+    }
+  ' "{{supplies_csv_path}}"
+variables:
+  supplies_csv_path:
+    default: "./classroom-supplies.csv"
+    description: "Path to a CSV with columns: item_name,current_stock,reorder_threshold."
+compatible_agents: [generic, claude, codex]
+notes: Update classroom-supplies.csv whenever a supply count is taken — one row per consumable item tracked.

package/jobs/construction/crew-safety-cert-expiry-check.yaml

@@ -0,0 +1,35 @@
+id: crew-safety-cert-expiry-check
+version: 1
+name: Crew Safety Certification Expiry Check
+description: >
+  Checks each crew member's safety certifications, like OSHA 10/30 or
+  forklift operator cards, against their expiry date and flags anyone
+  lapsing soon. Use this if a worker has ever been pulled off a site
+  because their safety card expired and nobody caught it beforehand.
+category: construction
+tags: [construction, safety, certification, crew]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v warn="{{warn_days}}" -v today="$today" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline exp_ts; close(cmd);
+      days_left = (exp_ts - today) / 86400;
+      if (days_left <= warn) {
+        printf "WARNING: %s — %s expires %s (%d days left)\n", $1, $2, $3, days_left;
+      }
+    }
+  ' "{{crew_certs_csv_path}}"
+variables:
+  crew_certs_csv_path:
+    default: "./crew-safety-certs.csv"
+    description: "Path to a CSV with columns: worker_name,cert_name,expiry_date (YYYY-MM-DD)."
+  warn_days:
+    default: 30
+    description: Days before expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Distinct from subcontractor-insurance-expiry-check — this tracks your own crew's individual safety cards, not a sub's company insurance policy.

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/affiliate-link-expiry-check.yaml

@@ -0,0 +1,35 @@
+id: affiliate-link-expiry-check
+version: 1
+name: Affiliate Link Expiry Check
+description: >
+  Checks affiliate links and discount codes in your published content
+  against their expiry date and flags anything expiring soon. Use this if
+  a viewer has ever hit a dead discount code in an old video description
+  because nobody remembered to pull or update it before it lapsed.
+category: creator
+tags: [creator, affiliate, links, monetization]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v warn="{{warn_days}}" -v today="$today" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline exp_ts; close(cmd);
+      days_left = (exp_ts - today) / 86400;
+      if (days_left <= warn) {
+        printf "WARNING: code %s (%s) expires %s (%d days left)\n", $1, $2, $3, days_left;
+      }
+    }
+  ' "{{affiliate_links_csv_path}}"
+variables:
+  affiliate_links_csv_path:
+    default: "./affiliate-links.csv"
+    description: "Path to a CSV with columns: code_or_link,associated_post,expiry_date (YYYY-MM-DD)."
+  warn_days:
+    default: 14
+    description: Days before expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Update affiliate-links.csv whenever you add a new sponsored link or code to a post — one row per tracked link.

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/nft-floor-price-watch.yaml

@@ -0,0 +1,37 @@
+id: nft-floor-price-watch
+version: 1
+name: NFT Floor Price Watch
+description: >
+  Checks an NFT collection's floor price via a public marketplace API and
+  alerts if it drops below a threshold. Use this if you've ever wanted a
+  heads-up when a collection you hold or track dips below a price level
+  you care about, without staring at a marketplace tab all day.
+category: crypto
+tags: [crypto, nft, floor-price, marketplace]
+schedule: "0 * * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  floor=$(curl -s -H "accept: application/json" "{{floor_price_api_url}}" |
+    grep -o '"floor_price":[0-9.]*' | head -1 | cut -d: -f2);
+  if [ -n "$floor" ]; then
+    echo "Floor price for {{collection_slug}}: $floor {{price_unit}}";
+    awk -v floor="$floor" -v min="{{min_floor_price}}" 'BEGIN{if (floor+0 < min+0) print "LOW FLOOR ALERT: below " min " " "{{price_unit}}" " threshold"}';
+  else
+    echo "Could not fetch floor price — check API URL/collection slug.";
+  fi
+variables:
+  floor_price_api_url:
+    default: "https://api.opensea.io/api/v2/collections/{{collection_slug}}/stats"
+    description: Marketplace API endpoint returning a floor_price field for the collection.
+  collection_slug:
+    default: "your-collection-slug"
+    description: Marketplace slug/identifier for the NFT collection to watch.
+  min_floor_price:
+    default: 0.1
+    description: Floor price threshold below which to alert.
+  price_unit:
+    default: "ETH"
+    description: Unit the floor price is denominated in, for display only.
+compatible_agents: [generic, claude, codex]
+notes: Read-only public API call — some marketplace APIs require a free API key in a header; add it via a wrapper script or an authenticated endpoint if needed.

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/coupon-code-expiry-check.yaml

@@ -0,0 +1,36 @@
+id: coupon-code-expiry-check
+version: 1
+name: Coupon Code Expiry Check
+description: >
+  Checks active promo and coupon codes against their expiry date and flags
+  any expiring soon so you can decide to extend, replace, or let them
+  lapse on purpose. Use this if a customer has ever complained a code from
+  your last campaign stopped working and nobody on the team knew it had
+  quietly expired.
+category: ecommerce
+tags: [ecommerce, coupons, promotions, marketing]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v warn="{{warn_days}}" -v today="$today" '
+    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_ts; close(cmd);
+      days_left = (exp_ts - today) / 86400;
+      if (days_left <= warn) {
+        printf "WARNING: code %s expires %s (%d days left)\n", $1, $2, days_left;
+      }
+    }
+  ' "{{coupons_csv_path}}"
+variables:
+  coupons_csv_path:
+    default: "./coupons.csv"
+    description: "Path to a CSV with columns: coupon_code,expiry_date (YYYY-MM-DD)."
+  warn_days:
+    default: 7
+    description: Days before expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Update coupons.csv whenever a new promo code is created or an existing one is deactivated — one row per active code.

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/education/tuition-payment-plan-delinquency-check.yaml

@@ -0,0 +1,35 @@
+id: tuition-payment-plan-delinquency-check
+version: 1
+name: Tuition Payment Plan Delinquency Check
+description: >
+  Checks tuition installment plans against their due dates and flags
+  accounts that have missed a payment. Use this if a family has ever
+  fallen behind on a payment plan for weeks before anyone in the office
+  noticed and followed up.
+category: education
+tags: [education, tuition, payments, billing]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v grace="{{grace_days}}" '
+    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 due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (now_epoch - due_epoch) / 86400;
+      if (diff_days >= grace) {
+        printf "DELINQUENT: %s — installment $%s due %s (%d days overdue)\n", $1, $2, $3, diff_days;
+      }
+    }
+  ' "{{payment_plans_csv_path}}"
+variables:
+  payment_plans_csv_path:
+    default: "./tuition-payment-plans.csv"
+    description: "Path to a CSV with columns: student_name,installment_amount,due_date (YYYY-MM-DD),paid (yes/no)."
+  grace_days:
+    default: 5
+    description: Days past the due date before an unpaid installment is flagged as delinquent.
+compatible_agents: [generic, claude, codex]
+notes: Mark the paid column as soon as a payment clears, or a settled installment will keep showing up as delinquent.

package/jobs/events/post-event-survey-response-rate-watch.yaml

@@ -0,0 +1,39 @@
+id: post-event-survey-response-rate-watch
+version: 1
+name: Post-Event Survey Response Rate Watch
+description: >
+  Compares how many attendees were sent a post-event survey against how
+  many actually responded, and flags events with a weak response rate.
+  Use this if you've ever sent a feedback survey after an event and had
+  no idea whether the response rate was normal or a sign nobody cared to
+  reply.
+category: events
+tags: [events, survey, feedback, response-rate]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v min_pct="{{min_response_pct}}" '
+    NR==1 {next}
+    {
+      sent[$1] += 1;
+      if ($3 == "yes") responded[$1] += 1;
+    }
+    END {
+      for (event in sent) {
+        pct = (responded[event] / sent[event]) * 100;
+        if (pct < min_pct) {
+          printf "LOW RESPONSE RATE: %s — %d of %d responded (%.0f%%)\n", event, responded[event], sent[event], pct;
+        }
+      }
+    }
+  ' "{{survey_sends_csv_path}}"
+variables:
+  survey_sends_csv_path:
+    default: "./event-survey-sends.csv"
+    description: "Path to a CSV with columns: event_name,attendee_email,responded (yes/no)."
+  min_response_pct:
+    default: 25
+    description: Minimum survey response percentage before an event is flagged as low-response.
+compatible_agents: [generic, claude, codex]
+notes: Update the responded column as replies come in — this only reads whatever the CSV currently reflects, it doesn't poll a survey tool directly.

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.