@wonsukchoi/crondex 0.21.0 → 0.22.0

package/jobs/finance/budget-vs-actual-variance-report.yaml

@@ -0,0 +1,38 @@
+id: budget-vs-actual-variance-report
+version: 1
+name: Budget vs. Actual Variance Report
+description: >
+  Compares budgeted vs. actual spend across every category or department
+  in one pass and reports the percentage variance for each, not just a
+  single category's pass/fail. Use this if you need a monthly variance
+  report across a whole budget (department, project, or household), which
+  is different from budget-overspend-check watching one category's limit.
+category: finance
+tags: [budget, variance, finance, reporting]
+schedule: "0 9 2 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  file={{budget_file}}; threshold={{variance_threshold_pct}};
+  [ -f "$file" ] || { echo "ERROR: $file not found"; exit 1; };
+  tail -n +2 "$file" | while IFS=, read -r category budgeted actual; do
+    variance=$(awk -v b="$budgeted" -v a="$actual" 'BEGIN{if(b==0){print "NA"} else {printf "%.1f", ((a-b)/b)*100}}');
+    if [ "$variance" = "NA" ]; then echo "$category: budget \$0, actual \$$actual (no budget set)"; continue; fi;
+    flag="";
+    if awk -v v="$variance" -v t="$threshold" 'BEGIN{exit !(v+0 > t || v+0 < -t)}'; then flag=" <-- OVER THRESHOLD"; fi;
+    echo "$category: budget \$$budgeted, actual \$$actual, variance ${variance}%$flag";
+  done
+variables:
+  budget_file:
+    default: "./budget-vs-actual.csv"
+    description: >
+      CSV with header "category,budgeted,actual" — one row per
+      category/department for the current period.
+  variance_threshold_pct:
+    default: 10
+    description: Percentage-point variance (over or under) that triggers a flag.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Zero-token. Distinct from budget-overspend-check, which watches a single
+  category against one hard dollar limit day-to-day — this one is a
+  periodic multi-category variance report across an entire budget.

package/jobs/finance/contractor-1099-threshold-tracker.yaml

@@ -0,0 +1,43 @@
+id: contractor-1099-threshold-tracker
+version: 1
+name: Contractor 1099 Threshold Tracker
+description: >
+  Tracks year-to-date payments per contractor and flags anyone
+  approaching or past the tax reporting threshold that triggers a 1099.
+  Use this if you pay freelancers or contractors and don't want to
+  discover in January that you're missing W-9s for someone you owe a
+  filing for.
+category: finance
+tags: ["1099", contractors, tax, finance]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  file={{payments_file}}; threshold={{reporting_threshold}}; warn_pct={{warn_pct}};
+  [ -f "$file" ] || { echo "ERROR: $file not found"; exit 1; };
+  year=$(date +%Y);
+  awk -F, -v year="$year" -v threshold="$threshold" -v warnpct="$warn_pct" '
+    NR>1 && $3 ~ "^"year"-" { total[$1] += $2 }
+    END {
+      for (contractor in total) {
+        pct = (total[contractor] / threshold) * 100;
+        if (total[contractor] >= threshold) print "OVER THRESHOLD: " contractor " paid $" total[contractor] " this year (1099 required)";
+        else if (pct >= warnpct) printf "APPROACHING: %s paid $%.2f this year (%.0f%% of $%.0f threshold)\n", contractor, total[contractor], pct, threshold;
+      }
+    }
+  ' "$file"
+variables:
+  payments_file:
+    default: "./contractor-payments.csv"
+    description: "CSV with header \"contractor,amount,date\" (date is YYYY-MM-DD), one row per payment."
+  reporting_threshold:
+    default: 600
+    description: Cumulative annual payment amount that triggers a 1099 filing requirement (US default is $600; adjust for your jurisdiction/year).
+  warn_pct:
+    default: 75
+    description: Percentage of the threshold at which to start warning ahead of a required filing.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Zero-token. US-centric default threshold — verify current IRS rules
+  and any state-specific thresholds for your situation; this doesn't
+  file anything, it only flags who needs a W-9/1099.

package/jobs/finance/credit-utilization-watch.yaml

@@ -0,0 +1,40 @@
+id: credit-utilization-watch
+version: 1
+name: Credit Utilization Watch
+description: >
+  Checks the balance-to-limit ratio on a credit card or line of credit
+  and warns when utilization crosses a threshold. Use this if you want
+  to protect your credit score or stay within a business line of
+  credit's comfortable operating range, rather than finding out only
+  when a statement arrives.
+category: finance
+tags: [credit, utilization, finance]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  balance={{current_balance}}; limit={{credit_limit}}; threshold={{warn_pct}};
+  util=$(awk -v b="$balance" -v l="$limit" 'BEGIN{if(l==0){print 0} else {printf "%.1f", (b/l)*100}}');
+  if awk -v u="$util" -v t="$threshold" 'BEGIN{exit !(u+0 >= t)}'; then
+    echo "WARNING: {{account_name}} utilization at ${util}% (\$$balance of \$$limit) — over ${threshold}% threshold";
+  else
+    echo "OK: {{account_name}} utilization at ${util}% (\$$balance of \$$limit)";
+  fi
+variables:
+  account_name:
+    default: "business line of credit"
+    description: Label for the account being checked.
+  current_balance:
+    default: 0
+    description: Current outstanding balance — update this manually or via your bank export before each run.
+  credit_limit:
+    default: 10000
+    description: Total credit limit on the account.
+  warn_pct:
+    default: 30
+    description: Utilization percentage at or above which to warn (30% is a common credit-score-friendly ceiling).
+compatible_agents: [generic, claude, codex]
+notes: >
+  Zero-token. current_balance is a manual input (or piped in from a
+  balance-export script) — this job doesn't fetch live balances from any
+  bank API itself.

package/jobs/finance/duplicate-payment-detection.yaml

@@ -0,0 +1,43 @@
+id: duplicate-payment-detection
+version: 1
+name: Duplicate Payment Detection
+description: >
+  Scans a payments/disbursements log for the same vendor and invoice
+  number (or same vendor/amount/date) paid more than once. Use this if
+  a bill has ever gotten paid twice because it was submitted through two
+  channels or reprocessed after a system hiccup.
+category: finance
+tags: [duplicate-payment, accounts-payable, fraud-prevention, finance]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  file={{payments_file}};
+  [ -f "$file" ] || { echo "ERROR: $file not found"; exit 1; };
+  echo "-- duplicate vendor+invoice_id --";
+  tail -n +2 "$file" | awk -F, '{key=$1"|"$2; count[key]++; rows[key]=rows[key]"\n    " $0} END{for (k in count) if (count[k]>1) print "DUPLICATE: " k " paid " count[k] " times:" rows[k]}';
+  echo "-- same vendor+amount within {{same_amount_window_days}} day(s) --";
+  tail -n +2 "$file" | sort -t, -k1,1 -k4,4 | awk -F, -v win="{{same_amount_window_days}}" '
+    {
+      cmd="date -d \"" $4 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $4 "\" +%s";
+      cmd | getline ts; close(cmd);
+      key=$1"|"$3;
+      if (key == prevkey && (ts - prevts) <= win*86400) print "POSSIBLE DUPLICATE: " $1 " $" $3 " paid on " prevdate " and again on " $4;
+      prevkey=key; prevts=ts; prevdate=$4;
+    }
+  '
+variables:
+  payments_file:
+    default: "./payments-log.csv"
+    description: >
+      CSV with header "vendor,invoice_id,amount,date" (date is
+      YYYY-MM-DD) — one row per outgoing payment made.
+  same_amount_window_days:
+    default: 14
+    description: Flag same vendor+amount payments made within this many days of each other, even without a matching invoice_id.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Zero-token. Exact-match check on vendor+invoice_id catches clear
+  duplicates; the amount+window check is a heuristic for reprocessed
+  payments without a shared invoice_id — review flagged pairs before
+  assuming either is a real duplicate.

package/jobs/finance/expense-report-compliance-check.yaml

@@ -0,0 +1,46 @@
+id: expense-report-compliance-check
+version: 1
+name: Expense Report Compliance Check
+description: >
+  Scans submitted expense report line items for missing receipts or
+  amounts over your policy limit for that category. Use this if
+  reimbursements have ever gone out the door with a missing receipt or a
+  suspiciously large "meals" line nobody double-checked.
+category: finance
+tags: [expenses, compliance, policy, finance]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  file={{expenses_file}};
+  [ -f "$file" ] || { echo "ERROR: $file not found"; exit 1; };
+  tail -n +2 "$file" | while IFS=, read -r employee category amount has_receipt date; do
+    flagged="";
+    if [ "$has_receipt" != "yes" ] && awk "BEGIN{exit !($amount > {{receipt_required_over}})}"; then
+      flagged="$flagged missing-receipt";
+    fi;
+    limit=$(awk -F, -v cat="$category" '$1==cat{print $2}' {{category_limits_file}} 2>/dev/null);
+    if [ -n "$limit" ] && awk "BEGIN{exit !($amount > $limit)}"; then
+      flagged="$flagged over-limit(\$$limit)";
+    fi;
+    if [ -n "$flagged" ]; then echo "FLAGGED: $employee — $category \$$amount on $date —$flagged"; fi;
+  done
+variables:
+  expenses_file:
+    default: "./expense-reports.csv"
+    description: >
+      CSV with header "employee,category,amount,has_receipt,date"
+      (has_receipt is yes/no, date is YYYY-MM-DD).
+  category_limits_file:
+    default: "./expense-category-limits.csv"
+    description: >
+      CSV with header "category,limit" giving the max allowed amount per
+      category; categories not listed are treated as unlimited.
+  receipt_required_over:
+    default: 25
+    description: Require a receipt for any expense above this amount.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Zero-token. You export expense-reports.csv from whatever expense tool
+  you use (or fill it in by hand) — this doesn't connect to a live expense
+  platform.

package/jobs/finance/late-fee-interest-risk-check.yaml

@@ -0,0 +1,43 @@
+id: late-fee-interest-risk-check
+version: 1
+name: Late Fee & Interest Accrual Risk Check
+description: >
+  Estimates the dollar cost of leaving an overdue bill unpaid by
+  projecting late fees and accrued interest against its grace period.
+  Use this if you want to know what an overdue balance is actually
+  costing you, not just that it's overdue (see accounts-payable-aging-check
+  for the plain aging list).
+category: finance
+tags: [late-fees, interest, accounts-payable, finance]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  file={{payables_file}};
+  [ -f "$file" ] || { echo "ERROR: $file not found"; exit 1; };
+  today=$(date +%s);
+  tail -n +2 "$file" | while IFS=, read -r vendor amount due grace_days annual_rate_pct flat_fee paid; do
+    [ "$paid" = "yes" ] && continue;
+    due_epoch=$(date -j -f %Y-%m-%d "$due" +%s 2>/dev/null || date -d "$due" +%s);
+    days_over=$(( (today-due_epoch)/86400 ));
+    days_over_grace=$(( days_over - grace_days ));
+    if [ "$days_over_grace" -gt 0 ]; then
+      accrued=$(awk -v p="$amount" -v r="$annual_rate_pct" -v d="$days_over_grace" 'BEGIN{printf "%.2f", p*(r/100/365)*d}');
+      total_risk=$(awk -v a="$accrued" -v f="$flat_fee" 'BEGIN{printf "%.2f", a+f}');
+      echo "RISK: $vendor — \$$amount overdue, $days_over_grace day(s) past grace period, est. accrued cost so far: \$$total_risk (fee \$$flat_fee + interest \$$accrued)";
+    fi;
+  done
+variables:
+  payables_file:
+    default: "./late-fee-risk.csv"
+    description: >
+      CSV with header
+      "vendor,amount,due_date,grace_days,annual_rate_pct,flat_fee,paid"
+      — grace_days is the interest-free window after due_date,
+      annual_rate_pct is the penalty APR once grace expires, flat_fee is
+      a one-time late fee.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Zero-token, simple daily-accrual estimate (principal x rate/365 x
+  days) — not a substitute for the vendor/creditor's actual fee schedule,
+  which may compound or cap differently.

package/jobs/finance/loan-covenant-compliance-check.yaml

@@ -0,0 +1,37 @@
+id: loan-covenant-compliance-check
+version: 1
+name: Loan Covenant Compliance Check
+description: >
+  Computes financial ratios required by a loan agreement (e.g. debt
+  service coverage, current ratio) from your latest financials and flags
+  any that breach the covenant threshold. Use this if a lender requires
+  you to maintain certain ratios and a breach could trigger default or a
+  call on the loan.
+category: finance
+tags: [loan, covenants, ratios, finance]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  file={{financials_file}};
+  [ -f "$file" ] || { echo "ERROR: $file not found"; exit 1; };
+  tail -n +2 "$file" | while IFS=, read -r ratio_name value min_required max_allowed; do
+    breach="";
+    if [ -n "$min_required" ] && awk -v v="$value" -v m="$min_required" 'BEGIN{exit !(v+0 < m+0)}'; then breach="below minimum ($min_required)"; fi;
+    if [ -n "$max_allowed" ] && awk -v v="$value" -v m="$max_allowed" 'BEGIN{exit !(v+0 > m+0)}'; then breach="above maximum ($max_allowed)"; fi;
+    if [ -n "$breach" ]; then echo "COVENANT BREACH: $ratio_name = $value — $breach"; else echo "OK: $ratio_name = $value"; fi;
+  done
+variables:
+  financials_file:
+    default: "./loan-covenant-ratios.csv"
+    description: >
+      CSV with header "ratio_name,value,min_required,max_allowed" — one
+      row per covenant (leave min_required or max_allowed blank if that
+      side isn't part of the covenant). You compute/update the current
+      value each period from your financial statements.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Zero-token, pure comparison. You calculate each ratio's current value
+  yourself (e.g. DSCR, current ratio, debt-to-equity) from your
+  financial statements — this doesn't derive ratios from raw
+  balance-sheet/income-statement data.

package/jobs/finance/month-end-close-checklist-tracker.yaml

@@ -0,0 +1,39 @@
+id: month-end-close-checklist-tracker
+version: 1
+name: Month-End Close Checklist Tracker
+description: >
+  Tracks a list of month-end financial close tasks (reconcile bank,
+  post accruals, review AR/AP, close subledgers, etc.) and flags
+  incomplete items as the close deadline approaches. Use this if your
+  monthly close has ever slipped a step because nobody had a single
+  place tracking whether every task actually got done.
+category: finance
+tags: [month-end-close, checklist, bookkeeping, finance]
+schedule: "0 9 25 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  file={{checklist_file}}; close_day={{close_day_of_month}};
+  [ -f "$file" ] || { echo "ERROR: $file not found"; exit 1; };
+  today=$(date +%d);
+  incomplete=$(tail -n +2 "$file" | awk -F, '$2 != "done" {print}');
+  if [ -z "$incomplete" ]; then
+    echo "All month-end close tasks marked done.";
+  else
+    echo "INCOMPLETE close tasks (target close day: $close_day, today is day $today):";
+    echo "$incomplete" | awk -F, '{print "  - " $1 " (" $2 ")"}';
+  fi
+variables:
+  checklist_file:
+    default: "./month-end-close-checklist.csv"
+    description: >
+      CSV with header "task,status" (status is done/pending) — reset
+      status to pending for each task at the start of a new month.
+  close_day_of_month:
+    default: 5
+    description: Target day of the following month by which close should be finished (informational, shown in output).
+compatible_agents: [generic, claude, codex]
+notes: >
+  Zero-token. You maintain the checklist file and mark tasks done as you
+  complete them — this doesn't verify the underlying accounting work
+  itself, just whether each task is checked off.

package/jobs/finance/multi-account-cash-position-rollup.yaml

@@ -0,0 +1,45 @@
+id: multi-account-cash-position-rollup
+version: 1
+name: Multi-Account Cash Position Rollup
+description: >
+  Sums balances across multiple bank/cash accounts into one total
+  position and flags if the total or any single account drops below a
+  minimum threshold. Use this if cash is spread across several accounts
+  or entities and you want a single low-balance tripwire instead of
+  checking each account separately.
+category: finance
+tags: [cash, balances, multi-account, finance]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  file={{balances_file}}; min_total={{min_total_balance}}; min_account={{min_per_account_balance}};
+  [ -f "$file" ] || { echo "ERROR: $file not found"; exit 1; };
+  total=0;
+  tail -n +2 "$file" | while IFS=, read -r account balance; do
+    if awk -v b="$balance" -v m="$min_account" 'BEGIN{exit !(b+0 < m+0)}'; then
+      echo "LOW: $account balance \$$balance is below per-account minimum \$$min_account";
+    fi;
+  done;
+  total=$(tail -n +2 "$file" | awk -F, '{sum+=$2} END{printf "%.2f", sum}');
+  echo "TOTAL CASH POSITION: \$$total across $(tail -n +2 "$file" | wc -l | tr -d ' ') accounts";
+  if awk -v t="$total" -v m="$min_total" 'BEGIN{exit !(t+0 < m+0)}'; then
+    echo "WARNING: total cash position \$$total is below minimum \$$min_total";
+  fi
+variables:
+  balances_file:
+    default: "./account-balances.csv"
+    description: >
+      CSV with header "account,balance" — one row per account/entity,
+      updated manually or via bank export before each run.
+  min_total_balance:
+    default: 5000
+    description: Minimum acceptable combined cash position across all accounts.
+  min_per_account_balance:
+    default: 500
+    description: Minimum acceptable balance in any single account.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Zero-token. balances are a manual/exported snapshot, not a live bank
+  feed — refresh account-balances.csv before each run for accurate
+  results.

package/jobs/finance/petty-cash-float-reconciliation.yaml

@@ -0,0 +1,43 @@
+id: petty-cash-float-reconciliation
+version: 1
+name: Petty Cash Float Reconciliation
+description: >
+  Checks that a petty cash log's starting float minus logged expenses
+  plus replenishments matches the expected remaining balance, and flags
+  any variance. Use this if a physical cash box or float has ever come
+  up short (or over) and nobody could explain why.
+category: finance
+tags: [petty-cash, reconciliation, cash, finance]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  file={{petty_cash_log}}; expected_on_hand={{expected_on_hand}}; tolerance={{tolerance}};
+  [ -f "$file" ] || { echo "ERROR: $file not found"; exit 1; };
+  starting=$(head -2 "$file" | tail -1 | cut -d, -f2);
+  net=$(awk -F, 'NR>1 { if ($3=="expense") sum -= $2; else if ($3=="replenishment") sum += $2 } END {print sum+0}' "$file");
+  computed=$(awk -v s="$starting" -v n="$net" 'BEGIN{printf "%.2f", s+n}');
+  variance=$(awk -v c="$computed" -v e="$expected_on_hand" 'BEGIN{printf "%.2f", c-e}');
+  if awk -v v="$variance" -v t="$tolerance" 'BEGIN{v=(v<0?-v:v); exit !(v > t)}'; then
+    echo "VARIANCE: computed balance \$$computed vs. counted on-hand \$$expected_on_hand (diff \$$variance) — investigate";
+  else
+    echo "OK: computed balance \$$computed matches counted on-hand \$$expected_on_hand within \$$tolerance";
+  fi
+variables:
+  petty_cash_log:
+    default: "./petty-cash-log.csv"
+    description: >
+      CSV with header "date,amount,type,note" where type is
+      starting/expense/replenishment, first data row is the starting
+      float.
+  expected_on_hand:
+    default: 0
+    description: Actual counted cash currently in the box/float, entered manually after a physical count.
+  tolerance:
+    default: 5
+    description: Dollar variance allowed before flagging a discrepancy.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Zero-token. Requires a manual physical cash count entered as
+  expected_on_hand before each run — this doesn't track cash movement
+  automatically.

package/jobs/finance/quarterly-estimated-tax-calculator.yaml

@@ -0,0 +1,66 @@
+id: quarterly-estimated-tax-calculator
+version: 1
+name: Quarterly Estimated Tax Calculator
+description: >
+  Calculates a suggested quarterly estimated tax payment from your
+  logged year-to-date income and a target tax rate, and warns as the
+  next IRS-style quarterly due date approaches. Use this if you're
+  self-employed or have untaxed income and want the actual dollar
+  amount worked out, not just a bare date reminder (see
+  tax-deadline-reminder for a generic multi-jurisdiction deadline list).
+category: finance
+tags: [tax, estimated-tax, quarterly, finance]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  income_file={{income_ytd_csv}}; rate={{effective_tax_rate_pct}}; warn_days={{warn_days}};
+  [ -f "$income_file" ] || { echo "ERROR: $income_file not found"; exit 1; };
+  year=$(date +%Y);
+  ytd_income=$(awk -F, -v y="$year" 'NR>1 && $1 ~ "^"y"-" {sum+=$2} END{printf "%.2f", sum+0}' "$income_file");
+  owed=$(awk -v i="$ytd_income" -v r="$rate" 'BEGIN{printf "%.2f", i*(r/100)}');
+  echo "YTD income: \$$ytd_income | estimated tax owed so far ($rate%): \$$owed";
+  today=$(date +%s);
+  next_due="";
+  for d in {{q1_date}} {{q2_date}} {{q3_date}} {{q4_date}}; do
+    d_epoch=$(date -j -f %Y-%m-%d "$d" +%s 2>/dev/null || date -d "$d" +%s);
+    if [ "$d_epoch" -ge "$today" ]; then next_due="$d"; next_epoch="$d_epoch"; break; fi;
+  done;
+  if [ -n "$next_due" ]; then
+    days_left=$(( (next_epoch-today)/86400 ));
+    if [ "$days_left" -le "$warn_days" ]; then
+      echo "REMINDER: next estimated payment due $next_due (in $days_left day(s)) — suggested payment ~\$$owed based on YTD income";
+    else
+      echo "Next estimated payment due $next_due (in $days_left day(s))";
+    fi;
+  else
+    echo "No remaining estimated tax due dates configured for this year.";
+  fi
+variables:
+  income_ytd_csv:
+    default: "./income-log.csv"
+    description: "CSV with header \"date,amount\" (date YYYY-MM-DD) — one row per income event, self-employment or 1099 income."
+  effective_tax_rate_pct:
+    default: 25
+    description: Combined effective rate (federal + self-employment + state, as applicable) to apply to YTD income for an estimate.
+  q1_date:
+    default: "2026-04-15"
+    description: Q1 estimated payment due date for the current tax year.
+  q2_date:
+    default: "2026-06-15"
+    description: Q2 estimated payment due date.
+  q3_date:
+    default: "2026-09-15"
+    description: Q3 estimated payment due date.
+  q4_date:
+    default: "2027-01-15"
+    description: Q4 estimated payment due date.
+  warn_days:
+    default: 14
+    description: Days before the next due date to start showing the reminder line.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Zero-token, rough estimate only — not tax advice; confirm your actual
+  liability and safe-harbor rules with a tax professional. Default due
+  dates follow the typical US federal quarterly schedule; adjust for
+  your jurisdiction and update dates yearly.

package/jobs/finance/vendor-early-pay-discount-tracker.yaml

@@ -0,0 +1,45 @@
+id: vendor-early-pay-discount-tracker
+version: 1
+name: Vendor Early-Pay Discount Tracker
+description: >
+  Flags vendor invoices with an early-payment discount (like "2/10 net
+  30") whose discount window is about to close. Use this if you've ever
+  paid a bill on the regular due date and only afterward realized you
+  could've saved a couple percent by paying ten days earlier.
+category: finance
+tags: [accounts-payable, discounts, vendor-terms, finance]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  file={{payables_terms_file}}; warn_days={{warn_days}};
+  [ -f "$file" ] || { echo "ERROR: $file not found"; exit 1; };
+  today=$(date +%s);
+  tail -n +2 "$file" | while IFS=, read -r vendor amount invoice_date discount_pct discount_days paid; do
+    [ "$paid" = "yes" ] && continue;
+    [ -z "$discount_days" ] && continue;
+    inv_epoch=$(date -j -f %Y-%m-%d "$invoice_date" +%s 2>/dev/null || date -d "$invoice_date" +%s);
+    window_epoch=$(( inv_epoch + discount_days*86400 ));
+    days_left=$(( (window_epoch-today)/86400 ));
+    if [ "$days_left" -ge 0 ] && [ "$days_left" -le "$warn_days" ]; then
+      savings=$(awk -v a="$amount" -v p="$discount_pct" 'BEGIN{printf "%.2f", a*(p/100)}');
+      echo "DISCOUNT WINDOW CLOSING: $vendor invoice \$$amount — pay within $days_left day(s) to save \$$savings ($discount_pct% discount)";
+    fi;
+  done
+variables:
+  payables_terms_file:
+    default: "./vendor-payment-terms.csv"
+    description: >
+      CSV with header
+      "vendor,amount,invoice_date,discount_pct,discount_days,paid"
+      (invoice_date is YYYY-MM-DD; discount_days is how many days from
+      invoice_date the early-pay discount applies, e.g. 10 for "2/10 net
+      30"; leave discount_pct/discount_days blank if no early-pay term
+      exists).
+  warn_days:
+    default: 3
+    description: Start warning this many days before the discount window closes.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Zero-token. You maintain vendor-payment-terms.csv from vendor
+  invoices/contracts — this doesn't parse invoice terms automatically.

package/jobs/healthcare/appointment-slot-utilization-check.yaml

@@ -0,0 +1,56 @@
+id: appointment-slot-utilization-check
+version: 1
+name: Appointment Slot Utilization and Schedule Gap Check
+description: >
+  Computes daily/weekly appointment slot utilization from the schedule and
+  flags days running well under capacity, then suggests what to do about
+  the gaps. Use this if provider schedules have ever had large unbooked
+  gaps that nobody noticed until the day arrived nearly empty, wasting
+  billable capacity that a recall push or same-day-opening alert could
+  have filled.
+category: healthcare
+tags: [healthcare, scheduling, utilization, operations, capacity]
+schedule: "0 16 * * 5"
+timezone: "America/New_York"
+runner: hybrid
+command: >
+  awk -F',' -v threshold="{{low_utilization_threshold_pct}}" '
+    NR==1 {next}
+    {
+      total += $2; booked += $3;
+      pct = ($2 > 0) ? ($3 / $2 * 100) : 0;
+      if (pct < threshold) {
+        printf "LOW UTILIZATION: %s — %d/%d slots booked (%.1f%%)\n", $1, $3, $2, pct;
+      }
+    }
+    END {
+      overall = (total > 0) ? (booked / total * 100) : 0;
+      printf "WEEK OVERALL: %d/%d slots booked (%.1f%%)\n", booked, total, overall;
+    }
+  ' "{{schedule_utilization_csv_path}}"
+prompt: |
+  Look at the low-utilization days and overall weekly rate flagged above
+  (from {{schedule_utilization_csv_path}}).
+  1. Note which specific days/providers are consistently under
+     {{low_utilization_threshold_pct}}% booked versus a one-off dip.
+  2. For consistently low days, suggest a concrete fix: a targeted recall
+     push (see patient-recall-reminder) for that provider's open slots, a
+     schedule consolidation (fewer open days, more density), or a same-day
+     opening alert to a waitlist — whichever fits the pattern.
+  3. Keep it to a short, actionable list — this is a capacity-planning
+     nudge, not a full operations review.
+variables:
+  schedule_utilization_csv_path:
+    default: "./schedule-utilization.csv"
+    description: "Path to a CSV with columns: date_or_provider_day,total_slots,booked_slots."
+  low_utilization_threshold_pct:
+    default: 70
+    description: Utilization percentage below which a day is flagged as under capacity.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+script_note: >
+  The command gives you the per-day and weekly utilization percentages for free.
+  Only the prompt pass distinguishes a one-off dip from a real pattern and
+  recommends a specific fix — that judgment call is what the LLM pass adds.
+notes: >
+  Assumes an already-exported CSV from your scheduling/practice-management system.
+  Read-only analysis — it doesn't rebook anyone or change the schedule itself.

package/jobs/healthcare/claims-denial-resubmission-check.yaml

@@ -0,0 +1,43 @@
+id: claims-denial-resubmission-check
+version: 1
+name: Claims Denial Resubmission Check
+description: >
+  Checks denied insurance claims against their payer resubmission or appeal
+  deadline and flags anything still open as the deadline approaches or has
+  already passed. Use this if a denied claim has ever quietly aged past the
+  window to resubmit or appeal it, turning recoverable revenue into a
+  write-off nobody meant to take.
+category: healthcare
+tags: [healthcare, billing, claims, denials, revenue-cycle]
+schedule: "0 8 * * 1-5"
+timezone: "America/New_York"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v warn_days="{{warn_days_before_deadline}}" '
+    NR==1 {next}
+    $6 != "open" {next}
+    {
+      cmd = "date -d \"" $5 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $5 "\" +%s 2>/dev/null";
+      cmd | getline deadline_epoch; close(cmd);
+      diff_days = (deadline_epoch - today) / 86400;
+      if (diff_days < 0) {
+        printf "PAST DEADLINE: %s — claim %s (%s) resubmission deadline was %s (%d days ago)\n", $1, $2, $3, $5, -diff_days;
+      } else if (diff_days <= warn_days) {
+        printf "RESUBMIT SOON: %s — claim %s (%s) deadline %s (%d days left)\n", $1, $2, $3, $5, diff_days;
+      }
+    }
+  ' "{{denied_claims_csv_path}}"
+variables:
+  denied_claims_csv_path:
+    default: "./denied-claims.csv"
+    description: "Path to a CSV with columns: patient_name,claim_number,payer,denial_date (YYYY-MM-DD),resubmission_deadline (YYYY-MM-DD),status (open/resubmitted/appealed/written-off)."
+  warn_days_before_deadline:
+    default: 7
+    description: How many days before the resubmission/appeal deadline to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Assumes an already-exported CSV from your billing/clearinghouse system rather than
+  live PHI system access. Distinct from insurance-eligibility-verification-check
+  (pre-visit) and prior-authorization-expiry-check (treatment approval) — this is
+  post-visit claims that already got denied.