@wonsukchoi/crondex 0.6.0 → 0.8.0

package/jobs/logistics/freight-rate-spike-watch.yaml

@@ -0,0 +1,38 @@
+id: freight-rate-spike-watch
+version: 1
+name: Freight Rate Spike Watch
+description: >
+  Checks a freight lane's current quoted rate against your baseline and
+  flags a spike. Use this if a shipping rate has ever quietly doubled and
+  only got noticed when the invoice came in.
+category: logistics
+tags: [logistics, freight, rates]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check the current freight rate for the lane {{lane_description}} via
+  {{rate_source_hint}}.
+  1. Compare the current quote to the baseline rate of {{baseline_rate}}
+     per {{rate_unit}}.
+  2. Flag if it's {{spike_threshold_pct}}% or more above baseline.
+  3. Report the current rate, the delta, and if visible, the likely driver
+     (fuel surcharge, capacity crunch, seasonal demand).
+variables:
+  lane_description:
+    default: "Los Angeles, CA to Chicago, IL"
+    description: Origin/destination lane to check.
+  rate_source_hint:
+    default: "your freight broker or a rate index (DAT, Freightos)"
+    description: Where to check current freight rates.
+  baseline_rate:
+    default: 2.50
+    description: Baseline rate per unit to compare against.
+  rate_unit:
+    default: "mile"
+    description: Unit the rate is quoted in.
+  spike_threshold_pct:
+    default: 20
+    description: Percent above baseline that counts as a spike.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — freight rate sources vary (broker quotes, load boards, rate indices) and most don't expose a simple public API.

package/jobs/logistics/shipment-delay-watch.yaml

@@ -0,0 +1,38 @@
+id: shipment-delay-watch
+version: 1
+name: Shipment Delay Watch
+description: >
+  Checks a shipment's tracking status and flags it if it hasn't moved in a
+  while. Use this if a stuck shipment has ever gone unnoticed until a
+  customer asked where their order was.
+category: logistics
+tags: [logistics, shipping, tracking]
+schedule: "0 */6 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  status=$(curl -s -H "Authorization: Bearer {{carrier_api_token}}" "{{tracking_api_url}}" | grep -o '"status":"[^"]*"' | head -n1 | cut -d'"' -f4);
+  updated=$(curl -s -H "Authorization: Bearer {{carrier_api_token}}" "{{tracking_api_url}}" | grep -o '"updated_at":"[^"]*"' | head -n1 | cut -d'"' -f4);
+  if [ -z "$status" ]; then echo "ERROR: could not fetch tracking status from {{tracking_api_url}}"; exit 1; fi;
+  updated_ts=$(date -d "$updated" +%s 2>/dev/null);
+  now_ts=$(date +%s);
+  hours_stale=$(( (now_ts - updated_ts) / 3600 ));
+  if [ "$hours_stale" -ge "{{stale_hours}}" ] && [ "$status" != "delivered" ]; then
+    echo "WARNING: shipment {{shipment_id}} status \"$status\" hasn't updated in $hours_stale hours";
+    exit 1;
+  else echo "OK: shipment {{shipment_id}} status \"$status\", updated $hours_stale hours ago"; fi
+variables:
+  shipment_id:
+    default: "your-shipment-id"
+    description: Shipment/tracking identifier, for labeling output.
+  tracking_api_url:
+    default: "https://api.example-carrier.com/track/your-shipment-id"
+    description: Carrier tracking API endpoint returning status and updated_at.
+  carrier_api_token:
+    default: "your-api-token"
+    description: Bearer token for the carrier's tracking API.
+  stale_hours:
+    default: 48
+    description: Hours without a status update before it's flagged as delayed.
+compatible_agents: [generic, claude, codex]
+notes: Generic REST pattern — point tracking_api_url at your carrier or aggregator's (EasyPost, AfterShip, ShipEngine) tracking endpoint; adjust field names to match its response shape.

package/jobs/manufacturing/preventive-maintenance-due-check.yaml

@@ -0,0 +1,31 @@
+id: preventive-maintenance-due-check
+version: 1
+name: Preventive Maintenance Due Check
+description: >
+  Flags equipment coming due for scheduled preventive maintenance. Use
+  this if a machine has ever failed unexpectedly that would've been
+  caught by a PM visit nobody scheduled in time.
+category: manufacturing
+tags: [manufacturing, maintenance, equipment]
+schedule: "0 7 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" -v warn={{warn_days}} '
+    NR>1 {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline due_ts; close(cmd);
+      days_left = int((due_ts - today) / 86400);
+      if (days_left <= warn) print "WARNING: equipment \"" $1 "\" PM due in " days_left " days (" $2 ")";
+    }
+  ' {{pm_schedule_csv}}
+variables:
+  pm_schedule_csv:
+    default: "pm-schedule.csv"
+    description: "CSV with header row, columns: equipment_id,next_pm_date(YYYY-MM-DD)."
+  warn_days:
+    default: 7
+    description: Days before the scheduled PM date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Keep pm-schedule.csv updated from your CMMS export or maintenance log before each run.

package/jobs/manufacturing/production-line-downtime-watch.yaml

@@ -0,0 +1,34 @@
+id: production-line-downtime-watch
+version: 1
+name: Production Line Downtime Watch
+description: >
+  Checks how long a production line has been stopped and flags it once it
+  crosses a threshold. Use this if a line has ever sat down far longer
+  than anyone realized because the stoppage alert never made it to the
+  right person.
+category: manufacturing
+tags: [manufacturing, downtime, production]
+schedule: "*/15 * * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  status=$(curl -s "{{line_status_api_url}}" | grep -o '"status":"[^"]*"' | head -n1 | cut -d'"' -f4);
+  since=$(curl -s "{{line_status_api_url}}" | grep -o '"status_since":"[^"]*"' | head -n1 | cut -d'"' -f4);
+  if [ "$status" != "stopped" ]; then echo "OK: line {{line_id}} status is $status"; exit 0; fi;
+  since_ts=$(date -d "$since" +%s 2>/dev/null);
+  now_ts=$(date +%s);
+  minutes_down=$(( (now_ts - since_ts) / 60 ));
+  if [ "$minutes_down" -ge "{{threshold_minutes}}" ]; then echo "WARNING: line {{line_id}} stopped for $minutes_down minutes"; exit 1;
+  else echo "OK: line {{line_id}} stopped for $minutes_down minutes (under threshold)"; fi
+variables:
+  line_id:
+    default: "line-1"
+    description: Identifier of the production line, for labeling output.
+  line_status_api_url:
+    default: "https://api.example-mes.com/lines/line-1/status"
+    description: MES/SCADA API endpoint returning status and status_since fields.
+  threshold_minutes:
+    default: 30
+    description: Minutes stopped before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: Generic REST pattern — point line_status_api_url at your MES/SCADA system's status endpoint; adjust field names to match its response shape.

package/jobs/manufacturing/quality-defect-rate-check.yaml

@@ -0,0 +1,20 @@
+id: quality-defect-rate-check
+version: 1
+name: Quality Defect Rate Check
+description: >
+  Checks today's defect rate against a target and flags it if it's
+  running high. Use this if a quality problem has ever run for a full
+  shift before anyone pulled the numbers and noticed.
+category: manufacturing
+tags: [manufacturing, quality, defects]
+schedule: "0 */4 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  psql "{{database_url}}" -t -c "select round(100.0 * sum(case when defective then 1 else 0 end) / count(*), 2) from inspections where inspected_at >= current_date;"
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the quality/inspections database.
+compatible_agents: [generic, claude, codex]
+notes: Assumes an `inspections` table with a boolean `defective` column and `inspected_at` timestamp — adjust the query to your QMS schema; compare the printed rate against your target manually or extend the command with a threshold check.

package/jobs/marketing/ad-spend-pacing-check.yaml

@@ -0,0 +1,37 @@
+id: ad-spend-pacing-check
+version: 1
+name: Ad Spend Pacing Check
+description: >
+  Checks a campaign's spend so far against where it should be by this
+  point in the budget period, and flags over- or under-pacing. Use this
+  if a campaign has ever blown through its monthly budget in the first
+  two weeks because nobody was watching the burn rate.
+category: marketing
+tags: [marketing, ads, budget]
+schedule: "0 8 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check spend for campaign {{campaign_name}} on {{ad_platform_hint}}.
+  1. Pull total spend so far this budget period against the
+     {{budget_usd}} budget.
+  2. Compute expected spend-to-date based on days elapsed vs. total days
+     in the period, and compare to actual.
+  3. Flag if pacing is more than {{pacing_threshold_pct}}% over or under
+     the expected pace.
+  4. Report actual vs. expected spend and the pacing delta.
+variables:
+  campaign_name:
+    default: "your campaign"
+    description: Name/ID of the ad campaign to check.
+  ad_platform_hint:
+    default: "Google Ads, Meta Ads, or similar"
+    description: Which ad platform the campaign runs on.
+  budget_usd:
+    default: 5000
+    description: Total budget for the period, in USD.
+  pacing_threshold_pct:
+    default: 15
+    description: Percent over/under expected pace that triggers a flag.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — ad platform APIs need OAuth per-platform, and pacing math needs the campaign's period boundaries which vary by setup.

package/jobs/marketing/email-deliverability-check.yaml

@@ -0,0 +1,37 @@
+id: email-deliverability-check
+version: 1
+name: Email Deliverability Check
+description: >
+  Checks recent bounce and spam-complaint rates for your email sends and
+  flags a spike. Use this if a deliverability problem has ever quietly
+  tanked open rates for a week before anyone checked the actual bounce
+  numbers.
+category: marketing
+tags: [marketing, email, deliverability]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  stats=$(curl -s -H "Authorization: Bearer {{esp_api_token}}" "{{esp_stats_api_url}}");
+  bounce_rate=$(echo "$stats" | grep -o '"bounce_rate":[0-9.]*' | cut -d: -f2);
+  complaint_rate=$(echo "$stats" | grep -o '"complaint_rate":[0-9.]*' | cut -d: -f2);
+  if [ -z "$bounce_rate" ]; then echo "ERROR: could not fetch stats from {{esp_stats_api_url}}"; exit 1; fi;
+  flagged=0;
+  if awk "BEGIN{exit !($bounce_rate > {{max_bounce_pct}})}"; then echo "WARNING: bounce rate ${bounce_rate}% over threshold {{max_bounce_pct}}%"; flagged=1; fi;
+  if awk "BEGIN{exit !($complaint_rate > {{max_complaint_pct}})}"; then echo "WARNING: complaint rate ${complaint_rate}% over threshold {{max_complaint_pct}}%"; flagged=1; fi;
+  if [ "$flagged" -eq 0 ]; then echo "OK: bounce ${bounce_rate}%, complaint ${complaint_rate}%"; else exit 1; fi
+variables:
+  esp_stats_api_url:
+    default: "https://api.example-esp.com/stats/recent"
+    description: Email service provider stats API endpoint returning bounce_rate and complaint_rate.
+  esp_api_token:
+    default: "your-api-token"
+    description: API token for the email service provider.
+  max_bounce_pct:
+    default: 2
+    description: Bounce rate percent that triggers a warning.
+  max_complaint_pct:
+    default: 0.1
+    description: Spam complaint rate percent that triggers a warning.
+compatible_agents: [generic, claude, codex]
+notes: Generic REST pattern — point esp_stats_api_url at your ESP's (SendGrid, Mailgun, Postmark) stats endpoint; adjust field names to match its response shape.

package/jobs/marketing/seo-rank-drop-watch.yaml

@@ -0,0 +1,38 @@
+id: seo-rank-drop-watch
+version: 1
+name: SEO Keyword Rank Drop Watch
+description: >
+  Checks a tracked keyword's search ranking and flags a real drop. Use
+  this if a page has ever slipped off page one and nobody noticed until
+  organic traffic was already down for weeks.
+category: marketing
+tags: [seo, rankings, marketing]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check the current search ranking for the keyword "{{keyword}}" targeting
+  {{target_url}}, via {{rank_source_hint}}.
+  1. Compare the current position to the baseline position of
+     {{baseline_position}}.
+  2. Flag a drop of {{drop_threshold_positions}} positions or more.
+  3. If dropped, note which competing URLs now outrank {{target_url}}, if
+     visible.
+variables:
+  keyword:
+    default: "your target keyword"
+    description: Keyword to track.
+  target_url:
+    default: "https://example.com/page"
+    description: URL you're tracking rank for.
+  rank_source_hint:
+    default: "a rank tracker (Ahrefs, SEMrush, Search Console) or a manual SERP check"
+    description: Where to check current rank.
+  baseline_position:
+    default: 5
+    description: Baseline ranking position to compare against.
+  drop_threshold_positions:
+    default: 5
+    description: Position drop that counts as a real regression.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — SERP position checking needs a rank-tracking API or live search, both of which vary by provider/region.

package/jobs/nonprofit/grant-deadline-reminder.yaml

@@ -0,0 +1,44 @@
+id: grant-deadline-reminder
+version: 1
+name: Grant Deadline Reminder
+description: >
+  Warns you before a grant application deadline, and can help draft the
+  application. Use this if a funding opportunity has ever been missed
+  simply because the deadline crept up during a busy week.
+category: nonprofit
+tags: [nonprofit, grants, fundraising]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: hybrid
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" -v warn={{warn_days}} '
+    NR>1 {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline due_ts; close(cmd);
+      days_left = int((due_ts - today) / 86400);
+      if (days_left <= warn && days_left >= 0) print "WARNING: grant \"" $1 "\" due in " days_left " days (" $2 ")";
+    }
+  ' {{grants_csv}}
+prompt: |
+  Check {{grants_csv}} for grant application deadlines within
+  {{warn_days}} days.
+  1. Flag any that are close, listing days remaining.
+  2. For the closest one, help draft or outline the application based on
+     {{org_mission_hint}} — key sections, and what evidence/data to pull
+     together first.
+script_note: >
+  `command` only checks dates and warns. `prompt` also helps draft/outline
+  the closest application, which needs an LLM.
+variables:
+  grants_csv:
+    default: "grants.csv"
+    description: "CSV with header row, columns: grant_name,deadline(YYYY-MM-DD)."
+  warn_days:
+    default: 21
+    description: Days before deadline to start warning.
+  org_mission_hint:
+    default: "your organization's mission and programs"
+    description: Brief context on the org, to help draft the application outline.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Keep grants.csv updated with opportunities as you find them.

package/jobs/nonprofit/lapsed-donor-check.yaml

@@ -0,0 +1,26 @@
+id: lapsed-donor-check
+version: 1
+name: Lapsed Donor Check
+description: >
+  Flags donors who gave before but haven't in a while, before they're
+  fully lost. Use this if lapsed-donor outreach only happens during the
+  annual campaign instead of catching people while it's still recoverable.
+category: nonprofit
+tags: [nonprofit, donors, fundraising]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  psql "{{database_url}}" -t -c "select name, email, last_donation_at from donors where last_donation_at < now() - interval '{{lapsed_months}} months' and last_donation_at > now() - interval '{{lapsed_months}} months' - interval '90 days';"
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the donor database.
+  lapsed_months:
+    default: 12
+    description: Months since last donation before a donor counts as lapsing.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Assumes a `donors` table with `last_donation_at` — the 90-day window
+  after the lapsed_months mark keeps this from re-flagging the same donor
+  every run indefinitely.

package/jobs/nonprofit/volunteer-hours-shortfall-check.yaml

@@ -0,0 +1,30 @@
+id: volunteer-hours-shortfall-check
+version: 1
+name: Volunteer Hours Shortfall Check
+description: >
+  Compares logged volunteer hours against a program's target and flags a
+  shortfall. Use this if a program has ever fallen behind on a grant's
+  volunteer-hour commitment without anyone noticing until the report was
+  due.
+category: nonprofit
+tags: [nonprofit, volunteers, programs]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  logged=$(awk -F, -v month="$(date +%Y-%m)" -v program="{{program_name}}" '$1 ~ month && $2 == program {sum += $3} END {print sum+0}' {{volunteer_hours_csv}});
+  target={{monthly_target_hours}};
+  if awk "BEGIN{exit !($logged < $target)}"; then echo "WARNING: {{program_name}} logged $logged of $target target hours this month"; exit 1;
+  else echo "OK: {{program_name}} logged $logged of $target target hours"; fi
+variables:
+  volunteer_hours_csv:
+    default: "volunteer-hours.csv"
+    description: "CSV with columns: month(YYYY-MM),program,hours."
+  program_name:
+    default: "your program"
+    description: Program name to check.
+  monthly_target_hours:
+    default: 100
+    description: Target volunteer hours for the program this month.
+compatible_agents: [generic, claude, codex]
+notes: Keep volunteer-hours.csv updated from your volunteer management system's export before each run.

package/jobs/podcast/episode-publish-gap-check.yaml

@@ -0,0 +1,29 @@
+id: episode-publish-gap-check
+version: 1
+name: Podcast Episode Publish Gap Check
+description: >
+  Checks that a new episode has gone out recently and flags it if your
+  publish cadence has slipped. Use this if listeners have ever noticed a
+  gap in your feed before you did.
+category: podcast
+tags: [podcast, publishing, cadence]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  lastmod=$(curl -s {{feed_url}} | grep -o '<pubDate>[^<]*' | sed 's/<pubDate>//' | head -n1);
+  if [ -z "$lastmod" ]; then echo "WARNING: could not find any <pubDate> in {{feed_url}}"; exit 1; fi;
+  last_ts=$(date -d "$lastmod" +%s 2>/dev/null);
+  now_ts=$(date +%s);
+  days_since=$(( (now_ts - last_ts) / 86400 ));
+  if [ "$days_since" -ge "{{max_gap_days}}" ]; then echo "WARNING: last episode was $days_since days ago"; exit 1;
+  else echo "OK: last episode was $days_since days ago"; fi
+variables:
+  feed_url:
+    default: "https://example.com/podcast/feed.xml"
+    description: URL of the podcast's RSS feed.
+  max_gap_days:
+    default: 14
+    description: Days since the last episode before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: Relies on the feed's <pubDate> being in a standard RFC 822 format, which most podcast hosts produce.

package/jobs/podcast/guest-followup-reminder.yaml

@@ -0,0 +1,31 @@
+id: guest-followup-reminder
+version: 1
+name: Podcast Guest Follow-up Reminder
+description: >
+  Flags recorded guest episodes that haven't been published or thanked
+  yet. Use this if a guest has ever had to awkwardly ask when their
+  episode was coming out because nobody followed up after recording.
+category: podcast
+tags: [podcast, guests, followup]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" -v warn={{warn_days}} '
+    NR>1 && $3 == "unpublished" {
+      cmd="date -d \"" $2 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $2 "\" +%s";
+      cmd | getline recorded_ts; close(cmd);
+      days_since = int((today - recorded_ts) / 86400);
+      if (days_since >= warn) print "WARNING: episode with " $1 " recorded " days_since " days ago, still unpublished";
+    }
+  ' {{guest_episodes_csv}}
+variables:
+  guest_episodes_csv:
+    default: "guest-episodes.csv"
+    description: "CSV with header row, columns: guest_name,recorded_date(YYYY-MM-DD),status(unpublished/published)."
+  warn_days:
+    default: 14
+    description: Days since recording before an unpublished episode is flagged.
+compatible_agents: [generic, claude, codex]
+notes: Keep guest-episodes.csv updated as episodes are recorded and published — one row per guest episode.

package/jobs/podcast/sponsor-deliverable-tracker.yaml

@@ -0,0 +1,31 @@
+id: sponsor-deliverable-tracker
+version: 1
+name: Podcast Sponsor Deliverable Tracker
+description: >
+  Flags sponsor deliverables (read, mention, social post) coming due. Use
+  this if you've ever had a sponsor follow up asking where their promised
+  mention was.
+category: podcast
+tags: [podcast, sponsorship, deliverables]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  awk -F, -v today="$today" -v warn={{warn_days}} '
+    NR>1 {
+      cmd="date -d \"" $3 "\" +%s 2>/dev/null || date -jf \"%Y-%m-%d\" \"" $3 "\" +%s";
+      cmd | getline due_ts; close(cmd);
+      days_left = int((due_ts - today) / 86400);
+      if (days_left <= warn && days_left >= 0) print "WARNING: " $1 " deliverable (" $2 ") due in " days_left " days (" $3 ")";
+    }
+  ' {{sponsor_deliverables_csv}}
+variables:
+  sponsor_deliverables_csv:
+    default: "sponsor-deliverables.csv"
+    description: "CSV with header row, columns: sponsor_name,deliverable,due_date(YYYY-MM-DD)."
+  warn_days:
+    default: 7
+    description: Days before due date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Keep sponsor-deliverables.csv updated whenever a sponsorship deal is signed — one row per deliverable.

package/jobs/productivity/timezone-meeting-conflict-check.yaml

@@ -0,0 +1,31 @@
+id: timezone-meeting-conflict-check
+version: 1
+name: Timezone Meeting Conflict Check
+description: >
+  Checks tomorrow's meetings against a remote teammate's working hours and
+  flags any that fall outside them. Use this if a meeting has ever gotten
+  scheduled at 11pm for someone across the world without anyone realizing.
+category: productivity
+tags: [calendar, timezone, meetings]
+schedule: "0 16 * * *"
+timezone: "America/Los_Angeles"
+runner: agent-prompt
+prompt: |
+  Check tomorrow's calendar for meetings that include {{teammate_name}}
+  (timezone {{teammate_timezone}}, working hours {{working_hours}}).
+  1. Convert each meeting time to {{teammate_name}}'s local time.
+  2. Flag any meeting that falls outside their stated working hours.
+  3. Suggest an alternative time inside working hours for each flagged
+     meeting if the calendar shows open slots.
+variables:
+  teammate_name:
+    default: "your remote teammate"
+    description: Name of the teammate to check meetings against.
+  teammate_timezone:
+    default: "Europe/Berlin"
+    description: IANA timezone for the teammate.
+  working_hours:
+    default: "09:00-18:00"
+    description: The teammate's normal working hours, local time.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: No generic script mode — calendar access and timezone-aware conflict detection need an agent with calendar-tool access.

package/jobs/realestate/lease-expiry-reminder.yaml

@@ -0,0 +1,30 @@
+id: lease-expiry-reminder
+version: 1
+name: Lease Expiry Reminder
+description: >
+  Warns you before a lease ends so there's time to renew, renegotiate, or
+  start looking. Use this if a lease has ever gone month-to-month, or
+  ended, without anyone noticing the date was coming.
+category: realestate
+tags: [realestate, lease, reminder]
+schedule: "0 9 1 * *"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  end_ts=$(date -d "{{lease_end_date}}" +%s 2>/dev/null || date -jf "%Y-%m-%d" "{{lease_end_date}}" +%s);
+  days_left=$(( (end_ts - today) / 86400 ));
+  if [ "$days_left" -le "{{warn_days}}" ]; then echo "WARNING: lease for {{property_name}} ends in $days_left days ({{lease_end_date}})"; exit 1;
+  else echo "OK: lease for {{property_name}} ends in $days_left days"; fi
+variables:
+  property_name:
+    default: "your unit"
+    description: Name/address of the leased property.
+  lease_end_date:
+    default: "2027-01-01"
+    description: Lease end date (YYYY-MM-DD).
+  warn_days:
+    default: 60
+    description: Days before end date to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Manual lease_end_date input — run one copy per property/unit you're tracking.

package/jobs/realestate/rent-payment-late-check.yaml

@@ -0,0 +1,23 @@
+id: rent-payment-late-check
+version: 1
+name: Rent Payment Late Check
+description: >
+  Flags tenants whose rent is overdue past the grace period. Use this if
+  a late payment has ever gone unnoticed for weeks because nobody was
+  cross-checking the rent roll against the bank deposits.
+category: realestate
+tags: [realestate, rent, payments]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  psql "{{database_url}}" -t -c "select tenant_name, unit, amount_due, due_date from rent_ledger where paid = false and due_date < current_date - interval '{{grace_days}} days';"
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the property management database.
+  grace_days:
+    default: 5
+    description: Days past due_date before a late payment is flagged.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a `rent_ledger` table with `paid`, `due_date`, and `amount_due` columns — adjust the query to your property management system's schema.

package/jobs/realestate/rental-vacancy-check.yaml

@@ -0,0 +1,30 @@
+id: rental-vacancy-check
+version: 1
+name: Rental Vacancy Check
+description: >
+  Flags a rental listing that's been vacant longer than expected. Use this
+  if a unit has ever sat empty for months while everyone assumed someone
+  else was handling the listing.
+category: realestate
+tags: [realestate, vacancy, listings]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  today=$(date +%s);
+  vacant_since_ts=$(date -d "{{vacant_since_date}}" +%s 2>/dev/null || date -jf "%Y-%m-%d" "{{vacant_since_date}}" +%s);
+  days_vacant=$(( (today - vacant_since_ts) / 86400 ));
+  if [ "$days_vacant" -ge "{{warn_days}}" ]; then echo "WARNING: {{property_name}} has been vacant $days_vacant days (since {{vacant_since_date}})"; exit 1;
+  else echo "OK: {{property_name}} vacant $days_vacant days"; fi
+variables:
+  property_name:
+    default: "your unit"
+    description: Name/address of the vacant property.
+  vacant_since_date:
+    default: "2026-06-01"
+    description: Date the unit became vacant (YYYY-MM-DD).
+  warn_days:
+    default: 30
+    description: Days vacant before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: Manual vacant_since_date input — update it once the unit is leased, or when a new vacancy starts.

package/jobs/sales/lead-response-time-check.yaml

@@ -0,0 +1,23 @@
+id: lead-response-time-check
+version: 1
+name: Lead Response Time Check
+description: >
+  Flags new inbound leads that haven't gotten a first response within your
+  target window. Use this if you've ever lost a hot lead simply because
+  nobody replied fast enough.
+category: sales
+tags: [sales, leads, response-time]
+schedule: "*/30 * * * *"
+timezone: "UTC"
+runner: shell
+command: >
+  psql "{{database_url}}" -t -c "select name, email, created_at from leads where first_response_at is null and created_at < now() - interval '{{max_response_minutes}} minutes';"
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the leads database.
+  max_response_minutes:
+    default: 30
+    description: Minutes a lead can go without a first response before it's flagged.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a `leads` table with `created_at` and `first_response_at` columns — adjust the query to your CRM's schema.

package/jobs/sales/quota-attainment-check.yaml

@@ -0,0 +1,33 @@
+id: quota-attainment-check
+version: 1
+name: Quota Attainment Check
+description: >
+  Compares a rep's closed-won revenue this period against their quota
+  pace and flags whether they're on track. Use this if a rep has ever
+  found out they missed quota only at the end of the quarter, instead of
+  with enough runway left to fix it.
+category: sales
+tags: [sales, quota, pipeline]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  closed=$(psql "{{database_url}}" -t -c "select coalesce(sum(amount),0) from deals where owner = '{{rep_name}}' and stage = 'closed_won' and closed_at >= date_trunc('quarter', current_date);");
+  quota={{quarterly_quota}};
+  pct=$(awk "BEGIN{printf \"%.0f\", ($closed/$quota)*100}");
+  echo "quota check for {{rep_name}}: closed \$$closed of \$$quota quarterly quota (${pct}%) so far"
+variables:
+  database_url:
+    default: "postgres://user:pass@host:5432/db"
+    description: Connection string for the CRM/deals database.
+  rep_name:
+    default: "rep-name"
+    description: Sales rep owner field to check.
+  quarterly_quota:
+    default: 100000
+    description: Quarterly quota amount for this rep.
+compatible_agents: [generic, claude, codex]
+notes: >
+  Prints closed-won revenue vs. quota for the current quarter; the pacing
+  math (days elapsed vs. days in quarter) is left for you or your agent to
+  interpret since exact quarter boundaries vary by fiscal calendar.