@wonsukchoi/crondex 0.18.0 → 0.20.0

package/jobs/hr/i9-reverification-deadline-check.yaml

@@ -0,0 +1,36 @@
+id: i9-reverification-deadline-check
+version: 1
+name: I-9 Reverification Deadline Check
+description: >
+  Checks employees whose work authorization document has an expiration
+  date and warns before I-9 reverification is due. Use this if an I-9
+  reverification deadline has ever been missed and only caught during an
+  audit.
+category: hr
+tags: [hr, compliance, i9, employment-eligibility]
+schedule: "0 8 * * 1"
+timezone: "America/New_York"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    $2 == "" {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 "REVERIFICATION DUE: %s — document expires %s (%d days)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{i9_tracking_csv_path}}"
+variables:
+  i9_tracking_csv_path:
+    default: "./i9-tracking.csv"
+    description: "Path to a CSV with columns: employee_name,document_expiry_date (YYYY-MM-DD, blank if the employee's document has no expiration)."
+  warn_days_before:
+    default: 60
+    description: How many days before document expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Only applies to employees whose work-authorization document has an expiration date; consult counsel for I-9 process specifics and required forms.

package/jobs/hr/probation-period-review-reminder.yaml

@@ -0,0 +1,36 @@
+id: probation-period-review-reminder
+version: 1
+name: Probation Period Review Reminder
+description: >
+  Warns you before a new hire's probation period ends so a manager can
+  complete the required review before it lapses automatically. Use this
+  if a probation deadline has ever passed with no review on file and
+  nobody caught it until it became a compliance headache.
+category: hr
+tags: [hr, probation, new-hire, compliance]
+schedule: "0 8 * * 1"
+timezone: "America/New_York"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    $3 != "" {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline end_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (end_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "REVIEW DUE: %s — probation ends %s (%d days), no review on file\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{probation_tracking_csv_path}}"
+variables:
+  probation_tracking_csv_path:
+    default: "./probation-tracking.csv"
+    description: "Path to a CSV with columns: employee_name,probation_end_date (YYYY-MM-DD),review_completed_date (blank if not yet done)."
+  warn_days_before:
+    default: 14
+    description: How many days before probation ends to start warning if no review is on file.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a maintained CSV export from your HRIS tracking probation end dates and review completion; distinct from performance-review-cycle-reminder, which covers ongoing cyclical reviews rather than one-time new-hire probation.

package/jobs/insurance/beneficiary-designation-review-reminder.yaml

@@ -0,0 +1,35 @@
+id: beneficiary-designation-review-reminder
+version: 1
+name: Beneficiary Designation Review Reminder
+description: >
+  Reminds you to review beneficiary designations on your insurance
+  policies and retirement accounts once they haven't been checked in a
+  while. Use this if a beneficiary has ever gone unchanged for years
+  through a marriage, divorce, or new child without anyone catching it.
+category: insurance
+tags: [insurance, beneficiary, review, reminder]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v interval="{{review_interval_days}}" '
+    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_review_epoch; close(cmd);
+      days_since = (today - last_review_epoch) / 86400;
+      if (days_since >= interval) {
+        printf "REVIEW DUE: %s — last reviewed %s (%d days ago)\n", $1, $2, days_since;
+      }
+    }
+  ' "{{beneficiary_review_csv}}"
+variables:
+  beneficiary_review_csv:
+    default: "beneficiary-reviews.csv"
+    description: "CSV with header row, columns: policy_or_account_name,last_review_date (YYYY-MM-DD)."
+  review_interval_days:
+    default: 365
+    description: How many days to allow between beneficiary reviews before flagging it as due.
+compatible_agents: [generic, claude, codex]
+notes: Update last_review_date in the CSV each time you actually confirm designations are current, and after any major life event (marriage, divorce, new child, death in the family).

package/jobs/insurance/endorsement-request-followup-check.yaml

@@ -0,0 +1,37 @@
+id: endorsement-request-followup-check
+version: 1
+name: Policy Endorsement Request Follow-up Check
+description: >
+  Checks requested policy endorsements or amendments (e.g. adding a
+  driver, changing coverage limits) that haven't been confirmed processed
+  within a set window and flags them for follow-up. Use this if you've
+  ever submitted a change request to a carrier and only found out months
+  later it was never actually applied.
+category: insurance
+tags: [insurance, endorsement, policy-changes, 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 — %s requested %s (%d days, not confirmed processed)\n", $1, $2, $3, pending_days;
+      }
+    }
+  ' "{{endorsements_csv_path}}"
+variables:
+  endorsements_csv_path:
+    default: "./endorsement-requests.csv"
+    description: "Path to a CSV with columns: policy_name,requested_change,requested_date (YYYY-MM-DD),confirmed_date (blank if not yet confirmed by the carrier)."
+  overdue_days:
+    default: 10
+    description: Days since an endorsement was requested, with no carrier confirmation, before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: Maintain the CSV manually or export it from your broker/agency management system; distinct from claim-status-check, which tracks claims rather than policy change requests.

package/jobs/inventory/purchase-order-receiving-delay-check.yaml

@@ -0,0 +1,33 @@
+id: purchase-order-receiving-delay-check
+version: 1
+name: Purchase Order Receiving Delay Check
+description: >
+  Checks open purchase orders against their expected delivery date and
+  flags any that are overdue and not yet marked received. Use this if
+  stock has ever run out because a purchase order was quietly late and
+  nobody chased the supplier until shelves were already empty.
+category: inventory
+tags: [inventory, purchase-orders, receiving, suppliers]
+schedule: "0 7 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" '
+    NR==1 {next}
+    $5 != "" {next}
+    {
+      cmd = "date -d \"" $4 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $4 "\" +%s 2>/dev/null";
+      cmd | getline expected_epoch; close(cmd);
+      overdue_days = (today - expected_epoch) / 86400;
+      if (overdue_days > 0) {
+        printf "OVERDUE: PO %s from %s expected %s (%d days late, not received)\n", $1, $2, $4, overdue_days;
+      }
+    }
+  ' "{{purchase_orders_csv_path}}"
+variables:
+  purchase_orders_csv_path:
+    default: "./purchase-orders.csv"
+    description: "Path to a CSV with columns: po_number,supplier_name,order_date (YYYY-MM-DD),expected_delivery_date (YYYY-MM-DD),received_date (blank if not yet received)."
+compatible_agents: [generic, claude, codex]
+notes: Assumes a maintained CSV export from your procurement/inventory system; distinct from supplier-lead-time-drift-check, which tracks aggregate lead-time trends rather than individual overdue POs.

package/jobs/inventory/supplier-lead-time-drift-check.yaml

@@ -0,0 +1,34 @@
+id: supplier-lead-time-drift-check
+version: 1
+name: Supplier Lead Time Drift Check
+description: >
+  Compares each supplier's recent delivery lead time against their
+  historical baseline and flags suppliers who have started shipping
+  noticeably slower. Use this if a reorder point has ever gone stale
+  because a supplier quietly started taking longer to deliver than they
+  used to.
+category: inventory
+tags: [inventory, suppliers, lead-time, procurement]
+schedule: "0 6 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v threshold="{{drift_threshold_days}}" '
+    NR==1 {next}
+    {
+      supplier = $1; baseline = $2 + 0; recent = $3 + 0;
+      drift = recent - baseline;
+      if (drift >= threshold) {
+        printf "LEAD TIME DRIFT: %s — baseline %d days, recent %d days (+%d days)\n", supplier, baseline, recent, drift;
+      }
+    }
+  ' "{{supplier_lead_times_csv}}"
+variables:
+  supplier_lead_times_csv:
+    default: "./supplier-lead-times.csv"
+    description: "Path to a CSV with columns: supplier_name,baseline_lead_time_days,recent_lead_time_days."
+  drift_threshold_days:
+    default: 3
+    description: Days of increase over baseline before a supplier is flagged.
+compatible_agents: [generic, claude, codex]
+notes: Feed recent_lead_time_days from actual PO-to-delivery data (e.g. an average of the last 3-5 orders) rather than a single order, to avoid false positives from one slow shipment.

package/jobs/investing/bond-cd-maturity-reminder.yaml

@@ -0,0 +1,31 @@
+id: bond-cd-maturity-reminder
+version: 1
+name: Bond & CD Maturity Reminder
+description: >
+  Warns you before a bond or certificate of deposit reaches its maturity
+  date. Use this if a CD has ever auto-renewed into a worse rate because
+  the maturity date crept up unnoticed.
+category: investing
+tags: [investing, bonds, cd, maturity]
+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 mat_ts; close(cmd);
+      days_left = int((mat_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: \"" $1 "\" (" $3 ") matures in " days_left " days (" $2 ")";
+    }
+  ' {{holdings_csv}}
+variables:
+  holdings_csv:
+    default: "bond-cd-holdings.csv"
+    description: "CSV with header row, columns: name,maturity_date(YYYY-MM-DD),amount."
+  warn_days:
+    default: 30
+    description: Days before maturity to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Keep bond-cd-holdings.csv updated whenever you buy or roll over a bond/CD — one row per holding.

package/jobs/investing/dca-contribution-reminder.yaml

@@ -0,0 +1,33 @@
+id: dca-contribution-reminder
+version: 1
+name: DCA Contribution Reminder
+description: >
+  Checks your dollar-cost-averaging log and warns if it's been longer than
+  your planned interval since the last logged contribution. Use this if
+  you've ever meant to invest a fixed amount on a schedule and let a month
+  slip by without actually placing the order.
+category: investing
+tags: [investing, dca, dollar-cost-averaging, contributions]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  last_line=$(tail -n 1 "{{contribution_log_csv}}" 2>/dev/null);
+  if [ -z "$last_line" ]; then echo "WARNING: no contributions logged yet in {{contribution_log_csv}}"; exit 1; fi;
+  last_date=$(echo "$last_line" | cut -d',' -f1);
+  last_ts=$(date -d "$last_date" +%s 2>/dev/null || date -jf "%Y-%m-%d" "$last_date" +%s 2>/dev/null);
+  today_ts=$(date +%s);
+  days_since=$(( (today_ts - last_ts) / 86400 ));
+  if [ "$days_since" -ge "{{interval_days}}" ]; then
+    echo "WARNING: last DCA contribution was $days_since days ago (on $last_date) — due for another (${{interval_days}}-day interval)";
+    exit 1;
+  else echo "OK: last DCA contribution was $days_since days ago (on $last_date), within the ${{interval_days}}-day interval"; fi
+variables:
+  contribution_log_csv:
+    default: "dca-contributions.csv"
+    description: "CSV with header row, columns: date(YYYY-MM-DD),amount,ticker — append a row each time you invest."
+  interval_days:
+    default: 30
+    description: Expected number of days between contributions before this flags as overdue.
+compatible_agents: [generic, claude, codex]
+notes: Append a row to dca-contributions.csv yourself (or via your brokerage export) each time you make a scheduled contribution.

package/jobs/learning/practice-streak-check.yaml

@@ -0,0 +1,33 @@
+id: practice-streak-check
+version: 1
+name: Skill Practice Streak Check
+description: >
+  Checks a practice log file for a skill you're building (language,
+  instrument, coding kata) and warns if too many days have passed since
+  the last logged session. Use this if a daily practice habit has ever
+  quietly lapsed without you noticing until weeks had gone by.
+category: learning
+tags: [learning, practice, streak, habit]
+schedule: "0 20 * * *"
+timezone: "America/Los_Angeles"
+runner: shell
+command: >
+  last_line=$(tail -n1 "{{log_file_path}}" 2>/dev/null);
+  if [ -z "$last_line" ]; then echo "WARNING: no practice sessions logged yet in {{log_file_path}}"; exit 1; fi;
+  last_ts=$(date -d "$last_line" +%s 2>/dev/null || date -jf "%Y-%m-%d" "$last_line" +%s);
+  now_ts=$(date +%s);
+  days_since=$(( (now_ts - last_ts) / 86400 ));
+  if [ "$days_since" -ge "{{max_gap_days}}" ]; then echo "WARNING: no {{skill_name}} practice logged in $days_since days"; exit 1;
+  else echo "OK: last {{skill_name}} practice $days_since days ago"; fi
+variables:
+  log_file_path:
+    default: "./practice-log.txt"
+    description: "Path to a text file with one YYYY-MM-DD line per practice session, newest last."
+  skill_name:
+    default: "your skill"
+    description: Name of the skill being tracked, for labeling output.
+  max_gap_days:
+    default: 3
+    description: Days without a logged session before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: Append today's date to practice-log.txt each time you practice (e.g. `date +%F >> practice-log.txt`) — this job only reads the file, it doesn't log sessions for you.

package/jobs/learning/webinar-attendance-reminder.yaml

@@ -0,0 +1,32 @@
+id: webinar-attendance-reminder
+version: 1
+name: Webinar Attendance Reminder
+description: >
+  Checks a list of webinars/workshops you've registered for and flags any
+  happening soon so you can block the time and prep. Use this if you've
+  ever signed up for a webinar and completely forgotten about it by the
+  time it started.
+category: learning
+tags: [learning, webinars, events, reminders]
+schedule: "0 8 * * *"
+timezone: "America/Los_Angeles"
+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 event_ts; close(cmd);
+      days_left = int((event_ts - today) / 86400);
+      if (days_left >= 0 && days_left <= warn) print "UPCOMING: \"" $1 "\" on " $2 " (in " days_left " day(s))";
+    }
+  ' "{{registrations_csv}}"
+variables:
+  registrations_csv:
+    default: "webinar-registrations.csv"
+    description: "CSV with header row, columns: title,date(YYYY-MM-DD)."
+  warn_days:
+    default: 3
+    description: Days ahead of a webinar to start flagging it as upcoming.
+compatible_agents: [generic, claude, codex]
+notes: Add a row to webinar-registrations.csv whenever you sign up for a webinar or workshop — this job only reads it, it doesn't register you anywhere.

package/jobs/legal/business-license-renewal-check.yaml

@@ -0,0 +1,37 @@
+id: business-license-renewal-check
+version: 1
+name: Business License Renewal Check
+description: >
+  Warns you before a specific business license or permit (liquor,
+  contractor, professional, health department, etc.) reaches its renewal
+  deadline. Use this if a license has ever lapsed because its renewal
+  date lived only in someone's memory instead of a calendar.
+category: legal
+tags: [legal, license, permit, renewal]
+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 \"" $3 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $3 "\" +%s";
+      cmd | getline exp_ts; close(cmd);
+      days_left = int((exp_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: \"" $1 "\" (" $2 ") expires in " days_left " days (" $3 ")";
+    }
+  ' {{licenses_csv}}
+variables:
+  licenses_csv:
+    default: "business-licenses.csv"
+    description: "CSV with header row, columns: license_name,jurisdiction,expiry_date(YYYY-MM-DD)."
+  warn_days:
+    default: 45
+    description: Days before expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Keep business-licenses.csv updated whenever a license/permit is issued
+  or renewed — one row per license/jurisdiction. Distinct from
+  `compliance-filing-deadline-reminder` (recurring corporate/state
+  filings like annual reports and franchise tax) — this tracks
+  individually-issued operating licenses and permits instead.

package/jobs/legal/patent-maintenance-fee-reminder.yaml

@@ -0,0 +1,35 @@
+id: patent-maintenance-fee-reminder
+version: 1
+name: Patent Maintenance Fee Reminder
+description: >
+  Warns you before a patent maintenance (annuity) fee comes due so the
+  patent doesn't lapse. Use this if a patent has ever gone abandoned
+  because a maintenance fee deadline was missed.
+category: legal
+tags: [legal, patents, ip, maintenance-fees]
+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 due_ts; close(cmd);
+      days_left = int((due_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: patent \"" $1 "\" maintenance fee due in " days_left " days (" $2 ")";
+    }
+  ' "{{patents_csv}}"
+variables:
+  patents_csv:
+    default: "patent-maintenance-fees.csv"
+    description: "CSV with header row, columns: patent_name_or_number,fee_due_date(YYYY-MM-DD)."
+  warn_days:
+    default: 60
+    description: Days before a maintenance fee due date to start warning — most jurisdictions allow a grace period but with a surcharge, so warn early.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Keep patent-maintenance-fees.csv updated with each patent's next fee due
+  date (from your IP counsel or the relevant patent office schedule) —
+  fee intervals and amounts vary by jurisdiction, so this job only tracks
+  dates you supply.

package/jobs/logistics/driver-hos-compliance-check.yaml

@@ -0,0 +1,38 @@
+id: driver-hos-compliance-check
+version: 1
+name: Driver Hours-of-Service Compliance Check
+description: >
+  Checks logged driving hours against the daily hours-of-service limit and
+  flags any driver close to or over it. Use this if a driver has ever run
+  over their legal on-duty hours because nobody was tallying it in real
+  time.
+category: logistics
+tags: [logistics, drivers, hos, compliance, safety]
+schedule: "0 */4 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v limit={{daily_hours_limit}} -v warn={{warn_hours_remaining}} '
+    NR>1 {
+      driver = $1; hours_today = $2;
+      remaining = limit - hours_today;
+      if (hours_today >= limit) print "OVER LIMIT: " driver " has logged " hours_today "h, exceeds the " limit "h daily limit";
+      else if (remaining <= warn) print "WARNING: " driver " has logged " hours_today "h, only " remaining "h remaining before the " limit "h daily limit";
+    }
+  ' "{{driver_hours_csv}}"
+variables:
+  driver_hours_csv:
+    default: "driver-hours-today.csv"
+    description: "CSV with header row, columns: driver_name,hours_logged_today — update from your ELD (electronic logging device) export."
+  daily_hours_limit:
+    default: 11
+    description: Maximum on-duty driving hours allowed per day under your governing HOS rules.
+  warn_hours_remaining:
+    default: 1
+    description: Hours remaining before the limit at which to start warning a driver is close.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Defaults reflect the US FMCSA 11-hour driving limit — adjust
+  daily_hours_limit for your jurisdiction's rules. This is a schedule-side
+  check against a CSV you export from your ELD/telematics system, not a
+  replacement for that system's own compliance logging.

package/jobs/logistics/port-congestion-watch.yaml

@@ -0,0 +1,34 @@
+id: port-congestion-watch
+version: 1
+name: Port Congestion Watch
+description: >
+  Checks a port's average vessel wait time and flags it once congestion
+  crosses your threshold. Use this if a congested port has ever blown up
+  a shipping timeline before anyone checked the wait times.
+category: logistics
+tags: [logistics, port, congestion, shipping]
+schedule: "0 6 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  wait_hours=$(curl -s -H "Authorization: Bearer {{port_api_token}}" "{{port_status_api_url}}" | grep -o '"avg_wait_hours":[0-9.]*' | head -n1 | cut -d':' -f2);
+  if [ -z "$wait_hours" ]; then echo "ERROR: could not fetch port congestion data from {{port_status_api_url}}"; exit 1; fi;
+  if awk "BEGIN{exit !($wait_hours >= {{wait_hours_threshold}})}"; then
+    echo "WARNING: {{port_name}} average vessel wait is ${wait_hours}h (>= {{wait_hours_threshold}}h)";
+    exit 1;
+  else echo "OK: {{port_name}} average vessel wait is ${wait_hours}h"; fi
+variables:
+  port_name:
+    default: "your-port"
+    description: Port name, for labeling output.
+  port_status_api_url:
+    default: "https://api.example-port-tracker.com/ports/your-port/status"
+    description: Port status API endpoint returning avg_wait_hours.
+  port_api_token:
+    default: "your-api-token"
+    description: Bearer token for the port/maritime data API.
+  wait_hours_threshold:
+    default: 48
+    description: Hours of average vessel wait before flagging as congested.
+compatible_agents: [generic, claude, codex]
+notes: Generic REST pattern — point port_status_api_url at your port authority's or a maritime data provider's (MarineTraffic, Portcast, project44) congestion endpoint; adjust field names to match its response shape.

package/jobs/manufacturing/energy-consumption-spike-check.yaml

@@ -0,0 +1,37 @@
+id: energy-consumption-spike-check
+version: 1
+name: Energy Consumption Spike Check
+description: >
+  Compares today's logged energy usage against a rolling baseline and
+  flags an unusual spike. Use this if a jump in electricity use has ever
+  gone unnoticed until the utility bill arrived, when it could have
+  pointed to a failing motor, a stuck compressor, or equipment left
+  running.
+category: manufacturing
+tags: [manufacturing, energy, utilities, anomaly]
+schedule: "0 7 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v threshold={{spike_pct_threshold}} '
+    NR>1 { sum += $2; count++; readings[count] = $2 }
+    END {
+      if (count < 2) { print "OK: not enough readings yet to establish a baseline"; exit 0 }
+      latest = readings[count];
+      baseline_sum = sum - latest;
+      baseline_avg = baseline_sum / (count - 1);
+      if (baseline_avg == 0) { print "OK: baseline average is zero, skipping comparison"; exit 0 }
+      pct_over = ((latest - baseline_avg) / baseline_avg) * 100;
+      if (pct_over >= threshold) printf "SPIKE: latest reading %.1f kWh is %.1f%% above the %.1f kWh rolling baseline\n", latest, pct_over, baseline_avg;
+      else printf "OK: latest reading %.1f kWh is within %.1f%% of the %.1f kWh rolling baseline\n", latest, threshold, baseline_avg;
+    }
+  ' "{{energy_readings_csv}}"
+variables:
+  energy_readings_csv:
+    default: "energy-readings.csv"
+    description: "CSV with header row, columns: date,kwh — one row per day, most recent row last."
+  spike_pct_threshold:
+    default: 25
+    description: Percent above the rolling baseline average that counts as a spike worth flagging.
+compatible_agents: [generic, claude, codex]
+notes: Append a row to energy-readings.csv daily (from a smart meter export or utility portal) — the baseline is just the average of all prior rows, so accuracy improves as history builds up.

package/jobs/manufacturing/equipment-calibration-due-check.yaml

@@ -0,0 +1,32 @@
+id: equipment-calibration-due-check
+version: 1
+name: Equipment Calibration Due Check
+description: >
+  Warns you before a piece of measurement or test equipment is due for
+  calibration. Use this if an out-of-calibration gauge has ever kept
+  producing "passing" measurements nobody could actually trust.
+category: manufacturing
+tags: [manufacturing, calibration, quality, compliance]
+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 last_ts; close(cmd);
+      due_ts = last_ts + ($3 * 86400);
+      days_left = int((due_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: equipment \"" $1 "\" calibration due in " days_left " days";
+    }
+  ' {{equipment_csv}}
+variables:
+  equipment_csv:
+    default: "calibration-schedule.csv"
+    description: "CSV with header row, columns: equipment_id,last_calibrated(YYYY-MM-DD),interval_days."
+  warn_days:
+    default: 14
+    description: Days before calibration is due to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Keep calibration-schedule.csv updated after every calibration event — one row per instrument/gauge.

package/jobs/marketing/broken-campaign-link-check.yaml

@@ -0,0 +1,31 @@
+id: broken-campaign-link-check
+version: 1
+name: Broken Campaign Link Check
+description: >
+  Requests each active campaign's landing page URL and flags any that
+  return an error instead of loading. Use this if paid traffic has ever
+  kept flowing to a campaign whose landing page was quietly down or
+  redirecting to a 404.
+category: marketing
+tags: [marketing, campaigns, links, uptime]
+schedule: "0 */2 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  while IFS=',' read -r name url; do
+    [ "$name" = "campaign_name" ] && continue;
+    [ -z "$url" ] && continue;
+    code=$(curl -s -o /dev/null -w "%{http_code}" --max-time {{timeout_seconds}} "$url");
+    if [ "$code" -ge 400 ] || [ "$code" = "000" ]; then
+      echo "BROKEN: \"$name\" -> $url returned HTTP $code";
+    fi;
+  done < "{{campaign_urls_csv}}"
+variables:
+  campaign_urls_csv:
+    default: "campaign-urls.csv"
+    description: "CSV with header row, columns: campaign_name,landing_page_url — one row per active campaign."
+  timeout_seconds:
+    default: 10
+    description: Seconds to wait for each landing page before treating it as unreachable.
+compatible_agents: [generic, claude, codex]
+notes: Keep campaign-urls.csv in sync with whatever's currently live in your ad platform — a URL left in the file after a campaign ends will keep getting checked (and may false-flag if the page is intentionally retired).

package/jobs/marketing/newsletter-unsubscribe-spike-check.yaml

@@ -0,0 +1,37 @@
+id: newsletter-unsubscribe-spike-check
+version: 1
+name: Newsletter Unsubscribe Spike Check
+description: >
+  Checks your most recent newsletter send's unsubscribe rate against a
+  threshold and flags it if it's abnormally high. Use this if a bad
+  subject line or list segment has ever quietly torched your audience
+  before anyone compared it to prior sends.
+category: marketing
+tags: [marketing, newsletter, unsubscribe, retention]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  unsub_rate=$(curl -s -H "Authorization: Bearer {{esp_api_token}}" "{{campaign_stats_api_url}}" | grep -o '"unsubscribe_rate":[0-9.]*' | head -n1 | cut -d':' -f2);
+  if [ -z "$unsub_rate" ]; then echo "ERROR: could not fetch unsubscribe rate from {{campaign_stats_api_url}}"; exit 1; fi;
+  if awk "BEGIN{exit !($unsub_rate >= {{unsub_rate_threshold}})}"; then
+    echo "WARNING: unsubscribe rate ${unsub_rate}% is at/above threshold {{unsub_rate_threshold}}%";
+    exit 1;
+  else echo "OK: unsubscribe rate ${unsub_rate}%"; fi
+variables:
+  campaign_stats_api_url:
+    default: "https://api.example-esp.com/campaigns/latest/stats"
+    description: Email service provider endpoint returning the most recent send's unsubscribe_rate as a percent.
+  esp_api_token:
+    default: "your-api-token"
+    description: API token for the email service provider.
+  unsub_rate_threshold:
+    default: 0.5
+    description: Percent unsubscribe rate that triggers a warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Generic REST pattern — point campaign_stats_api_url at your ESP's
+  (Mailchimp, Klaviyo, SendGrid) campaign stats endpoint for the most
+  recent send; adjust field names to match its response shape. Distinct
+  from `email-deliverability-check` (bounce/spam-complaint risk) — this
+  tracks list attrition per send instead.