@wonsukchoi/crondex 0.20.1 → 0.22.0

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,16 @@ 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.",
+  ],
+  [
+    "claim-status-check",
+    "landlord-insurance-claim-status-check",
+    "Same stale-claim-followup goal, different mechanism and scale — generic insurance job is agent-prompt for a single policyholder's claims; realestate job is a zero-token shell scan over a property portfolio's claims CSV.",
+  ],
 ];
 
 export function isAllowedPair(idA, idB) {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wonsukchoi/crondex",
-  "version": "0.20.1",
+  "version": "0.22.0",
   "description": "A public directory of pre-made, agent-editable cron jobs.",
   "type": "module",
   "license": "MIT",
@@ -38,7 +38,7 @@
     "lint-shell": "node scripts/lint-shell.js",
     "check-duplicates": "node scripts/check-duplicates.js",
     "smoke-test": "node scripts/smoke-test.js",
-    "test": "node --test"
+    "test": "node --test \"test/*.test.js\""
   },
   "dependencies": {
     "js-yaml": "^4.1.0"