@wonsukchoi/crondex 0.19.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/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/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/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/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/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/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/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/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/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-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/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/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/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.