@wonsukchoi/crondex 0.20.0 → 0.21.0

package/jobs/fieldservice/maintenance-contract-renewal-check.yaml

@@ -0,0 +1,36 @@
+id: maintenance-contract-renewal-check
+version: 1
+name: Maintenance Contract Renewal Check
+description: >
+  Checks recurring service/maintenance contracts (annual HVAC tune-ups,
+  quarterly plumbing inspections) against their renewal date and flags
+  any coming up so the customer can be rebooked before the contract
+  lapses. Use this if a maintenance customer has ever silently churned
+  because nobody called to renew before the term ran out.
+category: fieldservice
+tags: [fieldservice, maintenance-contract, renewal, recurring-revenue]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v warn="{{warn_days_before}}" '
+    NR==1 {next}
+    $4 == "active" {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline renewal_epoch; close(cmd);
+      days_left = (renewal_epoch - today) / 86400;
+      if (days_left <= warn && days_left >= 0) {
+        printf "RENEWAL DUE: contract %s for %s — renews %s (%d days left)\n", $1, $2, $3, days_left;
+      }
+    }
+  ' "{{maintenance_contracts_csv_path}}"
+variables:
+  maintenance_contracts_csv_path:
+    default: "./maintenance-contracts.csv"
+    description: "Path to a CSV with columns: contract_id,customer_name,renewal_date (YYYY-MM-DD),status (active/lapsed/cancelled)."
+  warn_days_before:
+    default: 21
+    description: Days before renewal to start warning, giving time to schedule the visit.
+compatible_agents: [generic, claude, codex]
+notes: Reach out to schedule the renewal visit once flagged — this job only surfaces the upcoming date, it doesn't book anything.

package/jobs/fieldservice/parts-low-stock-reorder-check.yaml

@@ -0,0 +1,29 @@
+id: parts-low-stock-reorder-check
+version: 1
+name: Parts Low-Stock Reorder Check
+description: >
+  Checks your truck/warehouse parts inventory against reorder thresholds
+  and flags anything running low before a tech shows up on a job without
+  the capacitor or valve they need. Use this if a job has ever been
+  rescheduled because a common part was quietly out of stock.
+category: fieldservice
+tags: [fieldservice, inventory, parts, reorder]
+schedule: "0 6 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' '
+    NR==1 {next}
+    {
+      qty = $2 + 0; reorder_point = $3 + 0;
+      if (qty <= reorder_point) {
+        printf "LOW STOCK: %s — on hand %d (reorder point %d)\n", $1, qty, reorder_point;
+      }
+    }
+  ' "{{parts_inventory_csv_path}}"
+variables:
+  parts_inventory_csv_path:
+    default: "./parts-inventory.csv"
+    description: "Path to a CSV with columns: part_name,quantity_on_hand,reorder_point."
+compatible_agents: [generic, claude, codex]
+notes: Place the reorder with your supplier once flagged — this job only surfaces the shortage, it doesn't place orders.

package/jobs/fieldservice/tech-eta-no-show-check.yaml

@@ -0,0 +1,32 @@
+id: tech-eta-no-show-check
+version: 1
+name: Tech ETA No-Show Check
+description: >
+  Checks today's dispatch log for jobs where the technician's promised
+  arrival window has passed with no check-in logged. Use this if a
+  customer has ever called asking where the tech is before dispatch
+  even noticed the appointment was running late.
+category: fieldservice
+tags: [fieldservice, dispatch, eta, no-show]
+schedule: "*/30 7-18 * * 1-6"
+timezone: "UTC"
+runner: shell
+command: >
+  now=$(date +%s);
+  awk -F',' -v now="$now" '
+    NR==1 {next}
+    $5 == "dispatched" {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d\\ %H:%M \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline window_end_epoch; close(cmd);
+      if (now > window_end_epoch) {
+        late_min = (now - window_end_epoch) / 60;
+        printf "NO CHECK-IN: job %s — tech %s, window ended %s (%d min late)\n", $1, $2, $3, late_min;
+      }
+    }
+  ' "{{dispatch_log_csv_path}}"
+variables:
+  dispatch_log_csv_path:
+    default: "./dispatch-log.csv"
+    description: "Path to a CSV with columns: job_id,tech_name,eta_window_end (YYYY-MM-DD HH:MM),customer_name,status (dispatched/checked-in/completed)."
+compatible_agents: [generic, claude, codex]
+notes: Call the tech directly once flagged — this job only surfaces the miss, it doesn't page anyone.

package/jobs/fieldservice/tech-license-renewal-check.yaml

@@ -0,0 +1,36 @@
+id: tech-license-renewal-check
+version: 1
+name: Tech License & Certification Renewal Check
+description: >
+  Checks technician licenses and certifications (EPA 608, journeyman
+  electrician, plumbing license) against their expiration date and
+  flags any expiring soon. Use this if a tech has ever been pulled off
+  a job, or a permit rejected, because their certification quietly
+  lapsed without anyone tracking the renewal date.
+category: fieldservice
+tags: [fieldservice, license, certification, compliance]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v warn="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline expiry_epoch; close(cmd);
+      days_left = (expiry_epoch - today) / 86400;
+      if (days_left <= warn) {
+        printf "RENEWAL NEEDED: %s — %s expires %s (%d days left)\n", $1, $2, $3, days_left;
+      }
+    }
+  ' "{{tech_certifications_csv_path}}"
+variables:
+  tech_certifications_csv_path:
+    default: "./tech-certifications.csv"
+    description: "Path to a CSV with columns: tech_name,certification_type,expiration_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 30
+    description: Days before expiration to start warning, giving time to renew.
+compatible_agents: [generic, claude, codex]
+notes: Confirm renewal requirements with the issuing body (EPA, state licensing board) — this job only tracks the date, it doesn't file anything.

package/jobs/fieldservice/unpaid-invoice-aging-check.yaml

@@ -0,0 +1,35 @@
+id: unpaid-invoice-aging-check
+version: 1
+name: Unpaid Invoice Aging Check
+description: >
+  Checks invoices issued after completed jobs against their due date
+  and flags any going unpaid past your collection threshold. Use this
+  if cash has ever gotten tight because completed jobs sat uncollected
+  for weeks with nobody following up on payment.
+category: fieldservice
+tags: [fieldservice, invoicing, collections, aging]
+schedule: "0 9 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v max_days="{{max_days_overdue}}" '
+    NR==1 {next}
+    $4 == "unpaid" {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      overdue_days = (today - due_epoch) / 86400;
+      if (overdue_days >= max_days) {
+        printf "AGING: invoice %s for %s — $%s, due %s (%d days overdue)\n", $1, $2, $5, $3, overdue_days;
+      }
+    }
+  ' "{{invoices_csv_path}}"
+variables:
+  invoices_csv_path:
+    default: "./invoices.csv"
+    description: "Path to a CSV with columns: invoice_id,customer_name,due_date (YYYY-MM-DD),status (unpaid/paid),amount."
+  max_days_overdue:
+    default: 14
+    description: Days past the due date before an unpaid invoice is flagged.
+compatible_agents: [generic, claude, codex]
+notes: Send a payment reminder or call the customer once flagged — this job only surfaces the aging balance, it doesn't send anything.

package/jobs/fieldservice/unresolved-callback-tracker.yaml

@@ -0,0 +1,35 @@
+id: unresolved-callback-tracker
+version: 1
+name: Unresolved Callback Tracker
+description: >
+  Flags customer callbacks (a return visit for the same issue within
+  the warranty window) that are still open past a set number of days.
+  Use this if a rework job has ever slipped through the cracks and the
+  customer had to call a second time to get it actually fixed.
+category: fieldservice
+tags: [fieldservice, callback, rework, quality]
+schedule: "0 9 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v max_days="{{max_open_days}}" '
+    NR==1 {next}
+    $4 == "open" {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline reported_epoch; close(cmd);
+      open_days = (today - reported_epoch) / 86400;
+      if (open_days >= max_days) {
+        printf "STALE CALLBACK: %s — original job %s, open %d days, tech %s\n", $1, $3, open_days, $5;
+      }
+    }
+  ' "{{callbacks_csv_path}}"
+variables:
+  callbacks_csv_path:
+    default: "./callbacks.csv"
+    description: "Path to a CSV with columns: callback_id,reported_date (YYYY-MM-DD),original_job_id,status (open/resolved),assigned_tech."
+  max_open_days:
+    default: 3
+    description: How many days a callback can stay open before it's flagged as stale.
+compatible_agents: [generic, claude, codex]
+notes: Reassign or escalate the callback once flagged — this job only surfaces aging rework, it doesn't dispatch anyone.

package/jobs/fieldservice/warranty-claim-expiry-check.yaml

@@ -0,0 +1,35 @@
+id: warranty-claim-expiry-check
+version: 1
+name: Warranty Claim Expiry Check
+description: >
+  Checks open equipment warranty claims (HVAC units, water heaters,
+  appliances) against the manufacturer's filing deadline and flags any
+  about to lapse unfiled. Use this if a claim has ever been denied
+  because it was submitted a day after the manufacturer's window closed.
+category: fieldservice
+tags: [fieldservice, warranty, claims, deadline]
+schedule: "0 8 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v warn="{{warn_days_before}}" '
+    NR==1 {next}
+    $4 == "open" {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline deadline_epoch; close(cmd);
+      days_left = (deadline_epoch - today) / 86400;
+      if (days_left <= warn) {
+        printf "EXPIRING: claim %s for job %s — due %s (%d days left)\n", $1, $2, $3, days_left;
+      }
+    }
+  ' "{{warranty_claims_csv_path}}"
+variables:
+  warranty_claims_csv_path:
+    default: "./warranty-claims.csv"
+    description: "Path to a CSV with columns: claim_id,job_id,filing_deadline (YYYY-MM-DD),status (open/submitted)."
+  warn_days_before:
+    default: 5
+    description: Days before the filing deadline to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Filing windows vary by manufacturer (Carrier, Trane, Rheem, etc.) — keep warranty-claims.csv current from your service management system export.

package/jobs/hr/{payroll-run-reminder.yaml → payroll-cutoff-checklist-reminder.yaml}

@@ -1,4 +1,4 @@
-id: payroll-run-reminder
+id: payroll-cutoff-checklist-reminder
 version: 1
 name: Payroll Run Cutoff Reminder
 description: >

package/jobs/publishing/arc-review-copy-followup.yaml

@@ -0,0 +1,35 @@
+id: arc-review-copy-followup
+version: 1
+name: ARC Review Copy Followup
+description: >
+  Flags reviewers, bloggers, or media contacts who received an advance
+  review copy (ARC) but haven't posted or filed a review within a set
+  window, so a nudge can go out before the publication date. Use this if
+  ARCs have ever been sent out and quietly forgotten with no review to show
+  for them.
+category: publishing
+tags: [publishing, arc, review-copies, marketing]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v follow={{followup_days}} '
+    NR>1 && $4 == "no" {
+      cmd="date -d \"" $3 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $3 "\" +%s";
+      cmd | getline sent_ts; close(cmd);
+      days_since = int((today - sent_ts) / 86400);
+      if (days_since >= follow) print "FOLLOW UP: " $2 " received ARC for \"" $1 "\" " days_since " days ago, no review posted";
+    }
+  ' "{{arc_recipients_csv}}"
+variables:
+  arc_recipients_csv:
+    default: "./arc-recipients.csv"
+    description: "CSV with header row, columns: title,recipient,sent_date(YYYY-MM-DD),review_posted(yes|no)."
+  followup_days:
+    default: 21
+    description: Days after sending an ARC to wait before flagging a followup nudge.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Mark review_posted=yes in arc-recipients.csv as reviews come in so they
+  stop being flagged. Pair with your publicist's contact list export.

package/jobs/publishing/isbn-registration-tracker.yaml

@@ -0,0 +1,35 @@
+id: isbn-registration-tracker
+version: 1
+name: ISBN Registration Tracker
+description: >
+  Flags upcoming titles that don't yet have an ISBN assigned and registered
+  with the relevant agency, checked against their planned publication date.
+  Use this if a title has ever hit its pub date without an ISBN because
+  registration wasn't started early enough.
+category: publishing
+tags: [publishing, isbn, metadata, pre-press]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v lead={{lead_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_left = int((pub_ts - today) / 86400);
+      if ($3 == "" && days_left <= lead) print "MISSING ISBN: \"" $1 "\" publishes in " days_left " days (" $2 ") — no ISBN registered";
+    }
+  ' "{{titles_csv}}"
+variables:
+  titles_csv:
+    default: "./upcoming-titles.csv"
+    description: "CSV with header row, columns: title,pub_date(YYYY-MM-DD),isbn(blank if not yet assigned)."
+  lead_days:
+    default: 60
+    description: Days before publication to start warning if an ISBN is still missing.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Update upcoming-titles.csv as soon as an ISBN is assigned so the title
+  drops off the warning list. Registration lead time varies by agency, so
+  set lead_days to comfortably exceed your agency's typical turnaround.

package/jobs/publishing/manuscript-deadline-tracker.yaml

@@ -0,0 +1,34 @@
+id: manuscript-deadline-tracker
+version: 1
+name: Manuscript Deadline Tracker
+description: >
+  Flags manuscript milestones (first draft, revisions, final delivery) coming
+  due from authors or editors. Use this if a book has ever slipped its
+  production schedule because a manuscript deadline only lived in an email
+  thread nobody rechecked.
+category: publishing
+tags: [publishing, manuscripts, authors, deadlines]
+schedule: "0 9 * * 1-5"
+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 due_ts; close(cmd);
+      days_left = int((due_ts - today) / 86400);
+      if (days_left <= warn) print "DUE SOON: \"" $1 "\" (" $2 ") milestone due in " days_left " days (" $3 ")";
+    }
+  ' "{{manuscripts_csv}}"
+variables:
+  manuscripts_csv:
+    default: "./manuscripts.csv"
+    description: "CSV with header row, columns: title,milestone(draft|revision|final),due_date(YYYY-MM-DD)."
+  warn_days:
+    default: 7
+    description: Days before a milestone due date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Keep manuscripts.csv updated with each title's next milestone as it's
+  scheduled or renegotiated with the author/editor.

package/jobs/publishing/permissions-clearance-tracker.yaml

@@ -0,0 +1,36 @@
+id: permissions-clearance-tracker
+version: 1
+name: Permissions Clearance Tracker
+description: >
+  Flags quoted material, images, lyrics, or other third-party content in a
+  forthcoming title that still needs permissions clearance before the book
+  goes to press. Use this if a title has ever gone to print with an
+  uncleared quote or image because clearance status wasn't tracked
+  centrally.
+category: publishing
+tags: [publishing, permissions, rights-clearance, pre-press]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v lead={{lead_days}} '
+    NR>1 && $4 != "cleared" {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline pub_ts; close(cmd);
+      days_left = int((pub_ts - today) / 86400);
+      if (days_left <= lead) print "UNCLEARED: \"" $1 "\" — item \"" $3 "\" status=" $4 ", publishes in " days_left " days";
+    }
+  ' "{{permissions_csv}}"
+variables:
+  permissions_csv:
+    default: "./permissions-clearances.csv"
+    description: "CSV with header row, columns: title,pub_date(YYYY-MM-DD),item_description,status(pending|requested|denied|cleared)."
+  lead_days:
+    default: 30
+    description: Days before publication to start warning about any item not yet marked cleared.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Update permissions-clearances.csv as each request is sent, denied, or
+  cleared. A "denied" item still shows up here deliberately — it needs
+  editorial follow-up (cut or replace) before press, not just tracking.

package/jobs/publishing/print-run-reorder-threshold-check.yaml

@@ -0,0 +1,32 @@
+id: print-run-reorder-threshold-check
+version: 1
+name: Print Run Reorder Threshold Check
+description: >
+  Flags titles whose warehouse stock has dropped below the reorder
+  threshold, so a reprint can be queued before the book goes out of stock.
+  Use this if a title has ever gone unavailable for weeks because nobody
+  noticed the print run was running low until it was already sold out.
+category: publishing
+tags: [publishing, print-run, inventory, reprints]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v default_threshold={{default_reorder_threshold}} '
+    NR>1 {
+      threshold = ($3 != "" ? $3 : default_threshold);
+      if ($2+0 <= threshold+0) print "LOW STOCK: \"" $1 "\" at " $2 " units (reorder threshold " threshold ")";
+    }
+  ' "{{stock_csv}}"
+variables:
+  stock_csv:
+    default: "./print-run-stock.csv"
+    description: "CSV with header row, columns: title,units_in_stock,reorder_threshold(optional, blank uses default)."
+  default_reorder_threshold:
+    default: 250
+    description: Fallback reorder threshold (in units) used when a title's row doesn't set its own.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Update print-run-stock.csv from your distributor or warehouse inventory
+  export before each run. Reorder threshold should account for reprint
+  lead time, not just current demand.

package/jobs/publishing/rights-license-expiry-check.yaml

@@ -0,0 +1,35 @@
+id: rights-license-expiry-check
+version: 1
+name: Rights and License Expiry Check
+description: >
+  Warns you before a granted or acquired rights/licensing deal (foreign
+  rights, film/TV options, audio, translation) expires or comes up for
+  renewal. Use this if a rights deal has ever lapsed silently because the
+  expiry date only lived in the signed contract's PDF.
+category: publishing
+tags: [publishing, rights, licensing, contracts]
+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: " $2 " rights for \"" $1 "\" expire in " days_left " days (" $3 ")";
+    }
+  ' "{{rights_csv}}"
+variables:
+  rights_csv:
+    default: "./rights-licenses.csv"
+    description: "CSV with header row, columns: title,rights_type(foreign|film|audio|translation|other),expiry_date(YYYY-MM-DD)."
+  warn_days:
+    default: 45
+    description: Days before a rights expiry date to start warning, so renegotiation or renewal can start in time.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Covers both rights you've acquired (e.g. translation rights into a
+  language) and rights you've granted out (e.g. a film option). Keep
+  rights-licenses.csv updated from your contracts database.

package/jobs/publishing/royalty-statement-due-check.yaml

@@ -0,0 +1,33 @@
+id: royalty-statement-due-check
+version: 1
+name: Royalty Statement Due Check
+description: >
+  Warns you before a royalty statement and payment is due to an author or
+  co-author. Use this if a royalty statement has ever gone out late (or
+  didn't go out at all) because the payout schedule wasn't tracked anywhere.
+category: publishing
+tags: [publishing, royalties, authors, payments]
+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 due_ts; close(cmd);
+      days_left = int((due_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: royalty statement for \"" $1 "\" due in " days_left " days (" $2 ")";
+    }
+  ' "{{royalty_schedule_csv}}"
+variables:
+  royalty_schedule_csv:
+    default: "./royalty-schedule.csv"
+    description: "CSV with header row, columns: author_or_title,statement_due_date(YYYY-MM-DD)."
+  warn_days:
+    default: 14
+    description: Days before a statement due date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Most contracts pay semiannually or quarterly on fixed dates — keep
+  royalty-schedule.csv in sync with each contract's payout cadence.

package/jobs/spa/appointment-no-show-tracker.yaml

@@ -0,0 +1,46 @@
+id: appointment-no-show-tracker
+version: 1
+name: Appointment No-Show & Late-Cancel Tracker
+description: >
+  Flags clients who no-showed or cancelled late in the past window so front
+  desk can follow up or apply a policy. Use this if a chair or treatment
+  room has ever sat empty because a client skipped without warning and
+  nobody noticed the pattern until it kept happening.
+category: spa
+tags: [spa, appointments, no-show, front-desk]
+schedule: "0 18 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{lookback_days}}" -v threshold="{{repeat_threshold}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline appt_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (now_epoch - appt_epoch) / 86400;
+      if (diff_days >= 0 && diff_days <= days && ($3 == "no-show" || $3 == "late-cancel")) {
+        count[$1]++;
+        printf "FLAGGED: %s — %s on %s\n", $1, $3, $2;
+      }
+    }
+    END {
+      for (client in count) {
+        if (count[client] >= threshold) {
+          printf "REPEAT OFFENDER: %s — %d no-show/late-cancel(s) in last %d days\n", client, count[client], days;
+        }
+      }
+    }
+  ' "{{appointments_csv_path}}"
+variables:
+  appointments_csv_path:
+    default: "./appointments.csv"
+    description: "Path to a CSV with columns: client_name,appointment_date (YYYY-MM-DD),status (no-show,late-cancel,completed,etc)."
+  lookback_days:
+    default: 30
+    description: How many days back to scan for no-shows and late cancels.
+  repeat_threshold:
+    default: 2
+    description: Number of no-show/late-cancel incidents in the lookback window before flagging a client as a repeat offender.
+compatible_agents: [generic, claude, codex]
+notes: Repeat offenders are good candidates for a deposit-required or confirm-by-text policy before their next booking.

package/jobs/spa/gift-card-expiry-check.yaml

@@ -0,0 +1,35 @@
+id: gift-card-expiry-check
+version: 1
+name: Gift Card Expiry Check
+description: >
+  Scans your gift card ledger for cards approaching their expiration date
+  with a remaining balance. Use this if a client has ever held an unused
+  gift card that quietly expired, turning a goodwill purchase into a
+  complaint at checkout.
+category: spa
+tags: [spa, gift-cards, retention, front-desk]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    $3 > 0 {
+      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 && diff_days >= 0) {
+        printf "GIFT CARD EXPIRING: %s — balance $%.2f, expires %s (%d days)\n", $1, $3, $2, diff_days;
+      }
+    }
+  ' "{{gift_cards_csv_path}}"
+variables:
+  gift_cards_csv_path:
+    default: "./gift-cards.csv"
+    description: "Path to a CSV with columns: card_code_or_holder,expiry_date (YYYY-MM-DD),remaining_balance."
+  warn_days_before:
+    default: 30
+    description: How many days before expiry to start warning, so the holder can be reminded to redeem it.
+compatible_agents: [generic, claude, codex]
+notes: Check local law before letting balances actually expire — many states restrict or ban gift card expiration, so this may need to become a "reminder only" job.

package/jobs/spa/license-renewal-tracker.yaml

@@ -0,0 +1,35 @@
+id: license-renewal-tracker
+version: 1
+name: Esthetician/Cosmetologist License Renewal Tracker
+description: >
+  Warns before a staff member's state license, certification, or
+  continuing-education deadline lapses. Use this if a technician has ever
+  shown up ready to work a shift, only to discover their license expired
+  last month and they can't legally touch a client.
+category: spa
+tags: [spa, licensing, compliance, staff]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%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 "LICENSE EXPIRING: %s (%s) — expires %s (%d days)\n", $1, $2, $3, diff_days;
+      }
+    }
+  ' "{{licenses_csv_path}}"
+variables:
+  licenses_csv_path:
+    default: "./staff-licenses.csv"
+    description: "Path to a CSV with columns: staff_name,license_type,expiry_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 30
+    description: How many days before expiry to start warning, leaving time to complete renewal or CE hours.
+compatible_agents: [generic, claude, codex]
+notes: A lapsed license can be a licensing-board violation for both the technician and the business, so warn early enough to complete any required CE hours.

package/jobs/spa/membership-unused-session-expiry-check.yaml

@@ -0,0 +1,35 @@
+id: membership-unused-session-expiry-check
+version: 1
+name: Membership/Package Unused-Session Expiry Check
+description: >
+  Flags members or package holders whose prepaid sessions or membership
+  credits are about to expire unused. Use this if a client has ever paid
+  for a monthly facial membership, banked three unused visits, and let
+  them evaporate because nobody reminded them to book.
+category: spa
+tags: [spa, membership, churn, retention]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    $4 > 0 {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%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 && diff_days >= 0) {
+        printf "CREDITS EXPIRING: %s — %d unused credit(s), expires %s (%d days)\n", $1, $4, $3, diff_days;
+      }
+    }
+  ' "{{memberships_csv_path}}"
+variables:
+  memberships_csv_path:
+    default: "./memberships.csv"
+    description: "Path to a CSV with columns: member_name,plan_name,credit_expiry_date (YYYY-MM-DD),unused_credits."
+  warn_days_before:
+    default: 10
+    description: How many days before credit expiry to start warning, while there's still time to book.
+compatible_agents: [generic, claude, codex]
+notes: A member who repeatedly lets credits expire unused is a churn risk — treat this as a retention nudge, not just a "use it or lose it" notice.