@wonsukchoi/crondex 0.20.0 → 0.21.0

package/jobs/spa/product-chemical-expiry-check.yaml

@@ -0,0 +1,35 @@
+id: product-chemical-expiry-check
+version: 1
+name: Product & Chemical Expiry Check
+description: >
+  Flags skincare products, dye lots, wax, and other chemical inventory
+  approaching their expiration or period-after-opening date. Use this if
+  an esthetician or colorist has ever applied a product past its safe-use
+  date because the expiry label was never checked against today's date.
+category: spa
+tags: [spa, inventory, expiry, safety, chemicals]
+schedule: "0 6 * * 1"
+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 exp_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (exp_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "EXPIRING/EXPIRED: %s (lot %s) — expires %s (%d days)\n", $1, $3, $2, diff_days;
+      }
+    }
+  ' "{{product_expiry_csv_path}}"
+variables:
+  product_expiry_csv_path:
+    default: "./product-expiry.csv"
+    description: "Path to a CSV with columns: product_name,expiry_or_pao_date (YYYY-MM-DD),lot_number."
+  warn_days_before:
+    default: 14
+    description: How many days before expiry to start warning, so stock can be used up or pulled before it goes bad.
+compatible_agents: [generic, claude, codex]
+notes: Applying an expired chemical (peel, dye, wax) can cause skin reactions — pull flagged items from active use immediately, don't just discount and sell through.

package/jobs/spa/retail-product-low-stock-check.yaml

@@ -0,0 +1,26 @@
+id: retail-product-low-stock-check
+version: 1
+name: Retail Product Low-Stock Check
+description: >
+  Scans your retail/backbar inventory log and flags skincare, haircare, or
+  nail products at or below reorder point. Use this if a stylist or
+  esthetician has ever reached for a product mid-service and found the
+  shelf empty because nobody was watching the count.
+category: spa
+tags: [spa, retail, inventory, restock]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' '
+    NR==1 {next}
+    $2 <= $3 {
+      printf "LOW STOCK: %s — %d on hand, reorder point %d\n", $1, $2, $3;
+    }
+  ' "{{inventory_csv_path}}"
+variables:
+  inventory_csv_path:
+    default: "./retail-inventory.csv"
+    description: "Path to a CSV with columns: product_name,quantity_on_hand,reorder_point."
+compatible_agents: [generic, claude, codex]
+notes: Pair the reorder point with your supplier's typical lead time so you never hit zero mid-service.

package/jobs/spa/safety-inspection-due-reminder.yaml

@@ -0,0 +1,33 @@
+id: safety-inspection-due-reminder
+version: 1
+name: Health & Safety Inspection Due Reminder
+description: >
+  Warns before a health department, board-of-cosmetology, or fire/safety
+  inspection is expected, based on your jurisdiction's typical interval.
+  Use this if an inspector has ever shown up to a treatment room that
+  wasn't ready because nobody was tracking when the last inspection
+  happened.
+category: spa
+tags: [spa, compliance, inspection, safety]
+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 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/safety/board inspection (YYYY-MM-DD).
+  typical_interval_days:
+    default: 365
+    description: Typical number of days between inspections in your jurisdiction.
+  warn_days:
+    default: 21
+    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 a confirmed scheduled date — most boards don't publish inspection dates in advance.

package/jobs/telecom/circuit-outage-detection.yaml

@@ -0,0 +1,38 @@
+id: circuit-outage-detection
+version: 1
+name: Circuit Outage Detection
+description: >
+  Pings each monitored circuit endpoint and flags any that are down.
+  Use this if a customer circuit has ever gone dark and nobody on your
+  team noticed until the customer called in.
+category: telecom
+tags: [telecom, outage, monitoring, circuits]
+schedule: "*/5 * * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  down=0;
+  while IFS=',' read -r circuit_id endpoint _rest; do
+    [ "$circuit_id" = "circuit_id" ] && continue;
+    [ -z "$endpoint" ] && continue;
+    if ! ping -c "{{ping_count}}" -W "{{ping_timeout_sec}}" "$endpoint" >/dev/null 2>&1; then
+      echo "DOWN: circuit $circuit_id ($endpoint) is not responding";
+      down=1;
+    fi;
+  done < "{{circuits_csv_path}}";
+  if [ "$down" -eq 0 ]; then echo "OK: all monitored circuits responding"; else exit 1; fi
+variables:
+  circuits_csv_path:
+    default: "./circuits.csv"
+    description: "Path to a CSV with columns: circuit_id,endpoint (IP or hostname to ping)."
+  ping_count:
+    default: 2
+    description: Number of ping probes per circuit before declaring it down.
+  ping_timeout_sec:
+    default: 3
+    description: Timeout in seconds per ping probe.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Uses ICMP ping as a cheap reachability check — swap in an SNMP or NMS API
+  poll if your circuits are behind firewalls that block ICMP. Read-only,
+  no state changes.

package/jobs/telecom/circuit-provisioning-order-aging.yaml

@@ -0,0 +1,36 @@
+id: circuit-provisioning-order-aging
+version: 1
+name: Circuit Provisioning Order Aging Check
+description: >
+  Flags circuit orders that were placed but never activated within a
+  target number of days. Use this if a provisioning order has ever sat
+  in limbo for weeks because the install date fell through the cracks
+  between sales, the carrier, and the field tech.
+category: telecom
+tags: [telecom, provisioning, circuits, orders]
+schedule: "0 8 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v max_days="{{max_days_to_activate}}" '
+    NR==1 {next}
+    $3 != "" {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline order_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      age_days = (now_epoch - order_epoch) / 86400;
+      if (age_days >= max_days) {
+        printf "AGING ORDER: %s ordered %s (%d days ago), still not activated\n", $1, $2, age_days;
+      }
+    }
+  ' "{{orders_csv_path}}"
+variables:
+  orders_csv_path:
+    default: "./provisioning-orders.csv"
+    description: "Path to a CSV with columns: order_id,order_date (YYYY-MM-DD),activated_date (blank if not yet activated)."
+  max_days_to_activate:
+    default: 21
+    description: Days after order date to flag as aging if still not activated.
+compatible_agents: [generic, claude, codex]
+notes: Assumes order/activation dates are updated in the CSV from your provisioning ticketing system.

package/jobs/telecom/cpe-firmware-update-tracker.yaml

@@ -0,0 +1,45 @@
+id: cpe-firmware-update-tracker
+version: 1
+name: CPE Firmware/Warranty Update Tracker
+description: >
+  Checks deployed customer-premises equipment against current firmware
+  versions and warranty expiry dates, flagging anything out of date or
+  soon out of warranty. Use this if a modem or router has ever been
+  running years-old firmware with a known vulnerability because nobody
+  was tracking the fleet's patch level.
+category: telecom
+tags: [telecom, cpe, firmware, warranty]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v target_fw="{{target_firmware_version}}" -v warn_days="{{warranty_warn_days}}" '
+    NR==1 {next}
+    {
+      device=$1; fw=$2; warranty_end=$3;
+      if (fw != target_fw) {
+        printf "OUTDATED FIRMWARE: %s running %s, target is %s\n", device, fw, target_fw;
+      }
+      if (warranty_end != "") {
+        cmd = "date -d \"" warranty_end "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" warranty_end "\" +%s 2>/dev/null";
+        cmd | getline end_epoch; close(cmd);
+        "date +%s" | getline now_epoch; close("date +%s");
+        diff_days = (end_epoch - now_epoch) / 86400;
+        if (diff_days <= warn_days) {
+          printf "WARRANTY EXPIRING: %s warranty ends %s (%d days)\n", device, warranty_end, diff_days;
+        }
+      }
+    }
+  ' "{{cpe_inventory_csv_path}}"
+variables:
+  cpe_inventory_csv_path:
+    default: "./cpe-inventory.csv"
+    description: "Path to a CSV with columns: device_id,firmware_version,warranty_end_date (YYYY-MM-DD, blank if unknown)."
+  target_firmware_version:
+    default: "1.0.0"
+    description: The firmware version the fleet should be running.
+  warranty_warn_days:
+    default: 30
+    description: Days before warranty expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Assumes CPE inventory is exported from your provisioning/asset system into the CSV before this runs.

package/jobs/telecom/link-capacity-threshold-alert.yaml

@@ -0,0 +1,37 @@
+id: link-capacity-threshold-alert
+version: 1
+name: Link Capacity Threshold Alert
+description: >
+  Checks a link's current bandwidth utilization against a warning
+  threshold so you can upgrade capacity before customers notice
+  congestion. Use this if a trunk or uplink has ever saturated during
+  peak hours and the first sign anyone saw was a flood of slow-speed
+  complaints.
+category: telecom
+tags: [telecom, bandwidth, capacity, monitoring]
+schedule: "*/15 * * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  util=$(snmpget -v2c -c "{{snmp_community}}" -Ovq "{{link_host}}" "{{snmp_oid}}" 2>/dev/null | tr -d '\r');
+  if [ -z "$util" ]; then echo "no SNMP response from {{link_host}} — check reachability/community string"; exit 0;
+  elif [ "${util%.*}" -ge "{{warn_threshold_pct}}" ]; then echo "WARNING: link {{link_host}} at ${util}% utilization (threshold {{warn_threshold_pct}}%)"; exit 1;
+  else echo "OK: link {{link_host}} at ${util}% utilization"; fi
+variables:
+  link_host:
+    default: "10.0.0.1"
+    description: IP or hostname of the router/switch interface to poll.
+  snmp_community:
+    default: "public"
+    description: SNMP community string (or use SNMPv3 credentials via a wrapper script).
+  snmp_oid:
+    default: "1.3.6.1.2.1.31.1.1.1.6"
+    description: SNMP OID for the interface counter you're tracking utilization from.
+  warn_threshold_pct:
+    default: 85
+    description: Utilization percentage that triggers a warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Requires `snmpget` (net-snmp) and a readable SNMP OID for the target
+  interface — the default OID is illustrative, replace with the correct
+  ifHCOutOctets/utilization OID for your gear. Read-only poll.

package/jobs/telecom/peering-transit-contract-renewal-check.yaml

@@ -0,0 +1,36 @@
+id: peering-transit-contract-renewal-check
+version: 1
+name: Peering/Transit Contract Renewal Check
+description: >
+  Checks upstream transit and peering agreements for upcoming renewal or
+  auto-renew deadlines and warns with enough lead time to renegotiate.
+  Use this if a transit contract has ever auto-renewed at last year's
+  rate (or worse) because nobody flagged the deadline until the invoice
+  changed.
+category: telecom
+tags: [telecom, peering, transit, contracts]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v warn_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 renewal_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (renewal_epoch - now_epoch) / 86400;
+      if (diff_days <= warn_days && diff_days >= 0) {
+        printf "RENEWAL DUE: %s (%s) renews/auto-renews %s (%d days)\n", $1, $3, $2, diff_days;
+      }
+    }
+  ' "{{contracts_csv_path}}"
+variables:
+  contracts_csv_path:
+    default: "./transit-peering-contracts.csv"
+    description: "Path to a CSV with columns: provider_name,renewal_date (YYYY-MM-DD),contract_type (transit/peering/IX)."
+  warn_days_before:
+    default: 60
+    description: Days before renewal date to start warning — transit renegotiation needs lead time.
+compatible_agents: [generic, claude, codex]
+notes: Assumes contract renewal dates are manually tracked or exported from a contracts log into the CSV.

package/jobs/telecom/service-ticket-churn-risk-review.yaml

@@ -0,0 +1,56 @@
+id: service-ticket-churn-risk-review
+version: 1
+name: Service Ticket Churn Risk Review
+description: >
+  Reviews customers with repeated service tickets in a recent window and
+  drafts a churn-risk summary with recommended outreach. Use this if a
+  customer has ever quietly churned after their third outage ticket
+  because nobody connected the dots between separate complaints.
+category: telecom
+tags: [telecom, churn, support, retention]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: hybrid
+command: >
+  awk -F',' -v min_tickets="{{min_ticket_count}}" -v days="{{lookback_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 ticket_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      age_days = (now_epoch - ticket_epoch) / 86400;
+      if (age_days <= days) count[$1]++;
+    }
+    END {
+      for (c in count) if (count[c] >= min_tickets) printf "%s: %d tickets in last %d days\n", c, count[c], days;
+    }
+  ' "{{tickets_csv_path}}"
+prompt: |
+  Here is the customer's recent service ticket history: {{tickets_csv_path}}
+  (columns: customer,ticket_date,issue_summary). Customers with
+  {{min_ticket_count}}+ tickets in the last {{lookback_days}} days are at
+  elevated churn risk.
+  1. For each flagged customer, summarize the pattern of issues (repeat
+     outages, slow speeds, billing disputes, etc.).
+  2. Assess churn risk as low/medium/high based on ticket frequency and
+     issue severity.
+  3. Draft a short, specific outreach note (not generic) that account
+     management could send or use as a call script — reference the actual
+     issues so the customer feels heard, not processed.
+script_note: >
+  The shell command gives you the raw list of customers who crossed the
+  ticket-count threshold — zero tokens, no interpretation. The prompt adds
+  issue-pattern synthesis and drafts the actual outreach message, which
+  needs judgment the script can't provide.
+variables:
+  tickets_csv_path:
+    default: "./service-tickets.csv"
+    description: "Path to a CSV with columns: customer,ticket_date (YYYY-MM-DD),issue_summary."
+  min_ticket_count:
+    default: 3
+    description: Minimum tickets in the lookback window to flag as churn risk.
+  lookback_days:
+    default: 30
+    description: Rolling window, in days, to count tickets within.
+compatible_agents: [claude, codex, hermes, generic]
+notes: Read-only analysis — does not send anything, just prepares the flag list and draft outreach for a human to review and send.

package/jobs/telecom/sla-uptime-breach-tracker.yaml

@@ -0,0 +1,36 @@
+id: sla-uptime-breach-tracker
+version: 1
+name: SLA Uptime Breach Tracker
+description: >
+  Compares each customer's measured monthly uptime percentage against
+  their contracted SLA and flags anyone below threshold. Use this if
+  you've ever missed an SLA credit obligation because nobody totaled up
+  the downtime minutes until the customer's lawyer did.
+category: telecom
+tags: [telecom, sla, uptime, contracts]
+schedule: "0 6 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v default_sla="{{default_sla_pct}}" '
+    NR==1 {next}
+    {
+      customer=$1; measured=$2; contracted=$3;
+      if (contracted == "") contracted = default_sla;
+      if (measured+0 < contracted+0) {
+        printf "SLA BREACH: %s measured %.3f%% uptime, contracted %.3f%%\n", customer, measured, contracted;
+      }
+    }
+  ' "{{uptime_csv_path}}"
+variables:
+  uptime_csv_path:
+    default: "./customer-uptime.csv"
+    description: "Path to a CSV with columns: customer,measured_uptime_pct,contracted_sla_pct (contracted column may be blank to use the default)."
+  default_sla_pct:
+    default: 99.9
+    description: Fallback contracted SLA percentage when a row doesn't specify one.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Assumes measured uptime is exported monthly from your NMS/monitoring
+  platform into the CSV before this runs. Read-only — does not issue
+  SLA credits, just flags who owes one.

package/lib/category-descriptions.js

@@ -14,6 +14,7 @@ export const CATEGORY_DESCRIPTIONS = {
   ecommerce: "Storefront ops — carts, stock, returns, reviews.",
   education: "Classroom ops — grading, attendance, deadlines, permission slips.",
   events: "Event planning — budget, RSVPs, staffing, vendors, day-of check-in.",
+  fieldservice: "Dispatch ops — tech ETAs, parts, warranty claims, maintenance contracts.",
   finance: "Personal/business finance — budgets, invoices, taxes, subscriptions.",
   fitness: "Gym/studio ops — memberships, class utilization, equipment.",
   fleet: "Vehicle fleet compliance — maintenance, registration, licenses, fuel.",
@@ -37,13 +38,16 @@ export const CATEGORY_DESCRIPTIONS = {
   personal: "Daily life reminders — bills, habits, meals, screen time.",
   podcast: "Show ops — publish cadence, guests, sponsors, ratings.",
   productivity: "Work habits — inbox, standups, focus, meetings, reports.",
+  publishing: "Book/print ops — manuscript deadlines, royalties, print runs, rights.",
   realestate: "Property management — leases, rent, vacancy, inspections, tax.",
   restaurant: "Kitchen/FOH ops — food cost, labor cost, waste, inspections.",
   retail: "Store ops — till reconciliation, opening checklist, scheduling.",
   sales: "Pipeline ops — leads, deals, quota, CRM sync.",
   security: "Security posture — keys, certs, access, scans, firewalls.",
+  spa: "Salon/spa/wellness ops — no-shows, inventory, license renewals, membership churn.",
   support: "Helpdesk ops — SLA, backlog, CSAT, agent workload.",
   team: "Team ops — 1:1s, on-call, PTO, anniversaries.",
+  telecom: "ISP/telecom ops — outages, SLA uptime, circuit provisioning, churn.",
   travel: "Trip logistics — flights, passports, visas, insurance, miles.",
   veterinary: "Clinic ops for animals — vaccines, controlled substances, boarding.",
   warehousing: "Warehouse ops — dock scheduling, pick/pack errors, climate control.",

package/lib/duplicates-allowlist.js

@@ -11,6 +11,11 @@ export const ALLOWED_DUPLICATE_PAIRS = [
     "labor-cost-percentage-watch",
     "Same benchmark-against-sales pattern, different cost categories (food vs. labor) — intentionally parallel jobs, not a copy-paste duplicate.",
   ],
+  [
+    "warranty-claim-deadline-check",
+    "warranty-claim-expiry-check",
+    "Same deadline-check pattern, different domains — automotive repair-order warranty claims vs. HVAC/appliance manufacturer warranty claims.",
+  ],
 ];
 
 export function isAllowedPair(idA, idB) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wonsukchoi/crondex",
-  "version": "0.20.0",
+  "version": "0.21.0",
   "description": "A public directory of pre-made, agent-editable cron jobs.",
   "type": "module",
   "license": "MIT",