@wonsukchoi/crondex 0.6.0 → 0.8.0

package/jobs/finance/recurring-payment-failure-check.yaml

@@ -0,0 +1,23 @@
+id: recurring-payment-failure-check
+version: 1
+name: Recurring Payment Failure Check
+description: >
+  Flags subscription charges that failed and haven't successfully retried
+  yet. Use this if a failed card has ever silently churned a customer
+  because nobody noticed the retry never succeeded.
+category: finance
+tags: [finance, billing, payments]
+schedule: "0 */6 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  psql "{{database_url}}" -t -c "select customer_email, amount, failed_at, retry_count from subscription_charges where status = 'failed' and retry_count >= {{max_retries}};"
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the billing database.
+  max_retries:
+    default: 2
+    description: Retry count at or above which a failed charge is flagged for manual follow-up.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a `subscription_charges` table with `status`, `retry_count`, and `failed_at` columns — adjust the query to your billing provider's schema or webhook log.

package/jobs/fleet/fuel-card-anomaly-check.yaml

@@ -0,0 +1,37 @@
+id: fuel-card-anomaly-check
+version: 1
+name: Fuel Card Anomaly Check
+description: >
+  Flags fuel card transactions that look unusual (too large, too frequent,
+  or outside normal hours/locations). Use this if fuel card misuse has
+  ever gone unnoticed until the monthly statement showed up.
+category: fleet
+tags: [fleet, fuel-card, fraud]
+schedule: "0 7 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review fuel card transactions from {{fuel_card_provider_hint}} for the
+  last 24 hours.
+  1. Flag transactions over {{max_transaction_usd}} USD.
+  2. Flag more than {{max_daily_transactions}} transactions on the same
+     card in one day.
+  3. Flag transactions outside typical operating hours ({{operating_hours}})
+     if timestamps are available.
+  4. Report flagged transactions with card holder, amount, time, and
+     location.
+variables:
+  fuel_card_provider_hint:
+    default: "your fuel card provider (WEX, Fuelman, etc.)"
+    description: Name of the fuel card provider/portal.
+  max_transaction_usd:
+    default: 150
+    description: Single-transaction amount that triggers a flag.
+  max_daily_transactions:
+    default: 2
+    description: Transactions per card per day that triggers a flag.
+  operating_hours:
+    default: "06:00-19:00"
+    description: Normal operating hours; transactions outside this window are flagged.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — fuel card provider APIs/exports vary and flagging patterns benefits from judgment, not just fixed rules.

package/jobs/fleet/vehicle-maintenance-due-check.yaml

@@ -0,0 +1,36 @@
+id: vehicle-maintenance-due-check
+version: 1
+name: Fleet Vehicle Maintenance Due Check
+description: >
+  Flags fleet vehicles due for scheduled maintenance by date or mileage.
+  Use this if a fleet vehicle has ever broken down on a job because its
+  service interval quietly passed.
+category: fleet
+tags: [fleet, vehicles, maintenance]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" -v warn_days={{warn_days}} -v warn_miles={{warn_miles}} '
+    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);
+      miles_left = $4 - $3;
+      if (days_left <= warn_days || miles_left <= warn_miles)
+        print "WARNING: vehicle " $1 " due in " days_left " days or " miles_left " miles (service due " $2 " / " $4 " mi)";
+    }
+  ' {{fleet_csv}}
+variables:
+  fleet_csv:
+    default: "fleet-maintenance.csv"
+    description: "CSV with header row, columns: vehicle_id,next_service_date(YYYY-MM-DD),current_mileage,next_service_mileage."
+  warn_days:
+    default: 14
+    description: Days before the service date to start warning.
+  warn_miles:
+    default: 500
+    description: Miles remaining before the service mileage to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Keep fleet-maintenance.csv updated from odometer readings/telematics exports before each run.

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/candidate-followup-nudge.yaml

@@ -0,0 +1,23 @@
+id: candidate-followup-nudge
+version: 1
+name: Candidate Follow-up Nudge
+description: >
+  Flags interviewed candidates who haven't heard back in a while. Use this
+  if candidates have ever gone quiet after a final interview simply
+  because nobody circled back with a decision.
+category: hiring
+tags: [hiring, recruiting, candidates]
+schedule: "0 9 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  psql "{{database_url}}" -t -c "select name, stage, last_interview_at from candidates where stage not in ('hired','rejected') and last_interview_at < now() - interval '{{stale_days}} days';"
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the candidates/ATS database.
+  stale_days:
+    default: 7
+    description: Days since last interview before a candidate is flagged for follow-up.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a `candidates` table with `stage` and `last_interview_at` columns — adjust the query to your ATS's schema or export.

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/hiring/open-req-aging-check.yaml

@@ -0,0 +1,31 @@
+id: open-req-aging-check
+version: 1
+name: Open Req Aging Check
+description: >
+  Flags job requisitions that have been open too long without enough
+  candidates in the pipeline. Use this if a req has ever sat open for
+  months before anyone asked why it wasn't moving.
+category: hiring
+tags: [hiring, recruiting, requisitions]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review open job requisitions in {{ats_hint}}.
+  1. For each req open more than {{stale_days}} days, note days open and
+     current candidate count by stage.
+  2. Flag reqs with fewer than {{min_candidates}} active candidates as
+     needing sourcing attention.
+  3. Report the list ranked by days open, oldest first.
+variables:
+  ats_hint:
+    default: "your ATS (Greenhouse, Lever, Ashby)"
+    description: Name of the applicant tracking system in use.
+  stale_days:
+    default: 45
+    description: Days open before a req is flagged for review.
+  min_candidates:
+    default: 3
+    description: Minimum active candidates expected before a req is considered healthy.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — ATS APIs vary widely and most need OAuth the agent may not have configured.

package/jobs/home/warranty-expiry-reminder.yaml

@@ -0,0 +1,31 @@
+id: warranty-expiry-reminder
+version: 1
+name: Warranty Expiry Reminder
+description: >
+  Warns you before an appliance or product warranty expires. Use this if
+  you've ever discovered a warranty lapsed the week before whatever it
+  covered broke.
+category: home
+tags: [home, warranty, reminder]
+schedule: "0 9 1 * *"
+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 exp_ts; close(cmd);
+      days_left = int((exp_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: warranty for \"" $1 "\" expires in " days_left " days (" $2 ")";
+    }
+  ' {{warranties_csv}}
+variables:
+  warranties_csv:
+    default: "warranties.csv"
+    description: "CSV with header row, columns: item_name,expiry_date(YYYY-MM-DD)."
+  warn_days:
+    default: 30
+    description: Days before expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Keep warranties.csv updated whenever you buy something worth tracking — add the receipt/warranty end date at purchase time.

package/jobs/hospitality/food-safety-temp-log-check.yaml

@@ -0,0 +1,36 @@
+id: food-safety-temp-log-check
+version: 1
+name: Food Safety Temperature Log Check
+description: >
+  Checks that fridge/freezer temperature logs were actually recorded
+  today and flags any reading outside the safe range. Use this if a
+  temperature log has ever gone unfilled for a shift, or a unit drifted
+  out of range without anyone noticing until the food was already at risk.
+category: hospitality
+tags: [hospitality, food-safety, compliance]
+schedule: "0 */4 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%Y-%m-%d);
+  last_entry=$(awk -F, -v today="$today" '$1 ~ today {last=$0} END {print last}' {{temp_log_csv}});
+  if [ -z "$last_entry" ]; then echo "WARNING: no temperature log entry today for {{unit_name}}"; exit 1; fi;
+  temp=$(echo "$last_entry" | cut -d, -f3);
+  if awk "BEGIN{exit !($temp > {{max_temp_f}} || $temp < {{min_temp_f}})}"; then
+    echo "WARNING: {{unit_name}} reading ${temp}F is out of range ({{min_temp_f}}-{{max_temp_f}}F): $last_entry"; exit 1;
+  else echo "OK: {{unit_name}} last reading ${temp}F, in range"; fi
+variables:
+  unit_name:
+    default: "walk-in cooler"
+    description: Name of the unit being logged.
+  temp_log_csv:
+    default: "temp-log.csv"
+    description: "CSV with columns: date(YYYY-MM-DD HH:MM),unit,temp_f."
+  min_temp_f:
+    default: 33
+    description: Minimum safe temperature in Fahrenheit.
+  max_temp_f:
+    default: 40
+    description: Maximum safe temperature in Fahrenheit.
+compatible_agents: [generic, claude, codex]
+notes: Assumes manual or IoT-exported entries appended to temp-log.csv throughout the day — one job instance per unit tracked.

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/hospitality/reservation-noshow-check.yaml

@@ -0,0 +1,20 @@
+id: reservation-noshow-check
+version: 1
+name: Reservation No-show Check
+description: >
+  Checks yesterday's no-show rate against your normal baseline and flags a
+  spike. Use this if a run of no-shows has ever quietly hurt revenue for
+  days before anyone connected the pattern.
+category: hospitality
+tags: [hospitality, reservations, noshow]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  psql "{{database_url}}" -t -c "select round(100.0 * sum(case when status = 'no_show' then 1 else 0 end) / count(*), 1) from reservations where reservation_date = current_date - interval '1 day';"
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the reservations database.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a `reservations` table with `status` and `reservation_date` columns — adjust the query for your reservation system's schema; compare the printed rate against your normal baseline manually.

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/inventory/inventory-count-discrepancy-check.yaml

@@ -0,0 +1,38 @@
+id: inventory-count-discrepancy-check
+version: 1
+name: Inventory Count Discrepancy Check
+description: >
+  Compares a physical inventory count against system records and flags
+  mismatches worth investigating. Use this if shrinkage or data entry
+  errors have ever gone unnoticed until a full audit months later.
+category: inventory
+tags: [inventory, audit, discrepancy]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Compare the physical count file at {{physical_count_file}} against
+  system inventory records (query {{database_url}} or the inventory
+  system).
+  1. For each SKU, compute the difference between physical and system
+     quantity.
+  2. Flag any SKU with a discrepancy of {{threshold_units}} units or more,
+     or {{threshold_pct}}% of system quantity, whichever is smaller.
+  3. Report flagged SKUs ranked by discrepancy size, with a guess at
+     likely cause if the pattern suggests one (e.g. consistent
+     under-count of one category = possible shrinkage).
+variables:
+  physical_count_file:
+    default: "physical-count.csv"
+    description: CSV export of the physical count, columns sku,quantity.
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the system inventory database.
+  threshold_units:
+    default: 5
+    description: Absolute unit discrepancy that triggers a flag.
+  threshold_pct:
+    default: 10
+    description: Percent discrepancy that triggers a flag.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — matching two data sources and judging what's a meaningful discrepancy needs an agent, not a fixed query.

package/jobs/inventory/low-stock-alert.yaml

@@ -0,0 +1,20 @@
+id: low-stock-alert
+version: 1
+name: Low Stock Alert
+description: >
+  Checks inventory levels against a reorder point and flags SKUs running
+  low. Use this if you've ever gone out of stock on a bestseller because
+  nobody was watching the count.
+category: inventory
+tags: [inventory, stock, ecommerce]
+schedule: "0 7 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  psql "{{database_url}}" -t -c "select sku, quantity, reorder_point from inventory where quantity <= reorder_point;"
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the inventory database.
+compatible_agents: [generic, claude, codex]
+notes: Assumes an `inventory` table with `sku`, `quantity`, and `reorder_point` columns — adjust the query to your schema.

package/jobs/investing/crypto-price-alert.yaml

@@ -0,0 +1,33 @@
+id: crypto-price-alert
+version: 1
+name: Crypto Price Alert
+description: >
+  Checks a crypto asset's price and alerts when it crosses a threshold you
+  set. Use this if you're waiting for a price target and don't want to
+  keep a tab open all day watching a chart.
+category: investing
+tags: [crypto, price, alert]
+schedule: "*/15 * * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  price=$(curl -s "https://api.coingecko.com/api/v3/simple/price?ids={{coin_id}}&vs_currencies={{vs_currency}}" | grep -o '[0-9.]*' | head -n1);
+  if [ -z "$price" ]; then echo "ERROR: could not fetch price for {{coin_id}}"; exit 1; fi;
+  if awk "BEGIN{exit !($price {{comparison}} {{target_price}})}"; then
+    echo "ALERT: {{coin_id}} is $price {{vs_currency}} ({{comparison}} {{target_price}})";
+  else echo "OK: {{coin_id}} is $price {{vs_currency}}"; fi
+variables:
+  coin_id:
+    default: "bitcoin"
+    description: CoinGecko coin id (e.g. bitcoin, ethereum).
+  vs_currency:
+    default: "usd"
+    description: Currency to price against.
+  target_price:
+    default: 50000
+    description: Threshold price to compare against.
+  comparison:
+    default: ">="
+    description: "Comparison operator for triggering the alert: <=, >=, <, or >."
+compatible_agents: [generic, claude, codex]
+notes: Uses the free CoinGecko public API, no key required; rate-limited so avoid scheduling much tighter than every few minutes.

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/investing/portfolio-rebalance-check.yaml

@@ -0,0 +1,32 @@
+id: portfolio-rebalance-check
+version: 1
+name: Portfolio Rebalance Check
+description: >
+  Compares your current asset allocation to your target and flags drift
+  worth rebalancing. Use this if your portfolio only gets rebalanced
+  whenever you happen to remember to look.
+category: investing
+tags: [investing, portfolio, rebalancing]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check current portfolio allocation against the target allocation below.
+  Target: {{target_allocation}}
+  1. Pull current balances/allocation from {{brokerage_hint}} (or ask the
+     user for current values if no direct access).
+  2. Compute drift per asset class vs. target.
+  3. Flag any class drifted more than {{drift_threshold_pct}} percentage
+     points, and suggest the trade(s) to rebalance back.
+variables:
+  target_allocation:
+    default: "60% stocks / 30% bonds / 10% cash"
+    description: Your target allocation across asset classes.
+  brokerage_hint:
+    default: "your brokerage account"
+    description: Where portfolio balances live.
+  drift_threshold_pct:
+    default: 5
+    description: Percentage-point drift from target that triggers a rebalance flag.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — brokerage APIs vary widely and most require OAuth the agent may not have configured.

package/jobs/legal/contract-renewal-reminder.yaml

@@ -0,0 +1,31 @@
+id: contract-renewal-reminder
+version: 1
+name: Contract Renewal Reminder
+description: >
+  Warns you before a vendor or customer contract auto-renews or expires.
+  Use this if a contract has ever auto-renewed for another year because
+  nobody flagged the cancellation window in time.
+category: legal
+tags: [legal, contracts, 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 \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline renew_ts; close(cmd);
+      days_left = int((renew_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: " $1 " renews/expires in " days_left " days (" $2 ")";
+    }
+  ' {{contracts_csv}}
+variables:
+  contracts_csv:
+    default: "contracts.csv"
+    description: "CSV with header row, columns: name,renewal_date(YYYY-MM-DD)."
+  warn_days:
+    default: 30
+    description: Days before renewal/expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Keep contracts.csv updated manually or export it from your contract management tool before each run.

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/legal/trademark-renewal-reminder.yaml

@@ -0,0 +1,30 @@
+id: trademark-renewal-reminder
+version: 1
+name: Trademark Renewal Reminder
+description: >
+  Warns you before a trademark registration's renewal deadline. Use this
+  if you've ever let a trademark lapse simply because the renewal date
+  wasn't on anyone's calendar.
+category: legal
+tags: [legal, trademark, ip]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  due_ts=$(date -d "{{renewal_date}}" +%s 2>/dev/null || date -jf "%Y-%m-%d" "{{renewal_date}}" +%s);
+  days_left=$(( (due_ts - today) / 86400 ));
+  if [ "$days_left" -le "{{warn_days}}" ]; then echo "WARNING: trademark {{mark_name}} renewal due in $days_left days ({{renewal_date}})"; exit 1;
+  else echo "OK: trademark {{mark_name}} renewal due in $days_left days"; fi
+variables:
+  mark_name:
+    default: "your trademark"
+    description: Name/identifier of the trademark to track.
+  renewal_date:
+    default: "2027-01-01"
+    description: Renewal deadline date (YYYY-MM-DD).
+  warn_days:
+    default: 90
+    description: Days before deadline to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Manual renewal_date input — update after each renewal cycle; run one copy per registered mark/jurisdiction.

package/jobs/logistics/customs-clearance-check.yaml

@@ -0,0 +1,34 @@
+id: customs-clearance-check
+version: 1
+name: Customs Clearance Check
+description: >
+  Flags a shipment that's been sitting in customs longer than expected.
+  Use this if a shipment has ever been stuck at the border for weeks
+  before anyone thought to follow up with the broker.
+category: logistics
+tags: [logistics, customs, shipping]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check the customs clearance status of shipment {{shipment_id}} via
+  {{tracking_source_hint}}.
+  1. Determine how long it's been in a "customs hold" or equivalent
+     status.
+  2. If it's been more than {{warn_days}} days, flag it and note any
+     stated reason for the hold (missing documents, duties owed,
+     inspection) if visible.
+  3. Suggest the next action (contact broker, pay duties, provide
+     documents) based on the reason if known.
+variables:
+  shipment_id:
+    default: "your-shipment-id"
+    description: Shipment/tracking identifier to check.
+  tracking_source_hint:
+    default: "carrier tracking page or customs broker portal"
+    description: Where to check customs status for this shipment.
+  warn_days:
+    default: 5
+    description: Days in customs hold before it's flagged.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — customs status pages/APIs vary by carrier and broker, and reason codes need interpretation.