@wonsukchoi/crondex 0.7.0 → 0.8.0

package/jobs/fleet/vehicle-registration-expiry-check.yaml

@@ -0,0 +1,31 @@
+id: vehicle-registration-expiry-check
+version: 1
+name: Fleet Vehicle Registration Expiry Check
+description: >
+  Warns you before a fleet vehicle's registration expires. Use this if a
+  vehicle has ever gotten pulled over, or failed a job site check-in,
+  because its registration quietly lapsed.
+category: fleet
+tags: [fleet, registration, compliance]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" -v warn={{warn_days}} '
+    NR>1 {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline exp_ts; close(cmd);
+      days_left = int((exp_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: vehicle " $1 " registration expires in " days_left " days (" $2 ")";
+    }
+  ' {{fleet_registration_csv}}
+variables:
+  fleet_registration_csv:
+    default: "fleet-registration.csv"
+    description: "CSV with header row, columns: vehicle_id,registration_expiry(YYYY-MM-DD)."
+  warn_days:
+    default: 30
+    description: Days before expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Keep fleet-registration.csv updated after each renewal — one row per vehicle.

package/jobs/hiring/offer-expiry-reminder.yaml

@@ -0,0 +1,31 @@
+id: offer-expiry-reminder
+version: 1
+name: Offer Expiry Reminder
+description: >
+  Flags extended offers that are close to their response deadline with no
+  answer yet. Use this if an offer has ever quietly expired because
+  nobody followed up before the deadline passed.
+category: hiring
+tags: [hiring, offers, recruiting]
+schedule: "0 9 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" -v warn={{warn_days}} '
+    NR>1 && $3 == "pending" {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline exp_ts; close(cmd);
+      days_left = int((exp_ts - today) / 86400);
+      if (days_left <= warn && days_left >= 0) print "WARNING: offer to " $1 " expires in " days_left " days (" $2 "), no response yet";
+    }
+  ' {{offers_csv}}
+variables:
+  offers_csv:
+    default: "offers.csv"
+    description: "CSV with header row, columns: candidate_name,expiry_date(YYYY-MM-DD),status(pending/accepted/declined)."
+  warn_days:
+    default: 2
+    description: Days before offer expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Keep offers.csv updated as offers go out and candidates respond — one row per open offer.

package/jobs/hospitality/health-inspection-due-reminder.yaml

@@ -0,0 +1,32 @@
+id: health-inspection-due-reminder
+version: 1
+name: Health Inspection Due Reminder
+description: >
+  Warns you before a health department inspection is expected, based on
+  your jurisdiction's typical interval. Use this if an inspector has ever
+  shown up to a kitchen that wasn't ready because nobody was tracking when
+  the last one happened.
+category: hospitality
+tags: [hospitality, health-inspection, compliance]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  last_ts=$(date -d "{{last_inspection_date}}" +%s 2>/dev/null || date -jf "%Y-%m-%d" "{{last_inspection_date}}" +%s);
+  days_since=$(( (today - last_ts) / 86400 ));
+  days_left=$(( {{typical_interval_days}} - days_since ));
+  if [ "$days_left" -le "{{warn_days}}" ]; then echo "WARNING: next health inspection likely due within $days_left days (last was {{last_inspection_date}})"; exit 1;
+  else echo "OK: next inspection likely due in about $days_left days"; fi
+variables:
+  last_inspection_date:
+    default: "2026-01-01"
+    description: Date of the last health inspection (YYYY-MM-DD).
+  typical_interval_days:
+    default: 180
+    description: Typical number of days between inspections in your jurisdiction.
+  warn_days:
+    default: 14
+    description: Days before the estimated next inspection to start warning.
+compatible_agents: [generic, claude, codex]
+notes: This is an estimate based on your jurisdiction's typical cadence, not an actual scheduled date — most health departments don't publish inspection dates in advance.

package/jobs/inventory/expiring-perishable-stock-check.yaml

@@ -0,0 +1,24 @@
+id: expiring-perishable-stock-check
+version: 1
+name: Expiring Perishable Stock Check
+description: >
+  Flags perishable inventory nearing its expiry date so it can be sold,
+  discounted, or used before it's wasted. Use this if stock has ever
+  expired on the shelf because nobody was tracking dates until it was too
+  late.
+category: inventory
+tags: [inventory, perishables, waste]
+schedule: "0 6 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  psql "{{database_url}}" -t -c "select sku, quantity, expiry_date from inventory where expiry_date is not null and expiry_date <= current_date + interval '{{warn_days}} days' order by expiry_date;"
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the inventory database.
+  warn_days:
+    default: 5
+    description: Days before expiry_date to start flagging stock.
+compatible_agents: [generic, claude, codex]
+notes: Assumes an `inventory` table with a nullable `expiry_date` column — adjust the query to your schema.

package/jobs/investing/dividend-payment-tracker.yaml

@@ -0,0 +1,34 @@
+id: dividend-payment-tracker
+version: 1
+name: Dividend Payment Tracker
+description: >
+  Checks that an expected dividend payment actually landed by its
+  scheduled pay date. Use this if a dividend has ever quietly not shown up
+  and it took weeks to notice something was wrong with a holding or
+  broker.
+category: investing
+tags: [investing, dividends, income]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" '
+    NR>1 && $3 == "pending" {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline pay_ts; close(cmd);
+      if (pay_ts < today) print "WARNING: " $1 " dividend was due " $2 " and is still marked pending";
+    }
+  ' {{dividends_csv}}
+variables:
+  dividends_csv:
+    default: "dividends.csv"
+    description: "CSV with header row, columns: ticker,pay_date(YYYY-MM-DD),status(pending/received)."
+  warn_days:
+    default: 0
+    description: Unused placeholder kept for consistency with other date-check jobs; flags immediately once the pay date has passed.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Update dividends.csv to "received" once a payment lands (check your
+  brokerage statement) — this job only flags entries still marked
+  "pending" past their pay date.

package/jobs/legal/nda-expiry-check.yaml

@@ -0,0 +1,31 @@
+id: nda-expiry-check
+version: 1
+name: NDA Expiry Check
+description: >
+  Warns you before a signed NDA reaches its expiration or renewal date.
+  Use this if an NDA has ever lapsed mid-relationship and nobody noticed
+  the confidentiality coverage had run out.
+category: legal
+tags: [legal, nda, contracts]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" -v warn={{warn_days}} '
+    NR>1 {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline exp_ts; close(cmd);
+      days_left = int((exp_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: NDA with \"" $1 "\" expires in " days_left " days (" $2 ")";
+    }
+  ' {{ndas_csv}}
+variables:
+  ndas_csv:
+    default: "ndas.csv"
+    description: "CSV with header row, columns: counterparty,expiry_date(YYYY-MM-DD)."
+  warn_days:
+    default: 30
+    description: Days before expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Keep ndas.csv updated whenever an NDA is signed — one row per counterparty/agreement.

package/jobs/logistics/freight-rate-spike-watch.yaml

@@ -0,0 +1,38 @@
+id: freight-rate-spike-watch
+version: 1
+name: Freight Rate Spike Watch
+description: >
+  Checks a freight lane's current quoted rate against your baseline and
+  flags a spike. Use this if a shipping rate has ever quietly doubled and
+  only got noticed when the invoice came in.
+category: logistics
+tags: [logistics, freight, rates]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check the current freight rate for the lane {{lane_description}} via
+  {{rate_source_hint}}.
+  1. Compare the current quote to the baseline rate of {{baseline_rate}}
+     per {{rate_unit}}.
+  2. Flag if it's {{spike_threshold_pct}}% or more above baseline.
+  3. Report the current rate, the delta, and if visible, the likely driver
+     (fuel surcharge, capacity crunch, seasonal demand).
+variables:
+  lane_description:
+    default: "Los Angeles, CA to Chicago, IL"
+    description: Origin/destination lane to check.
+  rate_source_hint:
+    default: "your freight broker or a rate index (DAT, Freightos)"
+    description: Where to check current freight rates.
+  baseline_rate:
+    default: 2.50
+    description: Baseline rate per unit to compare against.
+  rate_unit:
+    default: "mile"
+    description: Unit the rate is quoted in.
+  spike_threshold_pct:
+    default: 20
+    description: Percent above baseline that counts as a spike.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — freight rate sources vary (broker quotes, load boards, rate indices) and most don't expose a simple public API.

package/jobs/manufacturing/preventive-maintenance-due-check.yaml

@@ -0,0 +1,31 @@
+id: preventive-maintenance-due-check
+version: 1
+name: Preventive Maintenance Due Check
+description: >
+  Flags equipment coming due for scheduled preventive maintenance. Use
+  this if a machine has ever failed unexpectedly that would've been
+  caught by a PM visit nobody scheduled in time.
+category: manufacturing
+tags: [manufacturing, maintenance, equipment]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" -v warn={{warn_days}} '
+    NR>1 {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline due_ts; close(cmd);
+      days_left = int((due_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: equipment \"" $1 "\" PM due in " days_left " days (" $2 ")";
+    }
+  ' {{pm_schedule_csv}}
+variables:
+  pm_schedule_csv:
+    default: "pm-schedule.csv"
+    description: "CSV with header row, columns: equipment_id,next_pm_date(YYYY-MM-DD)."
+  warn_days:
+    default: 7
+    description: Days before the scheduled PM date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Keep pm-schedule.csv updated from your CMMS export or maintenance log before each run.

package/jobs/marketing/seo-rank-drop-watch.yaml

@@ -0,0 +1,38 @@
+id: seo-rank-drop-watch
+version: 1
+name: SEO Keyword Rank Drop Watch
+description: >
+  Checks a tracked keyword's search ranking and flags a real drop. Use
+  this if a page has ever slipped off page one and nobody noticed until
+  organic traffic was already down for weeks.
+category: marketing
+tags: [seo, rankings, marketing]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check the current search ranking for the keyword "{{keyword}}" targeting
+  {{target_url}}, via {{rank_source_hint}}.
+  1. Compare the current position to the baseline position of
+     {{baseline_position}}.
+  2. Flag a drop of {{drop_threshold_positions}} positions or more.
+  3. If dropped, note which competing URLs now outrank {{target_url}}, if
+     visible.
+variables:
+  keyword:
+    default: "your target keyword"
+    description: Keyword to track.
+  target_url:
+    default: "https://example.com/page"
+    description: URL you're tracking rank for.
+  rank_source_hint:
+    default: "a rank tracker (Ahrefs, SEMrush, Search Console) or a manual SERP check"
+    description: Where to check current rank.
+  baseline_position:
+    default: 5
+    description: Baseline ranking position to compare against.
+  drop_threshold_positions:
+    default: 5
+    description: Position drop that counts as a real regression.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — SERP position checking needs a rank-tracking API or live search, both of which vary by provider/region.

package/jobs/nonprofit/volunteer-hours-shortfall-check.yaml

@@ -0,0 +1,30 @@
+id: volunteer-hours-shortfall-check
+version: 1
+name: Volunteer Hours Shortfall Check
+description: >
+  Compares logged volunteer hours against a program's target and flags a
+  shortfall. Use this if a program has ever fallen behind on a grant's
+  volunteer-hour commitment without anyone noticing until the report was
+  due.
+category: nonprofit
+tags: [nonprofit, volunteers, programs]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  logged=$(awk -F, -v month="$(date +%Y-%m)" -v program="{{program_name}}" '$1 ~ month && $2 == program {sum += $3} END {print sum+0}' {{volunteer_hours_csv}});
+  target={{monthly_target_hours}};
+  if awk "BEGIN{exit !($logged < $target)}"; then echo "WARNING: {{program_name}} logged $logged of $target target hours this month"; exit 1;
+  else echo "OK: {{program_name}} logged $logged of $target target hours"; fi
+variables:
+  volunteer_hours_csv:
+    default: "volunteer-hours.csv"
+    description: "CSV with columns: month(YYYY-MM),program,hours."
+  program_name:
+    default: "your program"
+    description: Program name to check.
+  monthly_target_hours:
+    default: 100
+    description: Target volunteer hours for the program this month.
+compatible_agents: [generic, claude, codex]
+notes: Keep volunteer-hours.csv updated from your volunteer management system's export before each run.

package/jobs/podcast/guest-followup-reminder.yaml

@@ -0,0 +1,31 @@
+id: guest-followup-reminder
+version: 1
+name: Podcast Guest Follow-up Reminder
+description: >
+  Flags recorded guest episodes that haven't been published or thanked
+  yet. Use this if a guest has ever had to awkwardly ask when their
+  episode was coming out because nobody followed up after recording.
+category: podcast
+tags: [podcast, guests, followup]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" -v warn={{warn_days}} '
+    NR>1 && $3 == "unpublished" {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline recorded_ts; close(cmd);
+      days_since = int((today - recorded_ts) / 86400);
+      if (days_since >= warn) print "WARNING: episode with " $1 " recorded " days_since " days ago, still unpublished";
+    }
+  ' {{guest_episodes_csv}}
+variables:
+  guest_episodes_csv:
+    default: "guest-episodes.csv"
+    description: "CSV with header row, columns: guest_name,recorded_date(YYYY-MM-DD),status(unpublished/published)."
+  warn_days:
+    default: 14
+    description: Days since recording before an unpublished episode is flagged.
+compatible_agents: [generic, claude, codex]
+notes: Keep guest-episodes.csv updated as episodes are recorded and published — one row per guest episode.

package/jobs/realestate/rent-payment-late-check.yaml

@@ -0,0 +1,23 @@
+id: rent-payment-late-check
+version: 1
+name: Rent Payment Late Check
+description: >
+  Flags tenants whose rent is overdue past the grace period. Use this if
+  a late payment has ever gone unnoticed for weeks because nobody was
+  cross-checking the rent roll against the bank deposits.
+category: realestate
+tags: [realestate, rent, payments]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  psql "{{database_url}}" -t -c "select tenant_name, unit, amount_due, due_date from rent_ledger where paid = false and due_date < current_date - interval '{{grace_days}} days';"
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the property management database.
+  grace_days:
+    default: 5
+    description: Days past due_date before a late payment is flagged.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a `rent_ledger` table with `paid`, `due_date`, and `amount_due` columns — adjust the query to your property management system's schema.

package/jobs/sales/quota-attainment-check.yaml

@@ -0,0 +1,33 @@
+id: quota-attainment-check
+version: 1
+name: Quota Attainment Check
+description: >
+  Compares a rep's closed-won revenue this period against their quota
+  pace and flags whether they're on track. Use this if a rep has ever
+  found out they missed quota only at the end of the quarter, instead of
+  with enough runway left to fix it.
+category: sales
+tags: [sales, quota, pipeline]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  closed=$(psql "{{database_url}}" -t -c "select coalesce(sum(amount),0) from deals where owner = '{{rep_name}}' and stage = 'closed_won' and closed_at >= date_trunc('quarter', current_date);");
+  quota={{quarterly_quota}};
+  pct=$(awk "BEGIN{printf \"%.0f\", ($closed/$quota)*100}");
+  echo "quota check for {{rep_name}}: closed \$$closed of \$$quota quarterly quota (${pct}%) so far"
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the CRM/deals database.
+  rep_name:
+    default: "rep-name"
+    description: Sales rep owner field to check.
+  quarterly_quota:
+    default: 100000
+    description: Quarterly quota amount for this rep.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Prints closed-won revenue vs. quota for the current quarter; the pacing
+  math (days elapsed vs. days in quarter) is left for you or your agent to
+  interpret since exact quarter boundaries vary by fiscal calendar.

package/jobs/support/sla-breach-warning.yaml

@@ -0,0 +1,31 @@
+id: sla-breach-warning
+version: 1
+name: SLA Breach Warning
+description: >
+  Flags open tickets that are about to breach their SLA, before they
+  actually do. Use this if a ticket has ever blown past its SLA with zero
+  warning because the only check was after the fact.
+category: support
+tags: [support, sla, tickets]
+schedule: "*/15 * * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  count=$(curl -s -H "Authorization: Bearer {{api_token}}" "{{api_url}}" | grep -o '"status":"open"' | wc -l | tr -d ' ');
+  if [ -z "$count" ] || [ "$count" -eq 0 ]; then echo "OK: no tickets approaching SLA breach"; exit 0;
+  else echo "WARNING: $count ticket(s) within {{warn_minutes}} minutes of SLA breach at {{api_url}}"; exit 1; fi
+variables:
+  api_url:
+    default: "https://api.example-helpdesk.com/tickets?status=open&sla_remaining_lt_minutes=30"
+    description: Helpdesk API endpoint pre-filtered to tickets close to breaching SLA.
+  api_token:
+    default: "your-api-token"
+    description: Bearer token for the helpdesk API.
+  warn_minutes:
+    default: 30
+    description: Minutes of SLA time remaining that counts as "about to breach", for labeling output.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Proactive counterpart to `ticket-backlog-aging-check` (which flags
+  tickets already past SLA) — point api_url at your helpdesk's filtered
+  search for tickets still within SLA but running low on time.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wonsukchoi/crondex",
-  "version": "0.7.0",
+  "version": "0.8.0",
   "description": "A public directory of pre-made, agent-editable cron jobs.",
   "type": "module",
   "license": "MIT",