@wonsukchoi/crondex 0.21.0 → 0.23.0

package/jobs/ecommerce/failed-payment-dunning-check.yaml

@@ -0,0 +1,35 @@
+id: failed-payment-dunning-check
+version: 1
+name: Failed Payment Dunning Check
+description: >
+  Checks recurring/subscription orders with a failed payment and flags
+  ones that have been retrying too long without success, so you can step
+  in before the customer silently churns. Use this if a subscriber has
+  ever stayed on "payment failed" for weeks with nobody following up,
+  quietly costing you recurring revenue.
+category: ecommerce
+tags: [ecommerce, subscriptions, payments, dunning, churn]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v max_days="{{max_retry_days}}" -v max_attempts="{{max_retry_attempts}}" '
+    NR==1 {next}
+    $2 == "failed" {
+      if ($3+0 >= max_days || $4+0 >= max_attempts) {
+        printf "NEEDS ACTION: subscription %s — %d days failing, %d retry attempts\n", $1, $3, $4;
+      }
+    }
+  ' "{{subscriptions_csv_path}}"
+variables:
+  subscriptions_csv_path:
+    default: "./subscriptions.csv"
+    description: "Path to a CSV with columns: subscription_id,status (failed/active),days_since_first_failure,retry_attempt_count."
+  max_retry_days:
+    default: 7
+    description: Days a subscription can sit in failed-payment status before it needs a manual touch (update card, human outreach, or cancel).
+  max_retry_attempts:
+    default: 4
+    description: Number of automatic retry attempts before it needs a manual touch instead of another silent retry.
+compatible_agents: [generic, claude, codex]
+notes: This flags when automatic dunning has run its course — pair with an actual outreach step (email, SMS, or account pause) since the job itself only identifies who needs it.

package/jobs/ecommerce/marketplace-listing-sync-drift-check.yaml

@@ -0,0 +1,48 @@
+id: marketplace-listing-sync-drift-check
+version: 1
+name: Marketplace Listing Sync Drift Check
+description: >
+  Compares price and stock on your source-of-truth catalog against what's
+  actually live on a marketplace (Amazon, eBay, Etsy) and flags any SKU
+  that's drifted out of sync. Use this if a marketplace listing has ever
+  shown a stale price or "in stock" on an item you'd already sold out of
+  on your own store, because the sync job silently failed.
+category: ecommerce
+tags: [ecommerce, marketplace, sync, inventory, pricing]
+schedule: "0 */4 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' '
+    FNR==NR {
+      if (FNR==1) {next}
+      truth_price[$1]=$2; truth_stock[$1]=$3; next
+    }
+    {
+      if (FNR==1) {next}
+      sku=$1; mkt_price=$2; mkt_stock=$3; marketplace=$4;
+      if (sku in truth_price) {
+        price_diff = truth_price[sku] - mkt_price; if (price_diff < 0) price_diff = -price_diff;
+        if (price_diff > {{price_tolerance_usd}}) {
+          printf "PRICE DRIFT: %s on %s — source: $%.2f, listed: $%.2f\n", sku, marketplace, truth_price[sku], mkt_price;
+        }
+        if ((truth_stock[sku]+0 <= 0) != (mkt_stock+0 <= 0)) {
+          printf "STOCK DRIFT: %s on %s — source stock: %s, listed stock: %s\n", sku, marketplace, truth_stock[sku], mkt_stock;
+        }
+      } else {
+        printf "UNMATCHED SKU: %s on %s not found in source-of-truth catalog\n", sku, marketplace;
+      }
+    }
+  ' "{{source_of_truth_csv_path}}" "{{marketplace_export_csv_path}}"
+variables:
+  source_of_truth_csv_path:
+    default: "./catalog-source-of-truth.csv"
+    description: "Path to a CSV with columns: sku,price,stock — your own store's authoritative price/stock."
+  marketplace_export_csv_path:
+    default: "./marketplace-listings.csv"
+    description: "Path to a CSV export with columns: sku,listed_price,listed_stock,marketplace — one row per live listing per marketplace."
+  price_tolerance_usd:
+    default: 1.00
+    description: Acceptable price difference in dollars between source and marketplace before flagging drift.
+compatible_agents: [generic, claude, codex]
+notes: Requires both exports to use the same SKU values — normalize SKU formatting on export if a marketplace mangles it (e.g. adds a prefix).

package/jobs/ecommerce/product-feed-health-check.yaml

@@ -0,0 +1,35 @@
+id: product-feed-health-check
+version: 1
+name: Product Feed Health Check
+description: >
+  Scans your product catalog export for listings that are live but broken
+  in some way — missing title, missing description, missing image, a
+  zero/blank price, or marked out-of-stock while still visible to
+  shoppers. Use this if a product has ever sat on your storefront for
+  weeks with a broken image or a $0 price because nobody was checking
+  feed quality after the initial upload.
+category: ecommerce
+tags: [ecommerce, product-feed, seo, catalog, data-quality]
+schedule: "0 5 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' '
+    NR==1 {next}
+    {
+      sku=$1; title=$2; description=$3; image_url=$4; price=$5; in_stock=$6; visible=$7;
+      issues="";
+      if (title == "") issues = issues "missing title; ";
+      if (description == "") issues = issues "missing description; ";
+      if (image_url == "") issues = issues "missing image; ";
+      if (price+0 <= 0) issues = issues "zero/blank price; ";
+      if (in_stock == "false" && visible == "true") issues = issues "out-of-stock but still visible; ";
+      if (issues != "") printf "ISSUE: %s — %s\n", sku, issues;
+    }
+  ' "{{product_feed_csv_path}}"
+variables:
+  product_feed_csv_path:
+    default: "./product-feed.csv"
+    description: "Path to a CSV export with columns: sku,title,description,image_url,price,in_stock(true/false),visible(true/false)."
+compatible_agents: [generic, claude, codex]
+notes: Export this from whatever generates your storefront/Google Shopping feed on a schedule — the checks are only as fresh as the export. Distinct from `low-stock-reorder-alert`, which tracks stock levels, not listing data quality.

package/jobs/ecommerce/purchase-order-overdue-check.yaml

@@ -0,0 +1,32 @@
+id: purchase-order-overdue-check
+version: 1
+name: Purchase Order Overdue Check
+description: >
+  Checks open purchase orders to suppliers against their expected
+  delivery date and flags anything that hasn't arrived on time. Use this
+  if a supplier has ever gone quiet on a PO and you only found out stock
+  wasn't coming when you were already out of the item.
+category: ecommerce
+tags: [ecommerce, purchase-orders, suppliers, inventory]
+schedule: "0 7 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v today="$today" '
+    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 expected_epoch; close(cmd);
+      if (today > expected_epoch) {
+        overdue_days = (today - expected_epoch) / 86400;
+        printf "OVERDUE PO: %s from %s — expected %s (%d days late)\n", $1, $2, $3, overdue_days;
+      }
+    }
+  ' "{{purchase_orders_csv_path}}"
+variables:
+  purchase_orders_csv_path:
+    default: "./purchase-orders.csv"
+    description: "Path to a CSV with columns: po_id,supplier_name,expected_delivery_date (YYYY-MM-DD),status (pending/received)."
+compatible_agents: [generic, claude, codex]
+notes: Mark a PO "received" as soon as stock lands so this only ever flags genuinely overdue orders. Distinct from `low-stock-reorder-alert` (decides when to place an order) and `shipping-delay-check` (tracks outbound orders to customers) — this tracks inbound supplier orders after they've been placed.

package/jobs/ecommerce/storefront-ssl-domain-expiry-check.yaml

@@ -0,0 +1,46 @@
+id: storefront-ssl-domain-expiry-check
+version: 1
+name: Storefront SSL & Domain Expiry Check
+description: >
+  Checks your storefront's SSL certificate and domain registration expiry
+  dates and flags anything expiring soon. Use this if your store has ever
+  gone down — or thrown a scary browser security warning at checkout —
+  because an SSL cert or domain renewal quietly lapsed.
+category: ecommerce
+tags: [ecommerce, ssl, domain, uptime, infrastructure]
+schedule: "0 6 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  domain="{{storefront_domain}}";
+  warn_days="{{warn_days}}";
+  cert_end=$(echo | openssl s_client -servername "$domain" -connect "$domain":443 2>/dev/null | openssl x509 -noout -enddate 2>/dev/null | cut -d= -f2);
+  if [ -n "$cert_end" ]; then
+    cert_epoch=$(date -d "$cert_end" +%s 2>/dev/null || date -j -f "%b %d %T %Y %Z" "$cert_end" +%s 2>/dev/null);
+    now_epoch=$(date +%s);
+    cert_days_left=$(( (cert_epoch - now_epoch) / 86400 ));
+    if [ "$cert_days_left" -le "$warn_days" ]; then
+      echo "SSL WARNING: cert for $domain expires in $cert_days_left days ($cert_end)";
+    fi;
+  else
+    echo "ERROR: could not read SSL cert for $domain";
+  fi;
+  domain_end=$(whois "$domain" 2>/dev/null | grep -iE "registry expiry|expiration date" | head -n1 | sed -E 's/.*: *//');
+  if [ -n "$domain_end" ]; then
+    dom_epoch=$(date -d "$domain_end" +%s 2>/dev/null);
+    if [ -n "$dom_epoch" ]; then
+      dom_days_left=$(( (dom_epoch - now_epoch) / 86400 ));
+      if [ "$dom_days_left" -le "$warn_days" ]; then
+        echo "DOMAIN WARNING: $domain registration expires in $dom_days_left days ($domain_end)";
+      fi;
+    fi;
+  fi
+variables:
+  storefront_domain:
+    default: "example.com"
+    description: The domain your storefront is served from (no protocol/path).
+  warn_days:
+    default: 21
+    description: Days before SSL cert or domain expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Requires `openssl` and `whois` on the runner; whois output format varies by registrar/TLD, so treat a missing DOMAIN WARNING line as inconclusive rather than "all clear" and spot-check manually a few times after setup.

package/jobs/ecommerce/vip-tier-reclassification-check.yaml

@@ -0,0 +1,55 @@
+id: vip-tier-reclassification-check
+version: 1
+name: VIP Tier Reclassification Check
+description: >
+  Checks each customer's year-to-date spend against your VIP tier
+  thresholds and flags anyone due to move up or down a tier, drafting a
+  short outreach note for new upgrades. Use this if a top customer has
+  ever crossed your VIP spend threshold months ago and never got the
+  perks (or the acknowledgment) because nobody was tracking tier
+  crossings.
+category: ecommerce
+tags: [ecommerce, vip, customers, ltv, segmentation]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: hybrid
+command: >
+  awk -F',' -v gold="{{gold_threshold_usd}}" -v platinum="{{platinum_threshold_usd}}" '
+    NR==1 {next}
+    {
+      customer=$1; spend=$2; current_tier=$3;
+      new_tier = "standard";
+      if (spend+0 >= platinum) new_tier = "platinum";
+      else if (spend+0 >= gold) new_tier = "gold";
+      if (new_tier != current_tier) {
+        printf "TIER CHANGE: %s — %s -> %s (YTD spend $%.2f)\n", customer, current_tier, new_tier, spend;
+      }
+    }
+  ' "{{customers_csv_path}}"
+prompt: |
+  The script above compared each customer's YTD spend to the VIP tier
+  thresholds and listed everyone whose tier should change.
+  1. For each upgrade (moving to a higher tier), draft a short, warm
+     note acknowledging the milestone and naming the specific new perk
+     they've unlocked.
+  2. For each downgrade, just list it plainly — no outreach needed, this
+     is usually just for internal tracking/perk removal timing.
+  3. Group the final output into "Upgrades (draft ready)" and
+     "Downgrades (no action needed)".
+script_note: >
+  `command` gives you the raw list of who crossed a threshold in either
+  direction, at zero token cost. `prompt` adds the human touch: a
+  genuine, specific congratulations note for upgrades instead of a
+  generic template, which is the part worth spending tokens on.
+variables:
+  customers_csv_path:
+    default: "./customer-ytd-spend.csv"
+    description: "Path to a CSV with columns: customer_name,ytd_spend_usd,current_tier (standard/gold/platinum)."
+  gold_threshold_usd:
+    default: 500
+    description: YTD spend at or above which a customer qualifies for gold tier.
+  platinum_threshold_usd:
+    default: 2000
+    description: YTD spend at or above which a customer qualifies for platinum tier.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Distinct from `loyalty-points-expiry-reminder` in retail, which tracks points balances expiring — this tracks total spend against tier thresholds, independent of any points program.

package/jobs/ecommerce/wishlist-abandonment-check.yaml

@@ -0,0 +1,37 @@
+id: wishlist-abandonment-check
+version: 1
+name: Wishlist Abandonment Check
+description: >
+  Checks customer wishlists for items that have sat untouched for a while
+  and drafts a nudge email when there's a real reason to reach out — a
+  price drop or the item is back in stock — instead of a generic
+  "you still want this?" reminder. Use this if you've ever had a wishlist
+  feature that quietly collects intent and never converts any of it back
+  into a sale.
+category: ecommerce
+tags: [ecommerce, wishlist, recovery, conversion, sales]
+schedule: "0 11 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check {{store_platform}} for wishlist items added at least
+  {{min_days_on_wishlist}} days ago that are still in the customer's
+  wishlist (not purchased).
+  1. For each, check whether the item's price has dropped or it went
+     from out-of-stock to in-stock since it was wishlisted.
+  2. Only draft an outreach email for items with one of those real
+     triggers — skip items where nothing has changed, since a nudge with
+     no news performs worse than no email at all.
+  3. Draft a short, specific email per triggered item: name the item, the
+     specific change (price/stock), and a clear link back to it.
+  4. Report how many wishlist items were checked, how many had a real
+     trigger, and how many drafts were produced.
+variables:
+  store_platform:
+    default: "your storefront platform"
+    description: Name of the e-commerce platform with wishlist data (e.g. "Shopify", "WooCommerce").
+  min_days_on_wishlist:
+    default: 14
+    description: Minimum days an item must have sat on a wishlist before it's eligible for a re-engagement check.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — review before sending, and confirm your platform's marketing-consent rules cover wishlist-triggered email. Distinct from `abandoned-cart-recovery-check`, which targets items already added to an active cart; this targets earlier-funnel intent that never reached checkout, and only fires on a real trigger rather than time elapsed alone.

package/jobs/education/chronic-absenteeism-tracker.yaml

@@ -0,0 +1,34 @@
+id: chronic-absenteeism-tracker
+version: 1
+name: Chronic Absenteeism Tracker
+description: >
+  Calculates each student's missed-day percentage for the term and flags
+  anyone crossing the chronic-absenteeism threshold. Use this if a student
+  has ever quietly racked up enough missed days to count as chronically
+  absent before anyone outside the attendance office noticed.
+category: education
+tags: [education, attendance, chronic-absenteeism, students]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v threshold="{{chronic_threshold_pct}}" '
+    NR==1 {next}
+    {
+      enrolled = $2; absent = $3;
+      if (enrolled <= 0) next;
+      pct = (absent / enrolled) * 100;
+      if (pct >= threshold) {
+        printf "CHRONIC: %s — %d/%d days missed (%.1f%%)\n", $1, absent, enrolled, pct;
+      }
+    }
+  ' "{{attendance_csv_path}}"
+variables:
+  attendance_csv_path:
+    default: "./term-attendance.csv"
+    description: "Path to a CSV with columns: student_name,enrolled_days,absent_days."
+  chronic_threshold_pct:
+    default: 10
+    description: Percentage of enrolled days missed that counts as chronically absent (10% is the common federal benchmark).
+compatible_agents: [generic, claude, codex]
+notes: This looks at the whole term to date, unlike attendance-anomaly-check which flags a short-term drop — the two catch different problems.

package/jobs/education/department-budget-variance-check.yaml

@@ -0,0 +1,37 @@
+id: department-budget-variance-check
+version: 1
+name: Department Budget Variance Check
+description: >
+  Compares each department's or program's actual spending against its
+  budget and flags meaningful overages or underspend. Use this if a
+  department has ever blown through its annual budget months early
+  because nobody was checking actual-vs-budget until year-end
+  reconciliation.
+category: education
+tags: [education, budget, finance, departments]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review department/program budget vs. actual spending from
+  {{finance_system_hint}} for the current fiscal year to date.
+  1. For each department or program, compute spend as a percentage of its
+     annual budget and compare that to the expected percentage of the
+     fiscal year elapsed.
+  2. Flag departments running more than {{variance_threshold_pct}}
+     percentage points ahead of pace (overspend risk) or behind pace
+     (possible underspend, use-it-or-lose-it risk, or a stalled
+     initiative).
+  3. Note any single large transactions that materially explain a
+     variance, if visible in the data.
+  4. Summarize so budget owners can adjust spending or reforecast before
+     the next reporting cycle.
+variables:
+  finance_system_hint:
+    default: "your district finance/ERP system"
+    description: Where budget and actuals data lives.
+  variance_threshold_pct:
+    default: 15
+    description: Percentage-point gap between spend pace and time-elapsed pace that counts as worth flagging.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: This tracks department/program-level spending, not headcount or payroll cost, which HR budget jobs already cover separately.

package/jobs/education/enrollment-withdrawal-trend-tracker.yaml

@@ -0,0 +1,39 @@
+id: enrollment-withdrawal-trend-tracker
+version: 1
+name: Enrollment/Withdrawal Trend Tracker
+description: >
+  Reviews new enrollments and withdrawals over time and flags a school or
+  grade level that's losing students faster than usual. Use this if
+  enrollment decline has ever gone unnoticed for a semester because
+  individual withdrawals looked routine one at a time.
+category: education
+tags: [education, enrollment, students, trends]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review enrollment and withdrawal records from {{sis_hint}} for the last
+  {{lookback_months}} months.
+  1. Calculate net enrollment change by school and by grade level over the
+     window.
+  2. Flag any school or grade with a withdrawal rate above
+     {{withdrawal_rate_threshold_pct}}%, or a net enrollment decline that's
+     unusual compared to the same period in prior years if that data is
+     available.
+  3. Where withdrawal reasons are recorded, summarize the most common ones
+     (moved out of district, transferred to another school, homeschooling,
+     etc.) to help spot a pattern worth addressing versus normal mobility.
+  4. Summarize findings for administration, since sustained enrollment
+     decline affects staffing and funding decisions.
+variables:
+  sis_hint:
+    default: "your student information system"
+    description: Where enrollment and withdrawal records live.
+  lookback_months:
+    default: 6
+    description: How many months of enrollment history to review.
+  withdrawal_rate_threshold_pct:
+    default: 8
+    description: Withdrawal rate percentage that counts as worth flagging.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — SIS platforms and how they record withdrawal reasons vary too widely to assume a common export format.

package/jobs/education/facility-work-order-backlog-check.yaml

@@ -0,0 +1,34 @@
+id: facility-work-order-backlog-check
+version: 1
+name: Facility Work Order Backlog Check
+description: >
+  Reviews open facility maintenance work orders and flags the ones that
+  have been sitting too long, especially safety-related requests. Use
+  this if a maintenance ticket has ever gone stale for weeks until it
+  turned into a bigger, more expensive problem.
+category: education
+tags: [education, facilities, maintenance, work-orders]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review open facility work orders from {{facilities_system_hint}}.
+  1. List every work order still open after {{stale_days}} days, with its
+     school/building, description, and age.
+  2. Call out anything that reads as a safety or code issue (electrical,
+     HVAC failure in occupied spaces, structural, fire/life-safety,
+     accessibility) separately from routine cosmetic or convenience
+     requests — those need different urgency.
+  3. Group the remaining backlog by building so facilities staff can see
+     where the workload is concentrated.
+  4. Summarize counts and the oldest few tickets so leadership can decide
+     where to add capacity or reprioritize.
+variables:
+  facilities_system_hint:
+    default: "your facilities/maintenance ticketing system"
+    description: Where work orders are tracked.
+  stale_days:
+    default: 14
+    description: Days a work order can stay open before it's counted as backlog.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — facilities/maintenance ticketing systems vary too widely for a single export format.

package/jobs/education/free-reduced-lunch-eligibility-renewal-check.yaml

@@ -0,0 +1,36 @@
+id: free-reduced-lunch-eligibility-renewal-check
+version: 1
+name: Free/Reduced Lunch Eligibility Renewal Check
+description: >
+  Checks free/reduced meal eligibility records for approvals that are
+  about to expire and flags families who need to renew. Use this if a
+  student has ever lost meal benefits mid-year because their eligibility
+  lapsed and nobody sent a renewal reminder in time.
+category: education
+tags: [education, meals, eligibility, compliance]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v warnDays="{{warn_days}}" '
+    NR==1 {next}
+    $3 == "no" {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");
+      days_left = (exp_epoch - now_epoch) / 86400;
+      if (days_left <= warnDays) {
+        printf "%s: %s eligibility expires %s (%d days)\n", (days_left < 0 ? "EXPIRED" : "RENEW SOON"), $1, $2, days_left;
+      }
+    }
+  ' "{{eligibility_csv_path}}"
+variables:
+  eligibility_csv_path:
+    default: "./meal-eligibility.csv"
+    description: "Path to a CSV with columns: student_name,expiration_date (YYYY-MM-DD),active (yes/no)."
+  warn_days:
+    default: 21
+    description: Days before expiration to start warning, giving families time to resubmit paperwork.
+compatible_agents: [generic, claude, codex]
+notes: Route renewal notices through whatever family-communication channel the district already uses for meal program paperwork.

package/jobs/education/iep-504-review-deadline-tracker.yaml

@@ -0,0 +1,35 @@
+id: iep-504-review-deadline-tracker
+version: 1
+name: IEP/504 Review Deadline Tracker
+description: >
+  Checks upcoming IEP and 504 plan review deadlines and flags any that are
+  close or already past due. Use this if a required review has ever slipped
+  past its compliance deadline because it wasn't on anyone's calendar until
+  a parent or auditor asked about it.
+category: education
+tags: [education, iep, 504-plan, compliance, deadlines]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v warnDays="{{warn_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 due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      days_left = (due_epoch - now_epoch) / 86400;
+      if (days_left <= warnDays) {
+        printf "%s: %s review due %s (%d days)\n", (days_left < 0 ? "OVERDUE" : "DUE SOON"), $1, $2, days_left;
+      }
+    }
+  ' "{{plans_csv_path}}"
+variables:
+  plans_csv_path:
+    default: "./iep-504-plans.csv"
+    description: "Path to a CSV with columns: student_name,next_review_due (YYYY-MM-DD)."
+  warn_days:
+    default: 14
+    description: Days before the review deadline to start warning.
+compatible_agents: [generic, claude, codex]
+notes: These deadlines are legally mandated in most jurisdictions — treat overdue results as urgent, not routine.

package/jobs/education/parent-teacher-conference-noshow-tracker.yaml

@@ -0,0 +1,29 @@
+id: parent-teacher-conference-noshow-tracker
+version: 1
+name: Parent-Teacher Conference No-Show Tracker
+description: >
+  Checks scheduled parent-teacher conferences against attendance and flags
+  no-shows for follow-up. Use this if a family has ever missed a
+  conference slot and nobody rescheduled it, especially for a student
+  where that conversation actually mattered.
+category: education
+tags: [education, parent-engagement, conferences]
+schedule: "0 17 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  noshows=$(awk -F',' 'NR>1 && $4=="no-show" {print $1" (with "$2", "$3")"}' "{{conferences_csv_path}}");
+  count=$(echo "$noshows" | grep -c . || true);
+  if [ "$count" -gt 0 ]; then
+    echo "NO-SHOWS TO FOLLOW UP:";
+    echo "$noshows";
+    exit 1;
+  else
+    echo "OK: no unaddressed conference no-shows";
+  fi
+variables:
+  conferences_csv_path:
+    default: "./conference-schedule.csv"
+    description: "Path to a CSV with columns: student_name,parent_name,teacher_name,status (attended, no-show, rescheduled)."
+compatible_agents: [generic, claude, codex]
+notes: Mark a no-show as rescheduled once a follow-up slot is booked, or it will keep showing up here.

package/jobs/education/school-bus-route-ontime-check.yaml

@@ -0,0 +1,40 @@
+id: school-bus-route-ontime-check
+version: 1
+name: School Bus Route On-Time Check
+description: >
+  Reviews bus route arrival data and flags routes that are consistently
+  running late. Use this if a route has ever drifted later and later over
+  weeks with only individual parent complaints, never a pattern anyone
+  actually looked at.
+category: education
+tags: [education, transportation, bus-routes]
+schedule: "0 16 * * 1-5"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review bus arrival/departure data from {{transportation_system_hint}} for
+  the last {{lookback_days}} days.
+  1. For each route, compare actual arrival times against the scheduled
+     times at each stop.
+  2. Flag any route that was late by more than {{late_threshold_min}}
+     minutes on {{repeat_occurrences}} or more days in the window —
+     one bad day is noise, a pattern is a scheduling or staffing problem.
+  3. For flagged routes, note whether the lateness looks tied to a specific
+     stop, time of day, or driver, since that changes what the fix is.
+  4. Summarize findings so transportation staff can adjust schedules or
+     staffing before it becomes a parent-complaint pattern.
+variables:
+  transportation_system_hint:
+    default: "your bus/transportation tracking system"
+    description: Where route timing data lives (GPS tracker, dispatch software, etc.).
+  lookback_days:
+    default: 10
+    description: How many school days of route data to review.
+  late_threshold_min:
+    default: 10
+    description: Minutes past scheduled time that counts as late.
+  repeat_occurrences:
+    default: 3
+    description: Number of late days within the window that counts as a pattern worth flagging.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — bus tracking/GPS systems vary too widely to assume a common export format.

package/jobs/education/standardized-test-registration-deadline-check.yaml

@@ -0,0 +1,35 @@
+id: standardized-test-registration-deadline-check
+version: 1
+name: Standardized Test Registration Deadline Check
+description: >
+  Warns before the registration cutoff for a standardized test (state
+  assessment, AP, SAT, etc.). Use this if a student has ever missed the
+  window to register for a test because the deadline landed during a busy
+  stretch of the term and nobody flagged it in advance.
+category: education
+tags: [education, testing, deadlines]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  due_ts=$(date -d "{{registration_deadline}}" +%s 2>/dev/null || date -jf "%Y-%m-%d" "{{registration_deadline}}" +%s);
+  days_left=$(( (due_ts - today) / 86400 ));
+  if [ "$days_left" -le "{{warn_days}}" ] && [ "$days_left" -ge 0 ]; then
+    echo "WARNING: {{test_name}} registration closes in $days_left days ({{registration_deadline}})";
+    exit 1;
+  else
+    echo "OK: {{test_name}} registration closes in $days_left days";
+  fi
+variables:
+  test_name:
+    default: "state standardized assessment"
+    description: Name of the test whose registration window this tracks.
+  registration_deadline:
+    default: "2026-12-15"
+    description: Registration cutoff date (YYYY-MM-DD).
+  warn_days:
+    default: 10
+    description: Days before the deadline to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Run one instance per test/deadline you need to track — AP, SAT, and state assessments usually have different windows.

package/jobs/education/substitute-teacher-fill-rate-tracker.yaml

@@ -0,0 +1,35 @@
+id: substitute-teacher-fill-rate-tracker
+version: 1
+name: Substitute Teacher Fill Rate Tracker
+description: >
+  Compares substitute requests against how many were actually filled and
+  flags days or schools with a low fill rate. Use this if classes have
+  ever gone uncovered because nobody was tracking whether sub requests
+  were actually getting filled.
+category: education
+tags: [education, staffing, substitute-teachers]
+schedule: "0 6 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v minRate="{{min_fill_rate_pct}}" '
+    NR==1 {next}
+    { requested[$1] += 1; if ($3 == "filled") filled[$1] += 1; }
+    END {
+      for (school in requested) {
+        rate = (filled[school] / requested[school]) * 100;
+        if (rate < minRate) {
+          printf "LOW FILL RATE: %s — %.1f%% (%d/%d requests filled)\n", school, rate, filled[school], requested[school];
+        }
+      }
+    }
+  ' "{{sub_requests_csv_path}}"
+variables:
+  sub_requests_csv_path:
+    default: "./sub-requests.csv"
+    description: "Path to a CSV with columns: school,request_date,status (filled or unfilled)."
+  min_fill_rate_pct:
+    default: 85
+    description: Fill rate percentage below which a school is flagged.
+compatible_agents: [generic, claude, codex]
+notes: Run this early in the morning before the school day starts so unfilled slots can still be covered.