@wonsukchoi/crondex 0.21.0 → 0.23.0

package/jobs/sales/referral-followup-tracker.yaml

@@ -0,0 +1,40 @@
+id: referral-followup-tracker
+version: 1
+name: Referral Follow-Up Tracker
+description: >
+  Flags customer referrals that were asked for or given, and haven't had a
+  logged follow-up after a set number of days. Use this if a happy
+  customer has ever offered a referral introduction and it fell through
+  the cracks because nobody owned the follow-up.
+category: sales
+tags: [sales, referrals, advocacy, follow-up]
+schedule: "0 9 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v wait_days="{{wait_days}}" '
+    NR==1 {next}
+    $5 == "yes" {next}
+    {
+      customer=$1; referred_contact=$2; requested_date=$3; owner=$4;
+      cmd = "date -d \"" requested_date "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" requested_date "\" +%s 2>/dev/null";
+      cmd | getline req_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      days = (now_epoch - req_epoch) / 86400;
+      if (days >= wait_days) {
+        printf "NEEDS FOLLOW-UP: %s referred %s (owner: %s) — %d day(s) since requested\n", customer, referred_contact, owner, days;
+      }
+    }
+  ' "{{referrals_csv_path}}"
+variables:
+  referrals_csv_path:
+    default: "./referrals.csv"
+    description: "Path to a CSV with columns: customer_name,referred_contact,requested_date,owner,followed_up (yes/no; requested_date is YYYY-MM-DD)."
+  wait_days:
+    default: 5
+    description: Days after a referral is logged before it's flagged as overdue for a follow-up.
+compatible_agents: [generic, claude, codex]
+notes: >
+  You maintain referrals.csv yourself (log it when a customer offers or
+  makes an introduction, mark followed_up=yes once the owner reaches out)
+  — doesn't integrate with any CRM directly.

package/jobs/sales/territory-coverage-gap-check.yaml

@@ -0,0 +1,43 @@
+id: territory-coverage-gap-check
+version: 1
+name: Territory Coverage Gap Check
+description: >
+  Flags target accounts that have no assigned rep, or have an assigned
+  rep but no logged activity in a long time. Use this if an account has
+  ever gone completely unworked for months simply because it fell between
+  territory reassignments and nobody noticed the gap.
+category: sales
+tags: [sales, territory, account-coverage, ops]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v stale_days="{{stale_days}}" '
+    NR==1 {next}
+    {
+      account=$1; rep=$2; last_activity=$3;
+      if (rep == "" ) {
+        printf "UNASSIGNED: %s has no assigned rep\n", account;
+        next;
+      }
+      cmd = "date -d \"" last_activity "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" last_activity "\" +%s 2>/dev/null";
+      cmd | getline last_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      days = (now_epoch - last_epoch) / 86400;
+      if (days >= stale_days) {
+        printf "NO ACTIVITY: %s (rep: %s) — %d day(s) since last activity\n", account, rep, days;
+      }
+    }
+  ' "{{accounts_csv_path}}"
+variables:
+  accounts_csv_path:
+    default: "./target-accounts.csv"
+    description: "Path to a CSV with columns: account_name,assigned_rep,last_activity_date (YYYY-MM-DD; assigned_rep blank if unowned)."
+  stale_days:
+    default: 45
+    description: Days without logged activity on an assigned account before it's flagged as a coverage gap.
+compatible_agents: [generic, claude, codex]
+notes: >
+  You maintain target-accounts.csv yourself (or export it from your CRM's
+  account list) — this is a coverage/ownership check, not a deal-level
+  staleness check (see `stale-deal-nudge` for that).

package/jobs/veterinary/appointment-no-show-rate-tracker.yaml

@@ -0,0 +1,49 @@
+id: appointment-no-show-rate-tracker
+version: 1
+name: Appointment No-Show Rate Tracker
+description: >
+  Calculates the weekly no-show rate from a logged appointment history and
+  flags when it crosses a threshold. Use this if the clinic has ever kept
+  eating empty exam-room slots without noticing the no-show rate had
+  crept up until the schedule was visibly hurting revenue — this tracks
+  the aggregate trend, distinct from a per-appointment outreach job.
+category: veterinary
+tags: [veterinary, appointments, no-show, scheduling, metrics]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v cutoff="{{lookback_days}}" -v threshold="{{alert_threshold_pct}}" '
+    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");
+      age_days = (now_epoch - appt_epoch) / 86400;
+      if (age_days >= 0 && age_days <= cutoff) {
+        total++;
+        if ($3 == "no-show") noshow++;
+      }
+    }
+    END {
+      if (total > 0) {
+        rate = (noshow / total) * 100;
+        printf "NO-SHOW RATE: %d/%d appointments in last %d day(s) = %.1f%%\n", noshow, total, cutoff, rate;
+        if (rate >= threshold) printf "ALERT: no-show rate %.1f%% is at or above the %.1f%% threshold\n", rate, threshold;
+      } else {
+        print "No appointments found in the lookback window.";
+      }
+    }
+  ' "{{appointments_csv_path}}"
+variables:
+  appointments_csv_path:
+    default: "./appointments.csv"
+    description: "Path to a CSV with columns: pet_name,appointment_date (YYYY-MM-DD),status (arrived/no-show/cancelled)."
+  lookback_days:
+    default: 7
+    description: How many trailing days of appointments to include in the rate calculation.
+  alert_threshold_pct:
+    default: 10
+    description: No-show rate percentage that triggers an alert.
+compatible_agents: [generic, claude, codex]
+notes: Zero-token trend check — pair with a per-appointment outreach job if you also want to contact each no-show individually.

package/jobs/veterinary/boarding-kennel-capacity-utilization-check.yaml

@@ -0,0 +1,39 @@
+id: boarding-kennel-capacity-utilization-check
+version: 1
+name: Boarding/Kennel Capacity Utilization Check
+description: >
+  Compares today's occupied boarding runs/kennels against total capacity
+  and warns when utilization crosses a threshold. Use this if the front
+  desk has ever accepted a boarding reservation only to discover at
+  drop-off that every run was already full — this tracks overall
+  occupancy, distinct from boarding-checkout-reminder.yaml which tracks
+  individual checkout dates.
+category: veterinary
+tags: [veterinary, boarding, kennel, capacity, occupancy]
+schedule: "0 6 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%Y-%m-%d);
+  occupied=$(awk -F',' -v today="$today" '
+    NR==1 {next}
+    $3 <= today && $4 >= today {count++}
+    END {print count+0}
+  ' "{{boarding_csv_path}}");
+  total="{{total_kennel_capacity}}";
+  warn="{{warn_threshold_pct}}";
+  pct=$(awk -v o="$occupied" -v t="$total" 'BEGIN { printf "%.1f", (t>0)?(o/t*100):0 }');
+  echo "OCCUPANCY: $occupied/$total runs occupied today ($pct%)";
+  awk -v pct="$pct" -v warn="$warn" 'BEGIN { if (pct+0 >= warn+0) print "ALERT: occupancy at or above " warn "% — confirm capacity before accepting more reservations." }'
+variables:
+  boarding_csv_path:
+    default: "./boarding-schedule.csv"
+    description: "Path to a CSV with columns: pet_name,owner_name,checkin_date (YYYY-MM-DD),checkout_date (YYYY-MM-DD)."
+  total_kennel_capacity:
+    default: 20
+    description: Total number of boarding runs/kennels available.
+  warn_threshold_pct:
+    default: 90
+    description: Occupancy percentage that triggers a capacity warning.
+compatible_agents: [generic, claude, codex]
+notes: Zero-token. Counts any stay whose check-in/checkout window spans today — adjust the CSV export cadence to keep this current through the day.

package/jobs/veterinary/client-payment-plan-delinquency-check.yaml

@@ -0,0 +1,36 @@
+id: client-payment-plan-delinquency-check
+version: 1
+name: Client Payment Plan Delinquency Check
+description: >
+  Checks active client payment plans (e.g. for a large surgery or
+  emergency bill) against their installment schedule and flags anyone
+  who's missed a payment. Use this if a payment plan has ever quietly
+  gone delinquent for months because nobody was cross-checking installment
+  due dates against what actually came in.
+category: veterinary
+tags: [veterinary, billing, payment-plans, collections, clients]
+schedule: "0 9 1,15 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v grace_days="{{grace_period_days}}" '
+    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 >= grace_days) {
+        printf "DELINQUENT: %s — installment $%s due %s (%d days overdue), plan total $%s\n", $1, $2, $3, overdue_days, $5;
+      }
+    }
+  ' "{{payment_plans_csv_path}}"
+variables:
+  payment_plans_csv_path:
+    default: "./payment-plans.csv"
+    description: "Path to a CSV with columns: owner_name,installment_amount,due_date (YYYY-MM-DD),status (paid/unpaid),plan_total_amount."
+  grace_period_days:
+    default: 5
+    description: Days past the due date before a missed installment is flagged as delinquent.
+compatible_agents: [generic, claude, codex]
+notes: Read-only aging check — actual collections outreach and any plan renegotiation should follow your practice's billing policy.

package/jobs/veterinary/dvm-license-dea-registration-expiry-check.yaml

@@ -0,0 +1,41 @@
+id: dvm-license-dea-registration-expiry-check
+version: 1
+name: Veterinarian License & DEA Registration Expiry Check
+description: >
+  Checks each veterinarian's state license and DEA registration expiry
+  dates and warns before either lapses. Use this if a vet has ever
+  discovered a lapsed DEA registration only when trying to write a
+  controlled-substance prescription — distinct from
+  license-credential-expiry-check.yaml in healthcare, which tracks
+  general staff credentials rather than the DVM license plus DEA
+  dual-registration requirement specific to prescribing controlled
+  substances for animal patients.
+category: veterinary
+tags: [veterinary, compliance, licensing, dea, 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 license_expiry_epoch; close(cmd);
+      cmd2 = "date -d \"" $4 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $4 "\" +%s 2>/dev/null";
+      cmd2 | getline dea_expiry_epoch; close(cmd2);
+      "date +%s" | getline now_epoch; close("date +%s");
+      license_days = (license_expiry_epoch - now_epoch) / 86400;
+      dea_days = (dea_expiry_epoch - now_epoch) / 86400;
+      if (license_days <= days) printf "EXPIRING: %s — state license expires %s (%d days)\n", $1, $3, license_days;
+      if (dea_days <= days) printf "EXPIRING: %s — DEA registration expires %s (%d days)\n", $1, $4, dea_days;
+    }
+  ' "{{credential_csv_path}}"
+variables:
+  credential_csv_path:
+    default: "./dvm-credentials.csv"
+    description: "Path to a CSV with columns: veterinarian_name,state,license_expiry_date (YYYY-MM-DD),dea_expiry_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 60
+    description: How many days before expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a maintained CSV export from your credentialing/HR system. A lapsed DEA registration blocks legal prescribing of controlled substances — treat DEA warnings as higher priority than license warnings.

package/jobs/veterinary/microchip-registration-verification-check.yaml

@@ -0,0 +1,40 @@
+id: microchip-registration-verification-check
+version: 1
+name: Microchip Registration Verification Check
+description: >
+  Reviews recently implanted microchips and checks whether the chip was
+  actually registered with the manufacturer's database under the owner's
+  current contact info. Use this if a lost pet has ever been scanned at
+  a shelter, chip found, but the registry came back with no owner info
+  or an outdated phone number — the chip is only useful if the
+  registration behind it is current.
+category: veterinary
+tags: [veterinary, microchip, registration, patients, compliance]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review the list of pets microchipped in the last {{lookback_days}} days
+  from {{practice_management_system}}: {{unregistered_chips_list}}.
+  1. For each chip, note whether the record shows it was registered with
+     the manufacturer's registry (e.g. HomeAgain, 24PetWatch, AKC
+     Reunite) and, if so, whether the owner contact info on file matches
+     the registry.
+  2. List any chip implanted but with no registration confirmed, and any
+     chip where the owner's phone/email on file has since changed
+     without the registry being updated.
+  3. Draft a short reminder message for owners with unregistered or
+     stale-registration chips, explaining briefly why an unregistered
+     chip won't reunite them with a lost pet.
+variables:
+  practice_management_system:
+    default: "your practice management system"
+    description: Name of the system where microchip implant records live.
+  unregistered_chips_list:
+    default: "the clinic's microchip implant log for the period"
+    description: Source of implanted-chip records to check against registry status.
+  lookback_days:
+    default: 30
+    description: How far back to check for recently implanted chips.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only outreach — registry lookups may require checking the specific manufacturer's site or portal, since there's no single universal microchip registry.

package/jobs/veterinary/patient-record-completeness-audit.yaml

@@ -0,0 +1,41 @@
+id: patient-record-completeness-audit
+version: 1
+name: Patient (Pet) Record Completeness Audit
+description: >
+  Spot-checks a sample of recent patient records for missing required
+  fields — weight, vaccine history, allergy flags, microchip number — and
+  lists the gaps. Use this if a chart has ever been missing a documented
+  drug allergy right when it mattered, because record completeness was
+  never actually reviewed, only assumed.
+category: veterinary
+tags: [veterinary, records, compliance, audit, patients]
+schedule: "0 10 * * 3"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review a sample of {{sample_size}} recent patient records from
+  {{practice_management_system}}, prioritizing patients seen in the last
+  {{lookback_days}} days.
+  1. For each record, check whether the following are present and current:
+     current weight, vaccine history, known allergies (or "none recorded"
+     explicitly, not just blank), and microchip number.
+  2. List each record with missing fields, grouped by which field is
+     missing most often across the sample — that's usually the intake
+     step actually breaking down.
+  3. Flag any record where an allergy field is blank rather than
+     explicitly marked "none" — a blank field is ambiguous and riskier
+     than a marked "none."
+  4. Suggest one process fix if the same field is missing across most of
+     the sample (e.g. "weight isn't being logged at check-in").
+variables:
+  practice_management_system:
+    default: "your practice management system"
+    description: Name of the system where patient records live.
+  sample_size:
+    default: 20
+    description: Number of recent records to sample for the audit.
+  lookback_days:
+    default: 30
+    description: How far back to pull records from for the sample.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Sampling audit, not a full chart review — use findings to spot a broken intake step, not to grade individual staff.

package/jobs/veterinary/pet-medication-refill-backlog-check.yaml

@@ -0,0 +1,36 @@
+id: pet-medication-refill-backlog-check
+version: 1
+name: Pet Medication Refill Request Backlog Check
+description: >
+  Checks pending prescription/food refill requests against how long
+  they've been waiting and flags anything past a reasonable turnaround.
+  Use this if a client has ever run out of a pet's chronic medication
+  (e.g. thyroid or seizure medication) because a refill request sat
+  unanswered in the queue over a weekend.
+category: veterinary
+tags: [veterinary, prescriptions, refills, patients, medication]
+schedule: "0 9,15 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v hours="{{escalate_after_hours}}" '
+    NR==1 {next}
+    $4 == "pending" {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline requested_epoch; close(cmd);
+      age_hours = (today - requested_epoch) / 3600;
+      if (age_hours >= hours) {
+        printf "REFILL PENDING: %s (%s) — %s requested %s (%d hrs ago)\n", $1, $2, $5, $3, age_hours;
+      }
+    }
+  ' "{{refill_requests_csv_path}}"
+variables:
+  refill_requests_csv_path:
+    default: "./pet-refill-requests.csv"
+    description: "Path to a CSV with columns: pet_name,owner_name,requested_date (YYYY-MM-DD),status (pending/approved/denied),medication."
+  escalate_after_hours:
+    default: 48
+    description: Hours a refill request can sit pending before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: Read-only triage — actual approval of a refill is a clinical decision made by the veterinarian, not this job. Flag chronic/maintenance medications for priority handling.

package/jobs/veterinary/puppy-kitten-vaccine-series-compliance-check.yaml

@@ -0,0 +1,39 @@
+id: puppy-kitten-vaccine-series-compliance-check
+version: 1
+name: Puppy/Kitten Vaccine Series Compliance Check
+description: >
+  Tracks young patients partway through their initial multi-dose vaccine
+  series and flags anyone who missed the next dose window. Use this if a
+  puppy or kitten has ever fallen off after the first shot in a series,
+  leaving them under-protected because nobody tracked series progress
+  separately from routine adult booster due dates — distinct from
+  pet-vaccine-due-reminder.yaml, which tracks single due-date reminders
+  rather than a multi-dose series with its own interval rules.
+category: veterinary
+tags: [veterinary, vaccine, puppy, kitten, patients]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review the puppy/kitten vaccine series tracking export from
+  {{practice_management_system}} for patients currently mid-series
+  (i.e. have had at least one dose of a multi-dose series but not the
+  final dose).
+  1. For each patient, note the series (e.g. DHPP, FVRCP), which dose
+     number they're on, the date of their last dose, and the
+     recommended interval to the next dose ({{series_interval_weeks}}
+     weeks is typical but confirm against the specific vaccine's label).
+  2. Flag anyone past their expected next-dose window with no
+     appointment booked.
+  3. Sort by most overdue first, since a gap in a puppy/kitten series
+     can mean restarting the series depending on how long the gap was.
+  4. Draft a short reminder message per overdue patient for the owner.
+variables:
+  practice_management_system:
+    default: "your practice management system"
+    description: Name of the system where vaccine series records live.
+  series_interval_weeks:
+    default: 3
+    description: Typical interval in weeks between doses in a puppy/kitten vaccine series (varies by vaccine and product label).
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — always confirm dosing interval and restart rules against the specific vaccine manufacturer's label, since gap tolerance varies by product.

package/jobs/veterinary/senior-pet-wellness-recall-tracker.yaml

@@ -0,0 +1,43 @@
+id: senior-pet-wellness-recall-tracker
+version: 1
+name: Senior Pet Wellness Recall Tracker
+description: >
+  Finds senior pets (past a configurable age threshold) who are overdue
+  for a semi-annual senior wellness exam or bloodwork panel and drafts
+  outreach. Use this if an older pet has ever gone a full year between
+  visits when twice-yearly senior screening would have caught a treatable
+  condition early — distinct from pet-vaccine-due-reminder.yaml, which
+  tracks vaccine due dates rather than age-based wellness screening
+  cadence.
+category: veterinary
+tags: [veterinary, senior-pets, wellness, recall, outreach]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check {{practice_management_system}} for patients aged
+  {{senior_age_threshold_years}} years or older whose last wellness
+  exam or senior bloodwork panel was more than
+  {{recall_interval_months}} months ago, with no future appointment
+  booked.
+  1. List each pet, species/breed if known, last visit date, and how
+     overdue they are.
+  2. Sort by most overdue first.
+  3. Draft a short outreach message per pet (or a reusable template)
+     inviting the owner to book a senior wellness visit, mentioning
+     that early screening catches age-related conditions while they're
+     still manageable.
+  4. Separately call out any pet more than double the recall interval
+     overdue.
+variables:
+  practice_management_system:
+    default: "your practice management system"
+    description: Name of the system where appointment history lives.
+  senior_age_threshold_years:
+    default: 7
+    description: Age in years at which a pet is treated as a senior for recall purposes.
+  recall_interval_months:
+    default: 6
+    description: How many months between senior wellness visits before a pet counts as due.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — outreach messages should be reviewed by staff before sending. Senior age threshold varies by species/breed; adjust the default per your patient mix.

package/jobs/veterinary/spay-neuter-followup-compliance-check.yaml

@@ -0,0 +1,35 @@
+id: spay-neuter-followup-compliance-check
+version: 1
+name: Spay/Neuter Post-Op Follow-Up Compliance Check
+description: >
+  Checks which spay/neuter patients are due for their post-op recheck
+  (incision check, suture removal) and haven't had one logged. Use this
+  if a pet has ever developed an incision complication that would have
+  been caught at a recheck nobody scheduled or confirmed happened.
+category: veterinary
+tags: [veterinary, surgery, post-op, follow-up, compliance]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v window="{{recheck_window_days}}" '
+    NR==1 {next}
+    $4 != "completed" {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline surgery_epoch; close(cmd);
+      days_since = (today - surgery_epoch) / 86400;
+      if (days_since >= window) {
+        printf "NO RECHECK LOGGED: %s (%s) — surgery %s, %d days ago, recheck status: %s\n", $1, $3, $2, days_since, $4;
+      }
+    }
+  ' "{{spay_neuter_csv_path}}"
+variables:
+  spay_neuter_csv_path:
+    default: "./spay-neuter-cases.csv"
+    description: "Path to a CSV with columns: pet_name,surgery_date (YYYY-MM-DD),owner_name,recheck_status (scheduled/completed/none)."
+  recheck_window_days:
+    default: 10
+    description: Days after surgery by which a post-op recheck should be scheduled or completed.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a maintained export from your practice management system — this is a backstop for cases that fell out of the recheck workflow, not a substitute for discharge instructions.

package/jobs/veterinary/specialist-referral-followup-check.yaml

@@ -0,0 +1,38 @@
+id: specialist-referral-followup-check
+version: 1
+name: Veterinary Specialist Referral Follow-Up Check
+description: >
+  Checks outbound referrals to veterinary specialists (cardiology,
+  oncology, orthopedic surgery, etc.) that haven't been scheduled or
+  completed within a set window and flags them for follow-up. Use this
+  if a pet has ever been referred out for a serious condition and the
+  primary clinic never confirmed the owner actually followed through and
+  got the specialist appointment.
+category: veterinary
+tags: [veterinary, referrals, specialists, follow-up, care-coordination]
+schedule: "0 8 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" -v days="{{stale_days}}" '
+    NR==1 {next}
+    $4 != "" {next}
+    {
+      cmd = "date -d \"" $3 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $3 "\" +%s 2>/dev/null";
+      cmd | getline sent_epoch; close(cmd);
+      pending_days = (today - sent_epoch) / 86400;
+      if (pending_days >= days) {
+        printf "STALE REFERRAL: %s -> %s (%s) sent %s (%d days pending, no scheduled date)\n", $1, $2, $5, $3, pending_days;
+      }
+    }
+  ' "{{referrals_csv_path}}"
+variables:
+  referrals_csv_path:
+    default: "./specialist-referrals.csv"
+    description: "Path to a CSV with columns: pet_name,specialist_name,referral_sent_date (YYYY-MM-DD),scheduled_date (blank if not yet scheduled),specialty."
+  stale_days:
+    default: 14
+    description: Days since a referral was sent, with no scheduled date, before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a maintained CSV export of outbound specialist referrals from your practice management system; adjust columns to match your export.

package/jobs/veterinary/surgical-schedule-utilization-check.yaml

@@ -0,0 +1,36 @@
+id: surgical-schedule-utilization-check
+version: 1
+name: Surgical Schedule/OR Utilization Check
+description: >
+  Calculates how much of tomorrow's surgical suite time is booked versus
+  open, so scheduling can fill gaps or flag overbooking. Use this if the
+  OR has ever sat half-empty on a weekday because nobody was watching
+  utilization, or double-booked because two procedures landed in the
+  same block — distinct from surgery-prep-check.yaml, which checks
+  individual case readiness (bloodwork/consent) rather than schedule
+  utilization.
+category: veterinary
+tags: [veterinary, surgery, scheduling, utilization, operations]
+schedule: "0 16 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  tomorrow=$(date -d "+1 day" +%Y-%m-%d 2>/dev/null || date -v+1d +%Y-%m-%d);
+  awk -F',' -v tomorrow="$tomorrow" -v capacity="{{available_or_minutes}}" '
+    NR==1 {next}
+    $2 == tomorrow { booked += $3; slots[$4]++ }
+    END {
+      pct = (capacity > 0) ? (booked / capacity * 100) : 0;
+      printf "OR UTILIZATION for %s: %d/%d minutes booked (%.1f%%)\n", tomorrow, booked, capacity, pct;
+      for (room in slots) if (slots[room] > 1) printf "POSSIBLE DOUBLE-BOOK: OR %s has %d procedures scheduled\n", room, slots[room];
+    }
+  ' "{{surgery_schedule_csv_path}}"
+variables:
+  surgery_schedule_csv_path:
+    default: "./surgery-schedule-detailed.csv"
+    description: "Path to a CSV with columns: pet_name,surgery_date (YYYY-MM-DD),duration_minutes,or_room."
+  available_or_minutes:
+    default: 480
+    description: Total surgical suite minutes available in a working day (e.g. 8 hours = 480).
+compatible_agents: [generic, claude, codex]
+notes: Zero-token. Flags overlapping bookings in the same OR room as a possible double-book — verify against the actual schedule before reassigning.

package/jobs/veterinary/vet-staff-ce-credit-tracking.yaml

@@ -0,0 +1,36 @@
+id: vet-staff-ce-credit-tracking
+version: 1
+name: Veterinary Staff CE Credit Tracking
+description: >
+  Reviews each veterinarian and licensed vet tech's continuing education
+  (CE) credit hours against what their state board requires by license
+  renewal, and flags anyone on track to fall short. Use this if a
+  provider has ever discovered close to renewal that they were short on
+  RACE-approved CE hours needed to keep their license active — distinct
+  from dvm-license-dea-registration-expiry-check.yaml, which tracks the
+  license's own expiry date rather than the ongoing education
+  requirement to renew it.
+category: veterinary
+tags: [veterinary, continuing-education, compliance, licensing, staff]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review the CE tracking export from {{ce_tracking_system}} for all
+  veterinarians and licensed vet techs.
+  1. For each staff member, compare CE hours completed this cycle
+     against the hours required by their state board (note: this varies
+     by state and by whether they're a DVM or LVT/CVT — flag if you're
+     unsure of the requirement rather than guessing).
+  2. List anyone whose completed hours, at the current pace, won't reach
+     the requirement before their cycle end date.
+  3. Sort by soonest cycle end date first.
+  4. Suggest which upcoming CE opportunities (conferences, RACE-approved
+     online courses) would close the gap, if that information is
+     available.
+variables:
+  ce_tracking_system:
+    default: "your CE tracking spreadsheet or HR/credentialing system"
+    description: Where completed CE hours and cycle end dates are recorded.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Requires knowing each state board's specific CE hour requirement, which varies — verify against the actual state veterinary board rule before treating a flagged shortfall as final.

package/jobs/warehousing/conveyor-sortation-downtime-watch.yaml

@@ -0,0 +1,48 @@
+id: conveyor-sortation-downtime-watch
+version: 1
+name: Conveyor & Sortation System Downtime Watch
+description: >
+  Checks the material handling system's downtime log for conveyor and
+  sortation equipment and flags outages exceeding a target duration, or
+  a segment with repeat outages in the period. Use this if a conveyor
+  jam has ever backed up the whole outbound line for an hour while
+  everyone treated it as a one-off instead of the third time that
+  segment failed this week.
+category: warehousing
+tags: [warehousing, conveyor, sortation, downtime, equipment]
+schedule: "0 21 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v max_min="{{max_outage_minutes}}" -v repeat="{{repeat_outage_threshold}}" '
+    NR==1 {next}
+    {
+      segment=$1; minutes=$3; count[segment]++; total[segment]+=minutes;
+      if (minutes >= max_min) {
+        printf "LONG OUTAGE: segment %s — %d min outage (%s), reason: %s\n", segment, minutes, $2, $4;
+      }
+    }
+    END {
+      for (s in count) {
+        if (count[s] >= repeat) {
+          printf "REPEAT OUTAGES: segment %s — %d outage(s) totaling %d min today\n", s, count[s], total[s];
+        }
+      }
+    }
+  ' "{{conveyor_downtime_csv_path}}"
+variables:
+  conveyor_downtime_csv_path:
+    default: "./conveyor-downtime-log.csv"
+    description: "Path to a CSV with columns: segment_id,started_at,duration_minutes,reason — one row per conveyor/sortation outage."
+  max_outage_minutes:
+    default: 20
+    description: Minutes a single outage can run before it's flagged individually.
+  repeat_outage_threshold:
+    default: 3
+    description: Number of outages on the same segment in one day that triggers a repeat-outage flag.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Covers material handling automation (conveyors, sorters) inside the
+  warehouse, distinct from manufacturing's production-line-downtime-watch,
+  which tracks stoppages on production/assembly lines rather than
+  outbound material handling systems.