@wonsukchoi/crondex 0.11.0 → 0.13.0

package/jobs/hr/performance-review-cycle-reminder.yaml

@@ -0,0 +1,34 @@
+id: performance-review-cycle-reminder
+version: 1
+name: Performance Review Cycle Reminder
+description: >
+  Tracks the performance review cycle deadline and flags managers who
+  haven't submitted reviews yet as the deadline approaches. Use this if a
+  review cycle has ever closed with a chunk of reviews still missing
+  because nobody chased the stragglers until HR asked.
+category: hr
+tags: [hr, performance-review, reminder, deadline]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check {{hris_system}} for the current performance review cycle, due
+  {{cycle_deadline}}.
+  1. Report days remaining until the deadline.
+  2. List managers who haven't submitted reviews for their direct reports
+     yet, with how many are outstanding.
+  3. If within {{final_warn_days}} days of the deadline, draft an urgent
+     reminder to each manager still missing reviews.
+  4. If the deadline has passed, report final completion rate instead.
+variables:
+  hris_system:
+    default: "your HRIS/performance management system"
+    description: Name of the system to check (e.g. "Lattice", "15Five", "Workday").
+  cycle_deadline:
+    default: "YYYY-MM-DD"
+    description: Date the current review cycle closes.
+  final_warn_days:
+    default: 5
+    description: Days before deadline to switch from routine reminders to urgent ones.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — review reminder messages before sending, especially the "urgent" framing near the deadline.

package/jobs/insurance/certificate-of-insurance-request-check.yaml

@@ -0,0 +1,38 @@
+id: certificate-of-insurance-request-check
+version: 1
+name: Certificate of Insurance Request Check
+description: >
+  Checks for incoming certificate-of-insurance (COI) requests from
+  vendors, clients, or landlords that haven't been fulfilled yet. Use this
+  if a COI request has ever sat unanswered long enough to hold up a
+  contract or a lease signing.
+category: insurance
+tags: [insurance, coi, compliance, requests]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{escalate_after_days}}" '
+    NR==1 {next}
+    $3 == "pending" {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline requested_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      age_days = (now_epoch - requested_epoch) / 86400;
+      if (age_days >= days) {
+        printf "OVERDUE: %s — requested %s (%d days ago)\n", $1, $2, age_days;
+      }
+    }
+  ' "{{coi_requests_csv_path}}"
+variables:
+  coi_requests_csv_path:
+    default: "./coi-requests.csv"
+    description: "Path to a CSV with columns: requester_name,requested_date (YYYY-MM-DD),status (pending/fulfilled)."
+  escalate_after_days:
+    default: 3
+    description: Days a request can sit before it counts as overdue.
+compatible_agents: [generic, claude, codex]
+notes: >
+  This is about issuing COIs to others who need proof of your coverage —
+  the opposite direction from `policy-renewal-reminder` and
+  `premium-payment-due-reminder`, which track your own policies.

package/jobs/insurance/premium-payment-due-reminder.yaml

@@ -0,0 +1,35 @@
+id: premium-payment-due-reminder
+version: 1
+name: Insurance Premium Payment Due Reminder
+description: >
+  Warns you before an insurance premium payment is due, separate from the
+  policy's renewal date. Use this if a policy has ever lapsed for
+  non-payment even though the renewal itself was months away, because a
+  monthly or quarterly premium payment was missed.
+category: insurance
+tags: [insurance, premium, payment, reminder]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (due_epoch - now_epoch) / 86400;
+      if (diff_days <= days && diff_days >= 0) {
+        printf "PREMIUM DUE: %s — due %s (%d days)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{premiums_csv_path}}"
+variables:
+  premiums_csv_path:
+    default: "./insurance-premiums.csv"
+    description: "Path to a CSV with columns: policy_name,next_payment_due_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 7
+    description: How many days before a premium payment is due to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Complements `policy-renewal-reminder` — that one tracks the annual/term renewal date, this one tracks the recurring payment schedule within the term.

package/jobs/inventory/inventory-shrinkage-watch.yaml

@@ -0,0 +1,36 @@
+id: inventory-shrinkage-watch
+version: 1
+name: Inventory Shrinkage Watch
+description: >
+  Tracks the gap between expected and actual inventory over time and
+  flags when shrinkage (theft, damage, data-entry error) crosses a
+  threshold. Use this if shrinkage has ever only gotten noticed at the
+  annual physical count instead of trending visibly for months first.
+category: inventory
+tags: [inventory, shrinkage, loss-prevention, audit]
+schedule: "0 6 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v pct="{{alert_threshold_pct}}" '
+    NR==1 {next}
+    {
+      expected = $2;
+      actual = $3;
+      if (expected > 0) {
+        shrink_pct = ((expected - actual) / expected) * 100;
+        if (shrink_pct >= pct) {
+          printf "SHRINKAGE: %s — expected %d, actual %d (%.1f%% shrink)\n", $1, expected, actual, shrink_pct;
+        }
+      }
+    }
+  ' "{{inventory_counts_csv_path}}"
+variables:
+  inventory_counts_csv_path:
+    default: "./inventory-counts.csv"
+    description: "Path to a CSV with columns: sku,expected_quantity,actual_counted_quantity."
+  alert_threshold_pct:
+    default: 3
+    description: Shrinkage percentage that triggers a flag.
+compatible_agents: [generic, claude, codex]
+notes: Complements `inventory-count-discrepancy-check` (single-count mismatch) by tracking shrinkage as an ongoing percentage worth watching for a trend, not just a one-off count reconciliation.

package/jobs/inventory/overstock-slow-mover-check.yaml

@@ -0,0 +1,36 @@
+id: overstock-slow-mover-check
+version: 1
+name: Overstock / Slow-Mover Check
+description: >
+  Flags SKUs sitting well above normal stock levels with low recent sales
+  velocity, tying up capital and warehouse space. Use this if slow-moving
+  stock has ever piled up quietly until a year-end count revealed how
+  much cash was sitting on shelves doing nothing.
+category: inventory
+tags: [inventory, overstock, slow-mover, capital]
+schedule: "0 6 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v mult="{{overstock_multiplier}}" -v min_days="{{min_days_of_stock}}" '
+    NR==1 {next}
+    {
+      daily_velocity = $3 / 30;
+      days_of_stock = (daily_velocity > 0) ? $2 / daily_velocity : 9999;
+      if (days_of_stock >= min_days && $2 > ($4 * mult)) {
+        printf "OVERSTOCK: %s — %d units (%.0f days of stock, %.1fx normal par)\n", $1, $2, days_of_stock, $2/$4;
+      }
+    }
+  ' "{{inventory_csv_path}}"
+variables:
+  inventory_csv_path:
+    default: "./inventory-with-par.csv"
+    description: "Path to a CSV with columns: sku,current_stock,units_sold_last_30_days,normal_par_level."
+  overstock_multiplier:
+    default: 2
+    description: How many times above normal par level counts as overstocked.
+  min_days_of_stock:
+    default: 90
+    description: Minimum days-of-stock-on-hand (at current velocity) before flagging, to avoid noise from normal restocking bumps.
+compatible_agents: [generic, claude, codex]
+notes: Complements `low-stock-alert`/`low-stock-reorder-alert` by catching the opposite problem — too much stock, not too little.

package/jobs/investing/earnings-calendar-watch.yaml

@@ -0,0 +1,32 @@
+id: earnings-calendar-watch
+version: 1
+name: Earnings Calendar Watch
+description: >
+  Checks for upcoming earnings dates on stocks you hold, so a report
+  doesn't catch you off guard. Use this if a holding has ever moved
+  sharply overnight and you only afterward realized earnings had been
+  scheduled for that day.
+category: investing
+tags: [investing, earnings, stocks, calendar]
+schedule: "0 8 * * 1"
+timezone: "America/New_York"
+runner: agent-prompt
+prompt: |
+  Check upcoming earnings dates for these holdings: {{tickers}}, over the
+  next {{lookahead_days}} days (via any market data source or earnings
+  calendar).
+  1. List each ticker with an earnings date in the window, and whether
+     it's before or after market close.
+  2. Note the analyst consensus estimate if easily available, for
+     context.
+  3. If none of the tracked tickers report in this window, say so in one
+     line.
+variables:
+  tickers:
+    default: "AAPL, MSFT"
+    description: Comma-separated list of stock tickers to track.
+  lookahead_days:
+    default: 14
+    description: How far ahead to check for scheduled earnings reports.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Informational only — not a recommendation to trade around earnings, which is notoriously volatile and easy to get wrong.

package/jobs/investing/tax-loss-harvesting-review.yaml

@@ -0,0 +1,33 @@
+id: tax-loss-harvesting-review
+version: 1
+name: Tax-Loss Harvesting Review
+description: >
+  Checks your holdings for unrealized losses worth considering for
+  tax-loss harvesting before year-end. Use this if you've ever realized in
+  December that a position had been sitting at a loss all year and you
+  never did anything about it for tax purposes.
+category: investing
+tags: [investing, tax, portfolio, capital-gains]
+schedule: "0 9 * * 1"
+timezone: "America/New_York"
+runner: agent-prompt
+prompt: |
+  Check current holdings and cost basis in {{brokerage_or_source}}.
+  1. List any position with an unrealized loss of at least
+     ${{min_loss_usd}}.
+  2. Note the loss amount and how long the position has been held
+     (relevant for short- vs. long-term treatment).
+  3. Flag anything that would trigger a wash sale if repurchased within 30
+     days, based on recent buy activity in the same or a substantially
+     identical security.
+  4. This is informational only, not tax advice — say so, and recommend
+     confirming with a tax professional before acting.
+variables:
+  brokerage_or_source:
+    default: "your brokerage account"
+    description: Where holdings and cost basis are tracked.
+  min_loss_usd:
+    default: 500
+    description: Minimum unrealized loss (USD) worth surfacing.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Not tax or investment advice — flags candidates for a human (ideally with a tax professional) to evaluate, doesn't execute any trades.

package/jobs/legal/compliance-filing-deadline-reminder.yaml

@@ -0,0 +1,38 @@
+id: compliance-filing-deadline-reminder
+version: 1
+name: Corporate Compliance Filing Deadline Reminder
+description: >
+  Warns you before a recurring corporate compliance filing is due —
+  annual reports, franchise tax, registered agent renewals. Use this if
+  you've ever had a company administratively dissolved (and had to pay to
+  reinstate it) because a routine state filing quietly lapsed.
+category: legal
+tags: [legal, compliance, corporate, filing]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (due_epoch - now_epoch) / 86400;
+      if (diff_days <= days && diff_days >= 0) {
+        printf "FILING DUE: %s — due %s (%d days)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{filings_csv_path}}"
+variables:
+  filings_csv_path:
+    default: "./compliance-filings.csv"
+    description: "Path to a CSV with columns: filing_name,due_date (YYYY-MM-DD) — e.g. annual report, franchise tax, registered agent renewal."
+  warn_days_before:
+    default: 30
+    description: How many days before a filing is due to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Covers routine corporate/administrative filings — distinct from
+  `court-deadline-reminder` (litigation deadlines) and
+  `tax-deadline-reminder` in finance (income/estimated tax deadlines).

package/jobs/logistics/container-demurrage-fee-watch.yaml

@@ -0,0 +1,35 @@
+id: container-demurrage-fee-watch
+version: 1
+name: Container Demurrage/Detention Fee Watch
+description: >
+  Checks tracked containers against their free-time deadline and warns
+  before demurrage or detention fees start accruing. Use this if a
+  container has ever sat at port past its free days and the fee bill only
+  showed up weeks later as a surprise.
+category: logistics
+tags: [logistics, shipping, demurrage, fees]
+schedule: "0 7 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline deadline_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (deadline_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "FEE RISK: container %s — free time ends %s (%d days)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{containers_csv_path}}"
+variables:
+  containers_csv_path:
+    default: "./container-free-time.csv"
+    description: "Path to a CSV with columns: container_number,free_time_expiry_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 2
+    description: How many days before free time expires to start warning — demurrage windows are usually short.
+compatible_agents: [generic, claude, codex]
+notes: Assumes free-time deadlines are exported or manually tracked from your carrier/terminal portal — this is the "did anyone actually check" backstop before fees start accruing.

package/jobs/logistics/last-mile-delivery-exception-check.yaml

@@ -0,0 +1,36 @@
+id: last-mile-delivery-exception-check
+version: 1
+name: Last-Mile Delivery Exception Check
+description: >
+  Checks recent deliveries for exceptions — failed attempts, refused
+  packages, address issues — and flags them for follow-up. Use this if a
+  failed delivery has ever sat unresolved until an annoyed customer
+  emailed asking where their order was.
+category: logistics
+tags: [logistics, delivery, last-mile, exceptions]
+schedule: "0 */4 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check {{carrier_or_tms}} for delivery exceptions (failed attempt,
+  refused, address issue, damaged) logged in the last
+  {{lookback_hours}} hours.
+  1. List each exception: order/tracking number, exception type, and how
+     long ago it occurred.
+  2. Flag anything with no follow-up action logged yet (redelivery
+     scheduled, customer contacted) past {{escalate_after_hours}} hours.
+  3. Draft a short customer-facing message per unresolved exception,
+     appropriate to the exception type (e.g. rescheduling for a failed
+     attempt vs. apologizing for damage).
+variables:
+  carrier_or_tms:
+    default: "your carrier's tracking API or TMS"
+    description: Where delivery exception data is available (carrier API, transportation management system).
+  lookback_hours:
+    default: 24
+    description: How far back to check for new exceptions.
+  escalate_after_hours:
+    default: 12
+    description: Hours an exception can sit without follow-up before it counts as overdue.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — review customer messages before sending, and confirm any rescheduled delivery actually gets booked through the carrier.

package/jobs/manufacturing/raw-material-shortage-risk-check.yaml

@@ -0,0 +1,31 @@
+id: raw-material-shortage-risk-check
+version: 1
+name: Raw Material Shortage Risk Check
+description: >
+  Compares raw material stock against what the production schedule needs
+  over the next planning window, and flags anything that'll run short.
+  Use this if a production run has ever stalled mid-shift because a
+  component ran out and nobody had cross-checked stock against the
+  schedule beforehand.
+category: manufacturing
+tags: [manufacturing, materials, production-planning, shortage]
+schedule: "0 6 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' '
+    NR==1 {next}
+    {
+      material = $1; on_hand = $2; needed = $3;
+      if (needed > on_hand) {
+        shortfall = needed - on_hand;
+        printf "SHORTFALL: %s — need %d, have %d (short %d)\n", material, needed, on_hand, shortfall;
+      }
+    }
+  ' "{{materials_needs_csv_path}}"
+variables:
+  materials_needs_csv_path:
+    default: "./material-requirements.csv"
+    description: "Path to a CSV with columns: material_name,on_hand_qty,needed_qty_for_schedule — needed_qty computed from your production schedule/BOM for the planning window."
+compatible_agents: [generic, claude, codex]
+notes: Assumes `needed_qty` is derived from your MRP/production schedule export — this job just does the comparison and flags shortfalls, it doesn't calculate the BOM requirement itself.

package/jobs/manufacturing/supplier-otd-performance-watch.yaml

@@ -0,0 +1,38 @@
+id: supplier-otd-performance-watch
+version: 1
+name: Supplier On-Time Delivery Performance Watch
+description: >
+  Tracks a supplier's on-time delivery rate over recent orders and flags
+  it when performance drops below target. Use this if a supplier's
+  reliability has ever quietly slipped for months before it showed up as a
+  production delay bad enough to notice.
+category: manufacturing
+tags: [manufacturing, supplier, otd, procurement]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v target="{{otd_target_pct}}" '
+    NR==1 {next}
+    {
+      total[$1]++;
+      if ($2 == "on-time") ontime[$1]++;
+    }
+    END {
+      for (s in total) {
+        pct = (ontime[s] / total[s]) * 100;
+        if (pct < target) {
+          printf "BELOW TARGET: %s — %.1f%% on-time (%d of %d orders), target %d%%\n", s, pct, ontime[s], total[s], target;
+        }
+      }
+    }
+  ' "{{orders_csv_path}}"
+variables:
+  orders_csv_path:
+    default: "./supplier-orders.csv"
+    description: "Path to a CSV with columns: supplier_name,status (on-time or late) — one row per recent order."
+  otd_target_pct:
+    default: 90
+    description: Minimum acceptable on-time delivery percentage.
+compatible_agents: [generic, claude, codex]
+notes: Assumes an exported or manually logged record of recent order statuses per supplier — export this from your ERP/procurement system on a schedule to keep the CSV current.

package/jobs/marketing/campaign-utm-tracking-check.yaml

@@ -0,0 +1,41 @@
+id: campaign-utm-tracking-check
+version: 1
+name: Campaign UTM Tracking Check
+description: >
+  Checks a list of campaign links for missing or malformed UTM parameters
+  before (or after) launch. Use this if a campaign has ever run for a week
+  with broken tracking, making every attribution report for that period
+  useless.
+category: marketing
+tags: [marketing, utm, tracking, analytics]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  required="{{required_params}}";
+  fail=0;
+  while IFS= read -r url; do
+    [ -z "$url" ] && continue;
+    missing="";
+    IFS=',' read -ra params <<< "$required";
+    for p in "${params[@]}"; do
+      case "$url" in
+        *"${p}="*) ;;
+        *) missing="$missing $p" ;;
+      esac;
+    done;
+    if [ -n "$missing" ]; then
+      echo "MISSING PARAMS ($missing): $url";
+      fail=1;
+    fi;
+  done < "{{urls_file_path}}";
+  exit $fail
+variables:
+  urls_file_path:
+    default: "./campaign-urls.txt"
+    description: Path to a plain text file with one campaign URL per line.
+  required_params:
+    default: "utm_source,utm_medium,utm_campaign"
+    description: Comma-separated list of UTM parameter names every URL must include.
+compatible_agents: [generic, claude, codex]
+notes: Checks parameter presence only, not that values are consistent/correctly spelled (e.g. "linkedin" vs "LinkedIn") — pair with a naming convention doc if that's a recurring issue.

package/jobs/nonprofit/board-action-item-followup-check.yaml

@@ -0,0 +1,28 @@
+id: board-action-item-followup-check
+version: 1
+name: Board Action Item Follow-Up Check
+description: >
+  Checks action items from recent board meeting minutes and flags any
+  that are overdue with no update. Use this if a board commitment has
+  ever quietly died between meetings because nobody tracked it after the
+  minutes were filed away.
+category: nonprofit
+tags: [nonprofit, board, governance, followup]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Read the action items list from {{action_items_source}} (extracted from
+  recent board meeting minutes).
+  1. List each open action item: owner, due date, and current status.
+  2. Flag anything past its due date with no completion note as overdue.
+  3. Draft a short status-check message per overdue item, addressed to
+     its owner.
+  4. Note any item with no owner assigned at all — that's usually the
+     first thing to fix, since it explains why nothing happened.
+variables:
+  action_items_source:
+    default: "your board meeting minutes / action item tracker"
+    description: Where board action items and their owners/due dates are recorded.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — status-check messages should go out through whatever channel the board already uses.

package/jobs/nonprofit/grant-reporting-deadline-check.yaml

@@ -0,0 +1,38 @@
+id: grant-reporting-deadline-check
+version: 1
+name: Grant Reporting Deadline Check
+description: >
+  Warns you before a post-award grant report is due, separate from the
+  application deadline. Use this if a funder relationship has ever soured
+  because a required progress or financial report was late, even though
+  the grant itself was won and the work was going fine.
+category: nonprofit
+tags: [nonprofit, grants, reporting, compliance]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (due_epoch - now_epoch) / 86400;
+      if (diff_days <= days && diff_days >= 0) {
+        printf "REPORT DUE: %s — due %s (%d days)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{reports_csv_path}}"
+variables:
+  reports_csv_path:
+    default: "./grant-reports.csv"
+    description: "Path to a CSV with columns: grant_name,report_due_date (YYYY-MM-DD) — one row per required progress/financial report."
+  warn_days_before:
+    default: 14
+    description: How many days before a report is due to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Tracks post-award reporting obligations — distinct from
+  `grant-deadline-reminder`, which tracks application deadlines for grants
+  not yet won.

package/jobs/podcast/podcast-download-drop-watch.yaml

@@ -0,0 +1,42 @@
+id: podcast-download-drop-watch
+version: 1
+name: Podcast Download Drop Watch
+description: >
+  Compares a new episode's early download numbers against your recent
+  average and flags a real drop. Use this if a listenership decline has
+  ever gone unnoticed for months because nobody compared episode numbers
+  side by side.
+category: podcast
+tags: [podcast, downloads, analytics, listenership]
+schedule: "0 10 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check download/listen numbers for the most recent episode of
+  {{podcast_name}} at the {{days_since_release}}-day mark, via
+  {{hosting_platform}}.
+  1. Compare against the average {{days_since_release}}-day download
+     count for the last {{baseline_episode_count}} episodes.
+  2. Flag a drop of {{drop_threshold_pct}}% or more below that average.
+  3. If flagged, note anything that coincided with this episode
+     (different topic, guest vs. solo, publish day/time change) that
+     might explain it, if that context is available.
+  4. If downloads are in the normal range, report the number in one line.
+variables:
+  podcast_name:
+    default: "your podcast"
+    description: Name of the podcast to check.
+  hosting_platform:
+    default: "your podcast host (e.g. Spotify for Podcasters, Buzzsprout, Libsyn)"
+    description: Where download analytics are available.
+  days_since_release:
+    default: 3
+    description: How many days after release to compare (early numbers are more predictive than day-one spikes).
+  baseline_episode_count:
+    default: 8
+    description: How many recent episodes to average for the baseline comparison.
+  drop_threshold_pct:
+    default: 20
+    description: Percentage drop below baseline that counts as worth flagging.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Complements `podcast-rating-review-watch` (qualitative feedback) with a quantitative listenership signal.

package/jobs/podcast/podcast-rating-review-watch.yaml

@@ -0,0 +1,37 @@
+id: podcast-rating-review-watch
+version: 1
+name: Podcast Rating/Review Watch
+description: >
+  Checks for new ratings and reviews on your podcast platforms and flags
+  a negative one or a rating drop worth looking into. Use this if a
+  critical review has ever sat unanswered for months because nobody
+  checks the ratings page between episodes.
+category: podcast
+tags: [podcast, reviews, ratings, reputation]
+schedule: "0 10 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check {{podcast_platforms}} for {{podcast_name}} for reviews/ratings
+  posted in the last {{lookback_days}} days.
+  1. List any new review, with rating and a one-line summary.
+  2. Flag anything rated at or below {{alert_threshold_stars}} stars, or
+     any average-rating drop compared to the prior period.
+  3. Note if a review raises a specific, actionable complaint (audio
+     quality, ad load, pacing) versus general subjective taste — the
+     actionable ones are worth a closer look.
+variables:
+  podcast_platforms:
+    default: "Apple Podcasts, Spotify"
+    description: Comma-separated list of platforms to check.
+  podcast_name:
+    default: "your podcast"
+    description: Name of the podcast to check.
+  lookback_days:
+    default: 7
+    description: How far back to check for new reviews.
+  alert_threshold_stars:
+    default: 3
+    description: Star rating at or below which a review gets flagged (out of 5).
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Most podcast platforms don't expose a review API directly — this typically means checking the platform's creator dashboard manually or via whatever export it offers.

package/jobs/realestate/property-tax-deadline-reminder.yaml

@@ -0,0 +1,35 @@
+id: property-tax-deadline-reminder
+version: 1
+name: Property Tax Deadline Reminder
+description: >
+  Warns you before a property tax payment is due for a tracked property.
+  Use this if a property tax bill has ever gone unpaid past the deadline
+  because it arrived by mail and got buried, resulting in penalties or a
+  lien risk.
+category: realestate
+tags: [realestate, property-tax, payment, deadline]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (due_epoch - now_epoch) / 86400;
+      if (diff_days <= days && diff_days >= 0) {
+        printf "TAX DUE: %s — due %s (%d days)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{properties_csv_path}}"
+variables:
+  properties_csv_path:
+    default: "./property-tax-due-dates.csv"
+    description: "Path to a CSV with columns: property_name,tax_due_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 21
+    description: How many days before the tax due date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Many jurisdictions bill property tax semi-annually or annually with different due dates per installment — add one row per installment rather than one per property per year.