@wonsukchoi/crondex 0.11.0 → 0.13.0

package/jobs/agriculture/crop-price-market-watch.yaml

@@ -0,0 +1,32 @@
+id: crop-price-market-watch
+version: 1
+name: Crop Price Market Watch
+description: >
+  Checks a commodity crop's current market price against a target and
+  alerts when it crosses your threshold. Use this if you've ever missed a
+  good selling window because nobody was watching the market that week.
+category: agriculture
+tags: [agriculture, commodity, price, market]
+schedule: "0 14 * * 1-5"
+timezone: "America/Chicago"
+runner: agent-prompt
+prompt: |
+  Check the current market price for {{commodity}} (via a commodity market
+  data source such as a futures quote or ag market report).
+  1. Report today's price and how it compares to {{target_price}}.
+  2. If price is at or above target, flag it as a potential selling window.
+  3. If price has moved more than {{move_threshold_pct}}% in the last week,
+     note that regardless of the target.
+  4. Otherwise report the price with no action needed.
+variables:
+  commodity:
+    default: "corn"
+    description: Commodity/crop to track (e.g. "corn", "soybeans", "wheat").
+  target_price:
+    default: "5.00 per bushel"
+    description: Price target that triggers a "consider selling" flag.
+  move_threshold_pct:
+    default: 5
+    description: Weekly price move percentage worth flagging even if the target isn't hit.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Not trading advice — a price-threshold alert only. Confirm quotes against your actual buyer/co-op before acting on them.

package/jobs/agriculture/livestock-feed-stock-check.yaml

@@ -0,0 +1,35 @@
+id: livestock-feed-stock-check
+version: 1
+name: Livestock Feed Stock Check
+description: >
+  Checks how many days of feed are left based on current stock and daily
+  consumption, and warns before you run out. Use this if feed has ever run
+  low over a weekend or holiday when the supplier wasn't reachable.
+category: agriculture
+tags: [agriculture, livestock, feed, inventory]
+schedule: "0 6 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  stock="{{feed_stock_lbs}}";
+  daily_use="{{daily_consumption_lbs}}";
+  warn_days="{{warn_days_before}}";
+  days_left=$(awk -v s="$stock" -v d="$daily_use" 'BEGIN{ if (d>0) printf "%.1f", s/d; else print "999" }');
+  if awk -v dl="$days_left" -v w="$warn_days" 'BEGIN{exit !(dl <= w)}'; then
+    echo "LOW FEED: $days_left days of feed left (stock ${stock}lb, using ${daily_use}lb/day)";
+    exit 1;
+  else
+    echo "OK: $days_left days of feed left";
+  fi
+variables:
+  feed_stock_lbs:
+    default: 0
+    description: Current feed stock on hand, in pounds (update this manually or from a scale reading).
+  daily_consumption_lbs:
+    default: 100
+    description: Average daily feed consumption in pounds.
+  warn_days_before:
+    default: 7
+    description: Days of remaining supply that triggers a warning — set with supplier lead time in mind.
+compatible_agents: [generic, claude, codex]
+notes: Assumes you update `feed_stock_lbs` after each delivery/count — this is a simple burn-rate calculation, not an automatic inventory sensor integration.

package/jobs/automotive/loaner-vehicle-return-reminder.yaml

@@ -0,0 +1,35 @@
+id: loaner-vehicle-return-reminder
+version: 1
+name: Loaner Vehicle Return Reminder
+description: >
+  Warns you before a loaner vehicle is due back, and flags anything
+  already overdue. Use this if a loaner has ever gone weeks without
+  coming back because nobody was tracking who had which car out.
+category: automotive
+tags: [automotive, loaner, fleet, reminder]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v days="{{warn_days_before}}" -v today="$today" '
+    NR==1 {next}
+    {
+      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);
+      diff_days = (due_epoch - today) / 86400;
+      if (diff_days <= days) {
+        if (diff_days < 0) printf "OVERDUE: %s with %s — was due %s (%d days late)\n", $1, $2, $3, -diff_days;
+        else printf "DUE SOON: %s with %s — due %s (%d days)\n", $1, $2, $3, diff_days;
+      }
+    }
+  ' "{{loaners_csv_path}}"
+variables:
+  loaners_csv_path:
+    default: "./loaner-vehicles.csv"
+    description: "Path to a CSV with columns: loaner_vehicle_id,customer_name,return_due_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 1
+    description: How many days before the return date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Distinct from `equipment-rental-return-reminder` in construction — this tracks vehicles the shop lends out, not equipment the shop rents in.

package/jobs/automotive/parts-backorder-check.yaml

@@ -0,0 +1,33 @@
+id: parts-backorder-check
+version: 1
+name: Parts Backorder Check
+description: >
+  Checks ordered parts against their expected arrival date and flags
+  anything overdue from the supplier. Use this if a repair has ever
+  stalled for a week because a part was quietly backordered and nobody
+  followed up with the supplier until a customer asked why their car
+  wasn't ready.
+category: automotive
+tags: [automotive, parts, backorder, supplier]
+schedule: "0 9 * * *"
+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: %s for RO %s — expected %s (%d days late)\n", $1, $2, $3, overdue_days;
+      }
+    }
+  ' "{{parts_orders_csv_path}}"
+variables:
+  parts_orders_csv_path:
+    default: "./parts-orders.csv"
+    description: "Path to a CSV with columns: part_name,ro_number,expected_arrival_date (YYYY-MM-DD),status (pending/received)."
+compatible_agents: [generic, claude, codex]
+notes: Follow up directly with the supplier once a part is flagged overdue — this job only surfaces the gap, it doesn't contact anyone.

package/jobs/automotive/repair-order-aging-check.yaml

@@ -0,0 +1,35 @@
+id: repair-order-aging-check
+version: 1
+name: Repair Order Aging Check
+description: >
+  Checks open repair orders and flags any vehicle that's been sitting in
+  the shop past your target turnaround with no status update. Use this if
+  a car has ever sat on a lift for days with no visible progress because
+  it fell out of the technician's mental queue.
+category: automotive
+tags: [automotive, repair-shop, workflow, aging]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v days="{{target_turnaround_days}}" -v today="$today" '
+    NR==1 {next}
+    $3 == "open" {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline checkin_epoch; close(cmd);
+      age_days = (today - checkin_epoch) / 86400;
+      if (age_days > days) {
+        printf "AGING: RO %s — checked in %s (%d days)\n", $1, $2, age_days;
+      }
+    }
+  ' "{{repair_orders_csv_path}}"
+variables:
+  repair_orders_csv_path:
+    default: "./repair-orders.csv"
+    description: "Path to a CSV with columns: ro_number,checkin_date (YYYY-MM-DD),status (open/closed)."
+  target_turnaround_days:
+    default: 3
+    description: Target days to complete a typical repair before it counts as aging.
+compatible_agents: [generic, claude, codex]
+notes: A vehicle waiting on a backordered part is a different problem than one just sitting unassigned — check `parts-backorder-check` alongside this to tell the two apart.

package/jobs/childcare/immunization-record-compliance-check.yaml

@@ -0,0 +1,33 @@
+id: immunization-record-compliance-check
+version: 1
+name: Immunization Record Compliance Check
+description: >
+  Checks enrolled children's immunization records against your state's
+  required schedule and flags anyone missing required documentation. Use
+  this if a compliance gap has ever gone unnoticed until a state licensing
+  inspection found it first.
+category: childcare
+tags: [childcare, immunization, compliance, licensing]
+schedule: "0 8 1 * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check enrolled children's immunization records in {{records_system}}
+  against the required schedule for {{jurisdiction}}.
+  1. List any child with missing or expired required immunization
+     documentation, or a filed exemption that needs renewal.
+  2. Flag anyone enrolled more than {{grace_period_days}} days ago with
+     still-incomplete records as past the grace period.
+  3. Draft a short reminder to the family for each incomplete record.
+variables:
+  records_system:
+    default: "your childcare management system"
+    description: Where enrollment and immunization records are tracked.
+  jurisdiction:
+    default: "your state/locality"
+    description: Which jurisdiction's required immunization schedule applies.
+  grace_period_days:
+    default: 30
+    description: Days a new enrollment can be missing records before it's past grace period.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — confirm your jurisdiction's actual required schedule and exemption rules, which vary and change; don't rely on this job to know them for you.

package/jobs/childcare/staff-child-ratio-compliance-check.yaml

@@ -0,0 +1,30 @@
+id: staff-child-ratio-compliance-check
+version: 1
+name: Staff-to-Child Ratio Compliance Check
+description: >
+  Checks each classroom/group's staff-to-child ratio for the day against
+  your licensing requirement and flags anything out of compliance. Use
+  this if a ratio has ever slipped out of compliance mid-shift because
+  someone called in sick and nobody recalculated the numbers.
+category: childcare
+tags: [childcare, ratio, compliance, staffing]
+schedule: "0 7,12 * * 1-5"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' '
+    NR==1 {next}
+    {
+      required_max = $4;
+      actual_ratio = $3 / $2;
+      if ($2 > required_max || actual_ratio > 1) {
+        printf "OUT OF RATIO: %s — %d staff for %d children (max %d children/staff)\n", $1, $2, $3, $4;
+      }
+    }
+  ' "{{classrooms_csv_path}}"
+variables:
+  classrooms_csv_path:
+    default: "./classroom-ratios.csv"
+    description: "Path to a CSV with columns: classroom_name,staff_count,child_count,max_children_per_staff (your licensing requirement for that age group)."
+compatible_agents: [generic, claude, codex]
+notes: Recompute this whenever staffing or headcount changes during the day (e.g. a callout, a late pickup) — it's only as current as the last update to the CSV.

package/jobs/childcare/tuition-payment-late-check.yaml

@@ -0,0 +1,35 @@
+id: tuition-payment-late-check
+version: 1
+name: Tuition Payment Late Check
+description: >
+  Flags families whose tuition payment is overdue past the grace period.
+  Use this if a late payment has ever gone unnoticed for weeks because
+  nobody was cross-checking the payment ledger against who'd actually
+  paid.
+category: childcare
+tags: [childcare, tuition, payment, billing]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F',' -v grace="{{grace_period_days}}" -v today="$today" '
+    NR==1 {next}
+    $3 == "unpaid" {
+      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);
+      days_late = (today - due_epoch) / 86400;
+      if (days_late > grace) {
+        printf "LATE: %s — due %s (%d days overdue)\n", $1, $2, days_late;
+      }
+    }
+  ' "{{tuition_csv_path}}"
+variables:
+  tuition_csv_path:
+    default: "./tuition-ledger.csv"
+    description: "Path to a CSV with columns: family_name,due_date (YYYY-MM-DD),status (paid/unpaid)."
+  grace_period_days:
+    default: 5
+    description: Days past the due date before a payment counts as late.
+compatible_agents: [generic, claude, codex]
+notes: Parallel structure to `rent-payment-late-check` in realestate — a plain grace-period check against a payment ledger.

package/jobs/construction/equipment-rental-return-reminder.yaml

@@ -0,0 +1,35 @@
+id: equipment-rental-return-reminder
+version: 1
+name: Equipment Rental Return Reminder
+description: >
+  Warns you before a rented piece of equipment is due back, so it doesn't
+  rack up late fees or an unplanned extension charge. Use this if a rental
+  has ever run days past due because nobody was tracking the return date
+  against the job schedule.
+category: construction
+tags: [construction, equipment, rental, deadline]
+schedule: "0 7 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (due_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "RETURN DUE: %s — due back %s (%d days)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{rentals_csv_path}}"
+variables:
+  rentals_csv_path:
+    default: "./equipment-rentals.csv"
+    description: "Path to a CSV with columns: equipment_name,return_due_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 2
+    description: How many days before the return date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: If a rental needs extending because the job's running long, that's a call to make with the rental company directly — this job only flags the deadline.

package/jobs/construction/subcontractor-insurance-expiry-check.yaml

@@ -0,0 +1,35 @@
+id: subcontractor-insurance-expiry-check
+version: 1
+name: Subcontractor Insurance (COI) Expiry Check
+description: >
+  Checks tracked subcontractor certificates of insurance and warns before
+  any expire. Use this if a sub has ever kept working on site after their
+  COI lapsed, leaving the general contractor exposed if something went
+  wrong.
+category: construction
+tags: [construction, insurance, compliance, subcontractor]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{warn_days_before}}" '
+    NR==1 {next}
+    {
+      cmd = "date -d \"" $2 "\" +%s 2>/dev/null || date -j -f %Y-%m-%d \"" $2 "\" +%s 2>/dev/null";
+      cmd | getline expiry_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (expiry_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "COI EXPIRING: %s — expires %s (%d days)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{subcontractors_csv_path}}"
+variables:
+  subcontractors_csv_path:
+    default: "./subcontractor-coi.csv"
+    description: "Path to a CSV with columns: subcontractor_name,coi_expiry_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 30
+    description: How many days before COI expiry to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Maintain the CSV from whatever COI-tracking process you already use (many insurers/brokers can export renewal dates); this is the "did anyone actually check" backstop.

package/jobs/creator/sponsorship-deliverable-tracker.yaml

@@ -0,0 +1,38 @@
+id: sponsorship-deliverable-tracker
+version: 1
+name: Sponsorship Deliverable Tracker
+description: >
+  Flags brand-deal deliverables (a video, post, story, or link placement)
+  coming due across whatever platforms you post on. Use this if a sponsor
+  has ever had to ask where their promised content was because the
+  deadline only lived in an email thread from weeks ago.
+category: creator
+tags: [creator, sponsorship, brand-deal, deliverable]
+schedule: "0 9 * * *"
+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 due_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      diff_days = (due_epoch - now_epoch) / 86400;
+      if (diff_days <= days) {
+        printf "DUE SOON: %s — %s due %s (%d days)\n", $1, $2, $3, diff_days;
+      }
+    }
+  ' "{{deliverables_csv_path}}"
+variables:
+  deliverables_csv_path:
+    default: "./sponsorship-deliverables.csv"
+    description: "Path to a CSV with columns: brand_name,deliverable_type,due_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 3
+    description: How many days before a deliverable is due to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Covers general brand-deal content (video, post, story, link) across any
+  platform. If you specifically need podcast ad-read tracking, see
+  `sponsor-deliverable-tracker` in the podcast category instead.

package/jobs/crypto/defi-liquidation-risk-watch.yaml

@@ -0,0 +1,36 @@
+id: defi-liquidation-risk-watch
+version: 1
+name: DeFi Liquidation Risk Watch
+description: >
+  Checks a lending position's current collateral ratio and warns before it
+  gets close to the liquidation threshold. Use this if a position has ever
+  gotten liquidated during a price dip because nobody was watching the
+  health factor in real time.
+category: crypto
+tags: [crypto, defi, lending, liquidation]
+schedule: "*/15 * * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check the current health factor / collateral ratio for the lending
+  position at {{position_address_or_id}} on {{protocol_name}} (via the
+  protocol's app, subgraph, or a position-tracking site).
+  1. Report the current health factor / collateral ratio.
+  2. Compare against the liquidation threshold — flag as urgent if within
+     {{danger_margin_pct}}% of triggering liquidation.
+  3. If urgent, suggest the immediate options: add collateral, repay part
+     of the loan, or reduce exposure — don't take any action, just lay out
+     the choices.
+  4. If healthy, report the current buffer in one line.
+variables:
+  protocol_name:
+    default: "Aave"
+    description: Name of the lending protocol (e.g. "Aave", "Compound", "MakerDAO").
+  position_address_or_id:
+    default: "your wallet address or position ID"
+    description: The wallet address or position identifier to check.
+  danger_margin_pct:
+    default: 15
+    description: How close to the liquidation threshold (in percent) counts as urgent.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Informational only — does not execute any transaction. Given how fast collateral ratios can move in volatile markets, treat the check interval as a floor, not a guarantee you'll always catch it in time.

package/jobs/crypto/token-unlock-vesting-watch.yaml

@@ -0,0 +1,34 @@
+id: token-unlock-vesting-watch
+version: 1
+name: Token Unlock/Vesting Watch
+description: >
+  Checks for upcoming token unlock or vesting cliff dates for a project
+  you're tracking and warns before a large unlock hits. Use this if a
+  token has ever dropped sharply right after an unlock you didn't see
+  coming.
+category: crypto
+tags: [crypto, tokenomics, vesting, unlock]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check {{token_name}}'s vesting/unlock schedule (via the project's
+  tokenomics docs, a vesting tracker site, or on-chain vesting contract
+  data) for unlocks in the next {{lookahead_days}} days.
+  1. List any upcoming unlock: date, amount, and percentage of circulating
+     supply it represents.
+  2. Flag any unlock over {{large_unlock_pct}}% of circulating supply as
+     worth watching closely for price impact.
+  3. If nothing is scheduled in the window, say so in one line.
+variables:
+  token_name:
+    default: "the token you're tracking"
+    description: Token/project name to check.
+  lookahead_days:
+    default: 14
+    description: How far ahead to check for scheduled unlocks.
+  large_unlock_pct:
+    default: 2
+    description: Percentage of circulating supply that counts as a "large" unlock worth flagging.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Not trading advice — an informational heads-up only. Vesting schedule accuracy depends entirely on the source; cross-check against the project's own docs before acting on it.

package/jobs/ecommerce/checkout-conversion-drop-watch.yaml

@@ -0,0 +1,39 @@
+id: checkout-conversion-drop-watch
+version: 1
+name: Checkout Conversion Drop Watch
+description: >
+  Compares today's checkout completion rate against your recent baseline
+  and flags a real drop. Use this if a checkout bug has ever silently cut
+  conversion for a day or two before anyone noticed sales looked soft.
+category: ecommerce
+tags: [ecommerce, checkout, conversion, analytics]
+schedule: "0 */6 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check checkout funnel data in {{analytics_source}} for the last
+  {{lookback_hours}} hours.
+  1. Calculate checkout-started-to-completed conversion rate for the
+     window.
+  2. Compare against the trailing {{baseline_days}}-day average for the
+     same time-of-day/day-of-week (checkout rates often vary by both).
+  3. Flag a drop of {{drop_threshold_pct}}% or more below baseline.
+  4. If flagged, note which step of the funnel shows the biggest relative
+     drop-off compared to baseline — that's usually where to look first
+     (payment step failing vs. shipping step confusing people are very
+     different problems).
+variables:
+  analytics_source:
+    default: "your storefront analytics (e.g. Shopify Analytics, GA4, a custom funnel dashboard)"
+    description: Where checkout funnel data is tracked.
+  lookback_hours:
+    default: 6
+    description: Window of recent checkout activity to evaluate.
+  baseline_days:
+    default: 14
+    description: Days of history used to establish the normal conversion rate.
+  drop_threshold_pct:
+    default: 15
+    description: Percentage drop below baseline that counts as worth flagging.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Time-of-day/day-of-week-aware baseline matters — comparing a Tuesday afternoon rate to a Black-Friday-morning baseline will false-positive constantly.

package/jobs/ecommerce/negative-review-alert.yaml

@@ -0,0 +1,35 @@
+id: negative-review-alert
+version: 1
+name: Negative Review Alert
+description: >
+  Checks for new low-star product reviews and flags them same-day instead
+  of letting them sit in a dashboard nobody checks. Use this if a bad
+  review has ever sat live for a week before anyone on the team noticed
+  and responded.
+category: ecommerce
+tags: [ecommerce, reviews, reputation, customer-service]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check {{store_platform}} for reviews posted in the last
+  {{lookback_hours}} hours rated at or below {{alert_threshold_stars}}
+  stars.
+  1. List each: product, rating, and a one-line summary of the complaint.
+  2. Draft a short, non-defensive response for each, acknowledging the
+     issue and offering a concrete next step (replacement, refund,
+     follow-up contact) — not a generic "sorry to hear that."
+  3. Flag any review mentioning a safety issue or a pattern matching a
+     recent product-quality complaint separately as higher priority.
+variables:
+  store_platform:
+    default: "your storefront/reviews platform"
+    description: Platform to check (e.g. "Shopify product reviews", "Amazon Seller Central", "Trustpilot").
+  lookback_hours:
+    default: 24
+    description: How far back to check for new reviews.
+  alert_threshold_stars:
+    default: 2
+    description: Star rating at or below which a review triggers this alert (out of 5).
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — review responses before posting publicly, since a bad public reply can do more damage than the original review.

package/jobs/education/at-risk-student-grade-watch.yaml

@@ -0,0 +1,35 @@
+id: at-risk-student-grade-watch
+version: 1
+name: At-Risk Student Grade Watch
+description: >
+  Flags students whose current grade has dropped below a passing threshold
+  partway through the term, instead of everyone finding out at report-card
+  time. Use this if a student has ever gone from passing to failing
+  without anyone reaching out until it was too late to recover.
+category: education
+tags: [education, grades, at-risk, students]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check current grades in {{gradebook_system}} for {{course_or_class}}.
+  1. List any student currently below {{passing_threshold}}.
+  2. For each, note which specific assignments are dragging the grade down
+     (missing work vs. low scores on completed work — the intervention is
+     different for each).
+  3. Flag anyone who was passing at the last check but has now dropped
+     below threshold, as a new/urgent case worth an earlier outreach.
+  4. Draft a short note for a teacher or counselor to send home, if that's
+     the practice at this school.
+variables:
+  gradebook_system:
+    default: "your gradebook/LMS (e.g. PowerSchool, Google Classroom, Canvas)"
+    description: Where grades are recorded.
+  course_or_class:
+    default: "the class/section to check"
+    description: Which course or section this job covers.
+  passing_threshold:
+    default: 65
+    description: Grade percentage below which a student counts as at-risk.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — outreach to students/families should go through whatever channel and approval process your school already uses.

package/jobs/education/field-trip-permission-slip-check.yaml

@@ -0,0 +1,36 @@
+id: field-trip-permission-slip-check
+version: 1
+name: Field Trip Permission Slip Check
+description: >
+  Checks which students still haven't returned a signed permission slip as
+  a field trip approaches. Use this if a student has ever been left behind
+  on a school trip because their slip got lost in a backpack and nobody
+  followed up in time.
+category: education
+tags: [education, field-trip, permission-slip, students]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  trip_date_epoch=$(date -d "{{trip_date}}" +%s 2>/dev/null || date -jf "%Y-%m-%d" "{{trip_date}}" +%s);
+  now_epoch=$(date +%s);
+  days_left=$(( (trip_date_epoch - now_epoch) / 86400 ));
+  if [ "$days_left" -lt 0 ]; then echo "trip date has passed"; exit 0; fi;
+  missing=$(awk -F',' '$2 != "returned" {print $1}' "{{slips_csv_path}}");
+  count=$(echo "$missing" | grep -c . || true);
+  if [ "$count" -gt 0 ]; then
+    echo "MISSING SLIPS ($days_left days until trip):";
+    echo "$missing";
+    exit 1;
+  else
+    echo "OK: all permission slips returned, $days_left days until trip";
+  fi
+variables:
+  trip_date:
+    default: "YYYY-MM-DD"
+    description: Date of the field trip.
+  slips_csv_path:
+    default: "./field-trip-slips.csv"
+    description: "Path to a CSV with columns: student_name,status (returned or pending)."
+compatible_agents: [generic, claude, codex]
+notes: Keep the CSV updated as slips come in — this just cross-checks the current list against the trip date, it doesn't collect slips itself.

package/jobs/events/attendee-checkin-rate-watch.yaml

@@ -0,0 +1,37 @@
+id: attendee-checkin-rate-watch
+version: 1
+name: Attendee Check-In Rate Watch
+description: >
+  Checks the day-of check-in rate against registered headcount and flags
+  it if turnout is running well below expectations while there's still
+  time to adjust (catering, seating, staffing). Use this if you've ever
+  found out an event was under-attended only after it ended, instead of
+  two hours into it.
+category: events
+tags: [events, checkin, attendance, day-of]
+schedule: "*/30 * * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  checked_in=$(wc -l < "{{checkins_csv_path}}");
+  checked_in=$((checked_in - 1));
+  registered="{{registered_count}}";
+  pct=$(awk -v c="$checked_in" -v r="$registered" 'BEGIN{ if (r>0) printf "%.0f", (c/r)*100; else print "0" }');
+  target="{{expected_checkin_pct}}";
+  if [ "$pct" -lt "$target" ]; then
+    echo "LOW TURNOUT: $checked_in of $registered checked in ($pct%, expected ~$target%)";
+  else
+    echo "OK: $checked_in of $registered checked in ($pct%)";
+  fi
+variables:
+  checkins_csv_path:
+    default: "./event-checkins.csv"
+    description: Path to a CSV of check-ins so far (one header row plus one row per checked-in attendee).
+  registered_count:
+    default: 100
+    description: Total number of registered attendees expected.
+  expected_checkin_pct:
+    default: 70
+    description: Typical check-in rate (percent of registrants) for this kind of event, used as the comparison baseline.
+compatible_agents: [generic, claude, codex]
+notes: Only useful once check-ins start (e.g. run it during the event's arrival window) — it's a live day-of signal, not a pre-event forecast.