@wonsukchoi/crondex 0.17.0 → 0.19.0

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

package/jobs/nonprofit/event-rsvp-shortfall-check.yaml

@@ -0,0 +1,40 @@
+id: event-rsvp-shortfall-check
+version: 1
+name: Fundraising Event RSVP Shortfall Check
+description: >
+  Checks confirmed RSVPs for an upcoming fundraising event against your
+  goal and flags it if you're falling short as the date approaches. Use
+  this if an event has ever snuck up with half-empty RSVPs and no time
+  left to push more invitations.
+category: nonprofit
+tags: [nonprofit, events, fundraising, rsvp]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  rsvp_count=$(psql "{{database_url}}" -t -A -c "select count(*) from rsvps where event_id = '{{event_id}}' and status = 'confirmed';");
+  today=$(date +%s);
+  event_ts=$(date -d "{{event_date}}" +%s 2>/dev/null || date -jf "%Y-%m-%d" "{{event_date}}" +%s);
+  days_left=$(( (event_ts - today) / 86400 ));
+  if [ "$rsvp_count" -lt "{{rsvp_goal}}" ] && [ "$days_left" -le "{{warn_days_before}}" ]; then
+    echo "WARNING: event {{event_id}} has $rsvp_count/{{rsvp_goal}} RSVPs with $days_left days left";
+    exit 1;
+  else echo "OK: event {{event_id}} has $rsvp_count/{{rsvp_goal}} RSVPs, $days_left days left"; fi
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the events/RSVP database.
+  event_id:
+    default: "your-event-id"
+    description: Identifier of the event to track, matching the rsvps table.
+  event_date:
+    default: "2027-01-01"
+    description: Event date (YYYY-MM-DD).
+  rsvp_goal:
+    default: 100
+    description: Target number of confirmed RSVPs.
+  warn_days_before:
+    default: 14
+    description: Days before the event to start warning if under goal.
+compatible_agents: [generic, claude, codex]
+notes: Assumes an `rsvps` table with `event_id` and a `status` column set to 'confirmed' for accepted invites — adjust the query to your CRM/registration schema.

package/jobs/podcast/transcript-publish-lag-check.yaml

@@ -0,0 +1,31 @@
+id: transcript-publish-lag-check
+version: 1
+name: Transcript Publish Lag Check
+description: >
+  Flags episodes that published without a transcript still missing after a
+  grace period. Use this if you've ever promised accessible, searchable
+  transcripts but had episodes quietly sit for weeks without one.
+category: podcast
+tags: [podcast, transcript, accessibility, publishing]
+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 pub_ts; close(cmd);
+      days_since = int((today - pub_ts) / 86400);
+      if ($3 == "missing" && days_since >= warn) print "WARNING: " $1 " published " days_since " days ago with no transcript (" $2 ")";
+    }
+  ' {{episodes_csv}}
+variables:
+  episodes_csv:
+    default: "episodes.csv"
+    description: "CSV with header row, columns: episode_title,publish_date(YYYY-MM-DD),transcript_status(ready/missing)."
+  warn_days:
+    default: 3
+    description: Days after publish to allow before flagging a missing transcript.
+compatible_agents: [generic, claude, codex]
+notes: Update transcript_status to "ready" in episodes.csv once a transcript is posted, so the row stops flagging.

package/jobs/realestate/hoa-fee-collection-check.yaml

@@ -0,0 +1,35 @@
+id: hoa-fee-collection-check
+version: 1
+name: HOA Fee Collection Check
+description: >
+  Scans an HOA/association dues ledger for owners who are past due and
+  totals what's outstanding. Use this if unpaid association dues have ever
+  piled up silently until the reserve fund came up short.
+category: realestate
+tags: [realestate, hoa, dues, collections]
+schedule: "0 8 5 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v grace="{{grace_days}}" -v today="$(date +%s)" '
+    NR==1 {next}
+    {
+      cmd="date -d \"" $3 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $3 "\" +%s";
+      cmd | getline due_ts; close(cmd);
+      days_late = int((today - due_ts) / 86400);
+      if ($4 == "unpaid" && days_late >= grace) {
+        printf "PAST DUE: unit %s owes %s, %d days late (due %s)\n", $1, $2, days_late, $3;
+        total += $2; count++;
+      }
+    }
+    END { if (count > 0) printf "TOTAL OUTSTANDING: $%.2f across %d unit(s)\n", total, count; else print "OK: no past-due dues"; }
+  ' "{{dues_ledger_csv}}"
+variables:
+  dues_ledger_csv:
+    default: "./hoa-dues-ledger.csv"
+    description: "Path to a CSV with columns: unit,amount_due,due_date(YYYY-MM-DD),status(paid/unpaid)."
+  grace_days:
+    default: 10
+    description: Days past the due date before a balance counts as past due.
+compatible_agents: [generic, claude, codex]
+notes: Update hoa-dues-ledger.csv status to "paid" as payments land so this only ever flags true outstanding balances.

package/jobs/restaurant/supplier-price-increase-watch.yaml

@@ -0,0 +1,36 @@
+id: supplier-price-increase-watch
+version: 1
+name: Supplier Price Increase Watch
+description: >
+  Compares this week's supplier invoice prices against your reference cost
+  sheet and flags ingredients that jumped more than a set percentage. Use
+  this if a supplier has ever quietly raised prices for months before
+  anyone noticed the food cost creeping up.
+category: restaurant
+tags: [restaurant, suppliers, cost, invoices]
+schedule: "0 6 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v threshold="{{pct_increase_threshold}}" '
+    FNR==NR { if (FNR>1) ref[$1]=$2; next }
+    FNR==1 { next }
+    {
+      if ($1 in ref && ref[$1] > 0) {
+        pct = (($2 - ref[$1]) / ref[$1]) * 100;
+        if (pct >= threshold) printf "PRICE UP: %s reference $%.2f -> invoice $%.2f (+%.1f%%)\n", $1, ref[$1], $2, pct;
+      }
+    }
+  ' "{{reference_cost_csv}}" "{{latest_invoice_csv}}"
+variables:
+  reference_cost_csv:
+    default: "./reference-costs.csv"
+    description: "CSV with header row, columns: ingredient,unit_cost — your baseline/expected price per ingredient."
+  latest_invoice_csv:
+    default: "./latest-invoice.csv"
+    description: "CSV with header row, columns: ingredient,unit_cost — the same ingredients priced on this week's invoice."
+  pct_increase_threshold:
+    default: 8
+    description: Percentage increase over the reference cost that counts as worth flagging.
+compatible_agents: [generic, claude, codex]
+notes: Ingredient names must match exactly between the two CSVs (same spelling/casing) or a row won't be compared.

package/jobs/retail/markdown-aging-inventory-check.yaml

@@ -0,0 +1,33 @@
+id: markdown-aging-inventory-check
+version: 1
+name: Markdown Aging Inventory Check
+description: >
+  Flags SKUs that have sat unsold past a set number of days so they can be
+  marked down before they become dead stock. Use this if slow-moving
+  inventory has ever tied up cash for months because nobody was tracking
+  how long items had actually been sitting on the shelf.
+category: retail
+tags: [retail, inventory, markdown, aging]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v warn={{aging_days_threshold}} '
+    NR==1 {next}
+    {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline received_ts; close(cmd);
+      days_on_shelf = int((today - received_ts) / 86400);
+      if ($3 == "in-stock" && days_on_shelf >= warn) printf "MARKDOWN CANDIDATE: SKU %s in stock %d days (received %s)\n", $1, days_on_shelf, $2;
+    }
+  ' "{{inventory_csv}}"
+variables:
+  inventory_csv:
+    default: "./inventory-log.csv"
+    description: "CSV with header row, columns: sku,received_date(YYYY-MM-DD),status(in-stock/sold)."
+  aging_days_threshold:
+    default: 60
+    description: Days on the shelf before a SKU counts as a markdown candidate.
+compatible_agents: [generic, claude, codex]
+notes: Update inventory-log.csv status to "sold" as items move so this only ever flags genuinely aging stock.

package/jobs/sales/proposal-followup-nudge.yaml

@@ -0,0 +1,31 @@
+id: proposal-followup-nudge
+version: 1
+name: Proposal Follow-Up Nudge
+description: >
+  Checks which sent proposals/quotes have had no reply after a set number
+  of days and drafts a short follow-up nudge for each. Use this if a
+  proposal has ever gone quiet after you sent it, and only much later did
+  you realize nobody had followed up.
+category: sales
+tags: [sales, proposals, follow-up, outreach]
+schedule: "0 9 * * 1-5"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Read {{proposals_source}} and find proposals/quotes sent more than
+  {{followup_days}} days ago with no recorded reply or status change.
+  1. List each: prospect name, proposal sent date, deal value if known.
+  2. Draft a short, low-pressure follow-up message per prospect that
+     references what was proposed and asks one specific question to
+     re-open the conversation, rather than a generic "just checking in."
+  3. Skip anything already marked closed-won, closed-lost, or explicitly
+     "do not contact" in {{proposals_source}}.
+variables:
+  proposals_source:
+    default: "your CRM's proposal/quote list, or a proposals.csv with columns: prospect,sent_date,status,value"
+    description: Where sent proposals and their status live.
+  followup_days:
+    default: 5
+    description: Days of silence after sending before a proposal counts as due for a follow-up.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — review each nudge before sending, and skip anything the prospect asked not to be contacted about.

package/jobs/support/macro-usage-staleness-check.yaml

@@ -0,0 +1,33 @@
+id: macro-usage-staleness-check
+version: 1
+name: Macro/Canned Response Staleness Check
+description: >
+  Flags saved canned responses (macros) that haven't been used in a long
+  time so someone can check whether they're still accurate. Use this if
+  a stale macro has ever gone out with outdated pricing, a dead link, or
+  a policy that changed months ago.
+category: support
+tags: [support, macros, canned-responses, knowledge-base]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v warn={{stale_days_threshold}} '
+    NR==1 {next}
+    {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline last_used_ts; close(cmd);
+      days_idle = int((today - last_used_ts) / 86400);
+      if (days_idle >= warn) printf "STALE MACRO: \"%s\" last used %d days ago (%s)\n", $1, days_idle, $2;
+    }
+  ' "{{macro_usage_csv}}"
+variables:
+  macro_usage_csv:
+    default: "./macro-usage-log.csv"
+    description: "CSV with header row, columns: macro_name,last_used_date(YYYY-MM-DD) — export this from your helpdesk's macro usage report."
+  stale_days_threshold:
+    default: 90
+    description: Days since last use before a macro counts as stale and worth a content review.
+compatible_agents: [generic, claude, codex]
+notes: A flagged macro isn't necessarily wrong — low usage can just mean a rare scenario — but it's worth a quick read for outdated info before it fires again.

package/jobs/team/expense-report-deadline-reminder.yaml

@@ -0,0 +1,28 @@
+id: expense-report-deadline-reminder
+version: 1
+name: Expense Report Deadline Reminder
+description: >
+  Warns you before the monthly expense report submission deadline
+  passes. Use this if you've ever missed reimbursement because the
+  expense window closed before you got around to submitting receipts.
+category: team
+tags: [team, expenses, finance, deadline]
+schedule: "0 9 * * *"
+timezone: "America/Los_Angeles"
+runner: shell
+command: >
+  today=$(date +%d); deadline={{deadline_day_of_month}};
+  days_left=$(( deadline - 10#$today ));
+  if [ "$days_left" -lt 0 ]; then echo "note: this month's deadline (day $deadline) has passed — nothing due until next month.";
+  elif [ "$days_left" -le {{warn_days_before}} ]; then
+    echo "REMINDER: expense report due in $days_left day(s), by day $deadline of this month.";
+  else echo "OK: $days_left day(s) until expense report deadline (day $deadline)."; fi
+variables:
+  deadline_day_of_month:
+    default: 25
+    description: Day of the month expense reports are due (use 1-28 for portability across months).
+  warn_days_before:
+    default: 5
+    description: Start warning this many days before the deadline.
+compatible_agents: [generic, claude, codex]
+notes: Zero-token. Assumes a fixed day-of-month deadline; adjust deadline_day_of_month if your company's cycle differs.

package/jobs/travel/hotel-cancellation-deadline-reminder.yaml

@@ -0,0 +1,32 @@
+id: hotel-cancellation-deadline-reminder
+version: 1
+name: Hotel Cancellation Deadline Reminder
+description: >
+  Warns you before a hotel booking's free-cancellation window closes.
+  Use this if you've ever gotten charged for a hotel you meant to
+  cancel because the deadline passed while you were still deciding.
+category: travel
+tags: [travel, hotel, cancellation, deadline]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  name="{{booking_name}}"; deadline={{cancellation_deadline}}; warn={{warn_hours_before}};
+  deadline_epoch=$(date -j -f "%Y-%m-%dT%H:%M" "$deadline" +%s 2>/dev/null || date -d "$deadline" +%s);
+  now_epoch=$(date +%s);
+  hours_left=$(( (deadline_epoch-now_epoch)/3600 ));
+  if [ "$hours_left" -le 0 ]; then echo "note: cancellation window for $name has passed — booking is now non-refundable (or already handled).";
+  elif [ "$hours_left" -le "$warn" ]; then echo "WARNING: free cancellation for $name closes in $hours_left hour(s) ($deadline)."; exit 1;
+  else echo "OK: $name, $hours_left hour(s) until cancellation deadline."; fi
+variables:
+  booking_name:
+    default: "hotel booking"
+    description: Name/label for this booking (hotel name or confirmation number).
+  cancellation_deadline:
+    default: "2026-12-31T23:59"
+    description: "Date and time (YYYY-MM-DDTHH:MM, local timezone) the free-cancellation window closes."
+  warn_hours_before:
+    default: 48
+    description: Start warning this many hours before the deadline.
+compatible_agents: [generic, claude, codex]
+notes: Zero-token. One job per booking — copy it and adjust for each reservation you're tracking.