@wonsukchoi/crondex 0.5.0 → 0.7.0

package/jobs/events/vendor-payment-deadline-reminder.yaml

@@ -0,0 +1,31 @@
+id: vendor-payment-deadline-reminder
+version: 1
+name: Event Vendor Payment Deadline Reminder
+description: >
+  Warns you before a vendor deposit or balance payment for an event is
+  due. Use this if a vendor has ever threatened to cancel because a
+  payment deadline slipped past unnoticed.
+category: events
+tags: [events, vendors, payments]
+schedule: "0 9 * * *"
+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 && days_left >= 0) print "WARNING: payment to \"" $1 "\" (" $3 ") due in " days_left " days (" $2 ")";
+    }
+  ' {{vendor_payments_csv}}
+variables:
+  vendor_payments_csv:
+    default: "vendor-payments.csv"
+    description: "CSV with header row, columns: vendor_name,due_date(YYYY-MM-DD),amount."
+  warn_days:
+    default: 7
+    description: Days before due date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Keep vendor-payments.csv updated as contracts are signed — one row per deposit/balance milestone.

package/jobs/finance/budget-overspend-check.yaml

@@ -0,0 +1,29 @@
+id: budget-overspend-check
+version: 1
+name: Budget Overspend Check
+description: >
+  Compares this month's spend in a budget category against your limit and
+  warns if you're over. Use this if you set budgets once and then never
+  actually check them until the month's already blown.
+category: finance
+tags: [budget, spending, finance]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  spent=$(awk -F, -v month="$(date +%Y-%m)" -v cat="{{category}}" '$1 ~ month && $2 == cat {sum += $3} END {print sum+0}' {{transactions_csv}});
+  limit={{budget_limit}};
+  if awk "BEGIN{exit !($spent >= $limit)}"; then echo "WARNING: {{category}} spend \$$spent has hit/exceeded budget \$$limit this month"; exit 1;
+  else echo "OK: {{category}} spend \$$spent, budget \$$limit"; fi
+variables:
+  transactions_csv:
+    default: "transactions.csv"
+    description: "CSV of transactions with columns: date(YYYY-MM-DD),category,amount."
+  category:
+    default: "dining"
+    description: Budget category to check.
+  budget_limit:
+    default: 300
+    description: Monthly budget limit for this category, in your currency.
+compatible_agents: [generic, claude, codex]
+notes: Expects a plain CSV export; point transactions_csv at wherever your bank/budgeting tool exports to.

package/jobs/finance/fx-rate-watch.yaml

@@ -0,0 +1,33 @@
+id: fx-rate-watch
+version: 1
+name: FX Rate Watch
+description: >
+  Checks a currency pair's exchange rate and alerts when it crosses a
+  threshold you set. Use this if you're timing a transfer, payment, or
+  purchase around a favorable rate and don't want to check manually every day.
+category: finance
+tags: [finance, currency, fx]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  rate=$(curl -s "https://api.exchangerate.host/latest?base={{from_currency}}&symbols={{to_currency}}" | grep -o '"{{to_currency}}":[0-9.]*' | cut -d: -f2);
+  if [ -z "$rate" ]; then echo "ERROR: could not fetch rate for {{from_currency}}/{{to_currency}}"; exit 1; fi;
+  if awk "BEGIN{exit !($rate {{comparison}} {{target_rate}})}"; then
+    echo "ALERT: {{from_currency}}/{{to_currency}} is $rate ({{comparison}} {{target_rate}})";
+  else echo "OK: {{from_currency}}/{{to_currency}} is $rate"; fi
+variables:
+  from_currency:
+    default: "USD"
+    description: Base currency code.
+  to_currency:
+    default: "EUR"
+    description: Target currency code.
+  target_rate:
+    default: 0.95
+    description: Threshold rate to compare against.
+  comparison:
+    default: "<="
+    description: "Comparison operator for triggering the alert: <=, >=, <, or >."
+compatible_agents: [generic, claude, codex]
+notes: Uses the free exchangerate.host API; swap in another FX API if you need higher rate limits or historical accuracy.

package/jobs/finance/payroll-run-reminder.yaml

@@ -0,0 +1,27 @@
+id: payroll-run-reminder
+version: 1
+name: Payroll Run Reminder
+description: >
+  Warns you before the payroll submission deadline so employees actually
+  get paid on time. Use this if payroll has ever run late because the
+  submission cutoff snuck up during a busy week.
+category: finance
+tags: [finance, payroll, deadlines]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  cutoff_ts=$(date -d "{{next_cutoff_date}}" +%s 2>/dev/null || date -jf "%Y-%m-%d" "{{next_cutoff_date}}" +%s);
+  days_left=$(( (cutoff_ts - today) / 86400 ));
+  if [ "$days_left" -le "{{warn_days}}" ] && [ "$days_left" -ge 0 ]; then echo "WARNING: payroll submission cutoff in $days_left days ({{next_cutoff_date}})"; exit 1;
+  else echo "OK: payroll submission cutoff in $days_left days"; fi
+variables:
+  next_cutoff_date:
+    default: "2026-08-01"
+    description: Next payroll submission cutoff date (YYYY-MM-DD).
+  warn_days:
+    default: 2
+    description: Days before the cutoff to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Manual next_cutoff_date input — update it each pay cycle, or generate a recurring schedule externally if your payroll provider uses a fixed cadence.

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/growth/churn-risk-watch.yaml

@@ -0,0 +1,33 @@
+id: churn-risk-watch
+version: 1
+name: Churn Risk Watch
+description: >
+  Flags accounts whose usage has dropped off sharply, before they actually
+  cancel. Use this if you only ever find out someone churned after the
+  cancellation email arrives.
+category: growth
+tags: [growth, churn, retention]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review usage/activity data (from {{analytics_hint}} or the database) for
+  paying accounts.
+  1. Compare each account's activity in the last {{recent_days}} days to
+     their prior baseline.
+  2. Flag accounts with a drop of {{drop_threshold_pct}}% or more as churn
+     risks.
+  3. Report the flagged accounts ranked by drop size, with their plan
+     value, so outreach can be prioritized.
+variables:
+  analytics_hint:
+    default: "product analytics tool (e.g. Mixpanel, PostHog, Amplitude)"
+    description: Where usage/activity data lives.
+  recent_days:
+    default: 14
+    description: Recent window to compare against baseline.
+  drop_threshold_pct:
+    default: 50
+    description: Percent drop in activity that counts as churn risk.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — "baseline vs. recent activity" needs querying an analytics source and judgment on what counts as a meaningful drop.

package/jobs/growth/trial-expiring-nudge.yaml

@@ -0,0 +1,33 @@
+id: trial-expiring-nudge
+version: 1
+name: Trial Expiring Nudge
+description: >
+  Finds trial users about to expire who haven't upgraded yet, and can
+  draft the nudge email. Use this if trial-to-paid conversion nudges only
+  happen when someone remembers to send them.
+category: growth
+tags: [growth, trials, conversion]
+schedule: "0 10 * * *"
+timezone: "UTC"
+runner: hybrid
+command: >
+  psql "{{database_url}}" -t -c "select email, trial_ends_at from users where trial_ends_at between now() and now() + interval '{{lookahead_days}} days' and plan = 'trial';"
+prompt: |
+  Find users whose trial ends within the next {{lookahead_days}} days and
+  who haven't upgraded to a paid plan (query {{database_url}} or the
+  billing system).
+  1. List each user with their trial end date.
+  2. Draft a short, friendly nudge email for each, mentioning what they'd
+     lose access to and a clear upgrade link. Don't send — draft only.
+script_note: >
+  `command` lists trial-ending users from Postgres with zero tokens.
+  `prompt` also drafts the nudge email per user, which needs an LLM.
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the users/billing database.
+  lookahead_days:
+    default: 3
+    description: How many days ahead to look for trial expirations.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Script mode assumes a `users` table with `trial_ends_at` and `plan` columns — adjust the query to your schema.

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/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/car-maintenance-due-reminder.yaml

@@ -0,0 +1,30 @@
+id: car-maintenance-due-reminder
+version: 1
+name: Car Maintenance Due Reminder
+description: >
+  Warns you when a car maintenance task (oil change, registration, etc.)
+  is coming due by date. Use this if you've ever found out your
+  registration expired because a sticker in the mail got ignored.
+category: home
+tags: [home, car, maintenance]
+schedule: "0 9 * * 1"
+timezone: "America/Los_Angeles"
+runner: shell
+command: >
+  today=$(date +%s);
+  due_ts=$(date -d "{{due_date}}" +%s 2>/dev/null || date -jf "%Y-%m-%d" "{{due_date}}" +%s);
+  days_left=$(( (due_ts - today) / 86400 ));
+  if [ "$days_left" -le "{{warn_days}}" ]; then echo "WARNING: {{task_name}} due in $days_left days ({{due_date}})"; exit 1;
+  else echo "OK: {{task_name}} due in $days_left days"; fi
+variables:
+  task_name:
+    default: "oil change"
+    description: Name of the maintenance task to track.
+  due_date:
+    default: "2026-09-01"
+    description: Date the task is due (YYYY-MM-DD).
+  warn_days:
+    default: 7
+    description: Days before due date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: One task per job instance — schedule multiple copies with different task_name/due_date for oil change, registration, inspection, etc.

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/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/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/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/learning/cert-renewal-reminder.yaml

@@ -0,0 +1,30 @@
+id: cert-renewal-reminder
+version: 1
+name: Professional Certification Renewal Reminder
+description: >
+  Warns you before a professional certification expires or its renewal
+  window opens. Use this if you've ever let a cert lapse and had to retake
+  an exam that a renewal course would've avoided.
+category: learning
+tags: [learning, certification, renewal]
+schedule: "0 9 1 * *"
+timezone: "America/Los_Angeles"
+runner: shell
+command: >
+  today=$(date +%s);
+  expiry_ts=$(date -d "{{expiry_date}}" +%s 2>/dev/null || date -jf "%Y-%m-%d" "{{expiry_date}}" +%s);
+  days_left=$(( (expiry_ts - today) / 86400 ));
+  if [ "$days_left" -le "{{warn_days}}" ]; then echo "WARNING: {{cert_name}} expires in $days_left days ({{expiry_date}})"; exit 1;
+  else echo "OK: {{cert_name}} expires in $days_left days"; fi
+variables:
+  cert_name:
+    default: "your certification"
+    description: Name of the certification to track.
+  expiry_date:
+    default: "2027-01-01"
+    description: Certification expiry date (YYYY-MM-DD).
+  warn_days:
+    default: 60
+    description: Days before expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Manual expiry_date input — update after each renewal cycle.