@wonsukchoi/crondex 0.8.0 → 0.9.1

package/jobs/healthcare/patient-recall-reminder.yaml

@@ -0,0 +1,34 @@
+id: patient-recall-reminder
+version: 1
+name: Patient Recall Reminder
+description: >
+  Finds patients due (or overdue) for a routine checkup, cleaning, or
+  screening and lists them for outreach. Use this if recall/recare lists
+  pile up and patients quietly fall off the schedule for a year or more.
+category: healthcare
+tags: [patients, recall, checkup, outreach]
+schedule: "0 8 1 * *"
+timezone: "America/New_York"
+runner: agent-prompt
+prompt: |
+  Check {{scheduling_system}} for patients whose last visit for
+  "{{recall_type}}" was more than {{recall_interval_months}} months ago and
+  who have no future appointment booked.
+  1. List each patient, their last visit date, and how overdue they are.
+  2. Sort by most overdue first.
+  3. Draft a short recall message per patient (or a template if the list is
+     long) inviting them to book.
+  4. Call out anyone more than double the recall interval overdue — these
+     are the ones most at risk of having left the practice entirely.
+variables:
+  scheduling_system:
+    default: "your scheduling/EHR system"
+    description: Name of the scheduling or EHR system to check.
+  recall_type:
+    default: "annual checkup"
+    description: What kind of visit this recall tracks (e.g. "dental cleaning", "annual physical", "eye exam").
+  recall_interval_months:
+    default: 12
+    description: How many months between visits before someone counts as due.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — outreach messages should be reviewed by staff before sending, and must follow your practice's patient communication/compliance policy.

package/jobs/hr/benefits-enrollment-deadline-reminder.yaml

@@ -0,0 +1,34 @@
+id: benefits-enrollment-deadline-reminder
+version: 1
+name: Benefits Open Enrollment Deadline Reminder
+description: >
+  Counts down to the open-enrollment deadline and flags employees who
+  haven't submitted elections yet. Use this if open enrollment has ever
+  closed with people accidentally defaulting to no coverage or last
+  year's plan.
+category: hr
+tags: [hr, benefits, enrollment, deadline]
+schedule: "0 9 * * *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Open enrollment closes on {{enrollment_deadline}}. Check
+  {{benefits_system}} for who has and hasn't submitted elections yet.
+  1. Report days remaining until the deadline.
+  2. List employees with no submitted election.
+  3. If within {{final_warn_days}} days of the deadline, draft an urgent
+     reminder message to the non-responders and, separately, a summary
+     for HR of who still needs a nudge.
+  4. If the deadline has passed, report final completion rate instead.
+variables:
+  enrollment_deadline:
+    default: "YYYY-MM-DD"
+    description: Date open enrollment closes.
+  benefits_system:
+    default: "your benefits administration platform"
+    description: Name of the benefits/HRIS system to check.
+  final_warn_days:
+    default: 5
+    description: Days before deadline to switch from routine reminders to urgent ones.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — review reminder messages before sending, especially anything framed as "urgent" to employees.

package/jobs/hr/new-hire-paperwork-check.yaml

@@ -0,0 +1,35 @@
+id: new-hire-paperwork-check
+version: 1
+name: New Hire Paperwork Completion Check
+description: >
+  Checks which recently started employees still have incomplete
+  onboarding paperwork (I-9, tax forms, benefits enrollment, signed
+  handbook) and flags them before they become a compliance problem. Use
+  this if onboarding paperwork has ever slipped through the cracks past
+  the legal deadline.
+category: hr
+tags: [hr, onboarding, compliance, paperwork]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check onboarding status in {{hris_system}} for anyone who started in the
+  last {{lookback_days}} days.
+  1. For each new hire, list which required documents are still
+     incomplete: {{required_documents}}.
+  2. Flag anyone approaching or past a legal deadline (e.g. I-9 must be
+     completed within 3 business days of start in the US) as urgent.
+  3. Draft a reminder message to the employee and/or their manager for
+     each incomplete item.
+variables:
+  hris_system:
+    default: "your HRIS/onboarding system"
+    description: Name of the HR system to check (e.g. "BambooHR", "Rippling", "Gusto").
+  lookback_days:
+    default: 30
+    description: How far back to check for recent hires.
+  required_documents:
+    default: "I-9, W-4, direct deposit form, benefits enrollment, signed handbook acknowledgment"
+    description: Comma-separated list of documents your onboarding requires.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Legal deadlines for onboarding paperwork vary by country/jurisdiction — confirm the specifics for yours rather than relying on the example given.

package/jobs/hr/payroll-run-reminder.yaml

@@ -0,0 +1,30 @@
+id: payroll-run-reminder
+version: 1
+name: Payroll Run Cutoff Reminder
+description: >
+  Reminds you before the payroll submission cutoff so timesheets and
+  changes get in on time. Use this if payroll has ever run late because a
+  timesheet or new-hire update missed the cutoff by a day.
+category: hr
+tags: [payroll, hr, reminder, deadline]
+schedule: "0 9 * * *"
+timezone: "America/New_York"
+runner: shell
+command: >
+  today=$(date +%d);
+  cutoff="{{cutoff_day_of_month}}";
+  if [ "$today" -ge $((cutoff - {{warn_days_before}})) ] && [ "$today" -le "$cutoff" ]; then
+    echo "PAYROLL CUTOFF APPROACHING: due on day $cutoff of this month, today is day $today.";
+    echo "Checklist: timesheets submitted, new hires entered, terminations processed, PTO adjustments logged.";
+  else
+    echo "No payroll cutoff in the warning window today.";
+  fi
+variables:
+  cutoff_day_of_month:
+    default: 25
+    description: Day of the month payroll submissions are due.
+  warn_days_before:
+    default: 3
+    description: How many days before the cutoff to start reminding.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a fixed monthly cutoff day — adjust the command or add a variable if your payroll provider uses a different schedule (biweekly, semi-monthly).

package/jobs/insurance/claim-status-check.yaml

@@ -0,0 +1,30 @@
+id: claim-status-check
+version: 1
+name: Open Claim Status Check
+description: >
+  Checks the status of any open insurance claims and flags ones that
+  haven't moved in a while. Use this if a claim has ever gone quiet for
+  weeks because nobody was following up with the adjuster.
+category: insurance
+tags: [insurance, claims, follow-up]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check the status of each open claim listed: {{open_claims}} (via the
+  insurer's portal, email correspondence, or whatever access is
+  available).
+  1. Report current status and last update date for each.
+  2. Flag any claim with no status change in more than
+     {{stale_after_days}} days as needing follow-up.
+  3. Draft a short follow-up message to the adjuster for each stale claim,
+     referencing the claim number and asking for a status update.
+variables:
+  open_claims:
+    default: "list your open claim numbers here"
+    description: Comma-separated list of open claim numbers/references to track.
+  stale_after_days:
+    default: 14
+    description: Days without a status update before a claim counts as stale.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — review before sending anything to an adjuster or insurer.

package/jobs/insurance/coverage-gap-audit.yaml

@@ -0,0 +1,37 @@
+id: coverage-gap-audit
+version: 1
+name: Coverage Gap Audit
+description: >
+  Compares your current insurance policies against a standard coverage
+  checklist for your situation and flags anything missing or underinsured.
+  Use this if you've ever added a policy for one specific thing and never
+  circled back to check the overall picture still made sense.
+category: insurance
+tags: [insurance, coverage, audit, risk]
+schedule: "0 9 1 1,7 *"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Review the current policies listed: {{current_policies}}, for a
+  {{profile_type}} profile.
+  1. Compare against a standard coverage checklist for that profile type
+     (e.g. for a homeowner: dwelling, liability, flood/earthquake if
+     applicable, umbrella; for a small business: general liability,
+     property, cyber, workers' comp as relevant).
+  2. Flag anything commonly recommended that's missing entirely.
+  3. Flag any policy whose coverage limit looks low relative to
+     {{asset_value_estimate}} in assets/exposure, with a one-line reason.
+  4. This is a gap-finding pass, not financial/legal advice — say so, and
+     recommend confirming any changes with a licensed agent.
+variables:
+  current_policies:
+    default: "list your current policies and coverage limits here"
+    description: Summary of currently held policies and their limits.
+  profile_type:
+    default: "homeowner"
+    description: Who this audit is for (e.g. "homeowner", "renter", "small business", "landlord").
+  asset_value_estimate:
+    default: "not specified"
+    description: Rough total value of assets/exposure to size coverage against.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: General-knowledge gap-finding only — not a substitute for advice from a licensed insurance professional.

package/jobs/insurance/policy-renewal-reminder.yaml

@@ -0,0 +1,35 @@
+id: policy-renewal-reminder
+version: 1
+name: Policy Renewal Reminder
+description: >
+  Warns you before an insurance policy's renewal date so you have time to
+  shop around or review coverage, instead of auto-renewing on autopilot.
+  Use this if you've ever realized a policy renewed months ago at a higher
+  rate without you noticing.
+category: insurance
+tags: [insurance, renewal, policy, reminder]
+schedule: "0 8 * * *"
+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 && diff_days >= 0) {
+        printf "RENEWAL DUE: %s renews %s (%d days)\n", $1, $2, diff_days;
+      }
+    }
+  ' "{{policies_csv_path}}"
+variables:
+  policies_csv_path:
+    default: "./insurance-policies.csv"
+    description: "Path to a CSV with columns: policy_name,renewal_date (YYYY-MM-DD)."
+  warn_days_before:
+    default: 30
+    description: How many days before renewal to start warning.
+compatible_agents: [generic, claude, codex]
+notes: Maintain the CSV manually or export it from whatever policy-management tool/broker portal you use.

package/jobs/marketing/competitor-page-diff-watch.yaml

@@ -0,0 +1,52 @@
+id: competitor-page-diff-watch
+version: 2
+name: Competitor Page Diff Watch
+description: >
+  Snapshots a competitor's pricing or landing page and diffs it against the
+  last snapshot, turning any real change into a short action memo instead
+  of a wall of markup diff. Use this if a competitor has ever changed
+  pricing or repositioned a page and you found out from a customer instead
+  of noticing it yourself.
+category: marketing
+tags: [competitor, monitoring, pricing, marketing]
+schedule: "0 9 * * 1"
+timezone: "UTC"
+runner: hybrid
+command: >
+  snapshot_dir="{{snapshot_dir}}";
+  mkdir -p "$snapshot_dir";
+  today_file="$snapshot_dir/$(date +%Y-%m-%d).html";
+  curl -s -A "Mozilla/5.0" "{{competitor_url}}" -o "$today_file";
+  prev_file="";
+  for f in "$snapshot_dir"/*.html; do
+    [ "$(basename "$f")" = "$(basename "$today_file")" ] && continue;
+    prev_file=$(basename "$f");
+  done;
+  if [ -n "$prev_file" ]; then
+    diff "$snapshot_dir/$prev_file" "$today_file" | head -100;
+  else
+    echo "first snapshot taken, nothing to diff against yet.";
+  fi
+prompt: |
+  Compare today's snapshot of {{competitor_url}} against the previous one
+  (raw HTML diff provided by the script, or fetch and compare yourself).
+  1. Ignore markup/whitespace/tracking-param noise.
+  2. Summarize any real content change: pricing, plan names, feature
+     claims, or messaging changes.
+  3. If nothing meaningful changed, say so in one line.
+  4. If something did change, draft a short internal action memo: what
+     changed, why it might matter, and one suggested response (match
+     pricing, update our comparison page, no action needed).
+script_note: >
+  `command` only saves a raw HTML diff — full of markup and whitespace
+  noise, no interpretation of what actually changed or whether it matters.
+  `prompt` filters the noise and produces an actionable summary.
+variables:
+  competitor_url:
+    default: "https://example.com/pricing"
+    description: Competitor page URL to monitor (pricing/landing pages work best).
+  snapshot_dir:
+    default: "./competitor-snapshots"
+    description: Local directory to store daily HTML snapshots for diffing.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Respect the target site's robots.txt/terms before scraping; some sites render pricing via JS and won't diff meaningfully from raw HTML alone.

package/jobs/personal/bill-due-reminder.yaml

@@ -1,5 +1,5 @@
 id: bill-due-reminder
-version: 1
+version: 2
 name: Bill Due Reminder
 description: >
   Warns you a few days before a recurring monthly bill is due. Use this if
@@ -13,7 +13,7 @@ command: >
   due={{due_day_of_month}}; warn={{warn_days}}; name="{{bill_name}}";
   today=$(date +%-d);
   days_left=$(( due - today ));
-  if [ "$days_left" -lt 0 ]; then days_left=$(( days_left + 30 )); fi
+  if [ "$days_left" -lt 0 ]; then days_left=$(( days_left + 30 )); fi;
   if [ "$days_left" -le "$warn" ]; then echo "REMINDER: $name due in $days_left day(s) (on day $due of the month)";
   else echo "OK: $name due in $days_left day(s)"; fi
 variables:

package/jobs/personal/end-of-day-wrap-message.yaml

@@ -0,0 +1,32 @@
+id: end-of-day-wrap-message
+version: 1
+name: End-of-Day Wrap Message
+description: >
+  Fires around the end of your work calendar and drafts a short wrap-up:
+  what got done today, what's carrying over to tomorrow. Use this if you
+  close your laptop most days without a clear sense of what actually
+  happened or what's still pending.
+category: personal
+tags: [reflection, end-of-day, productivity, wrap-up]
+schedule: "0 18 * * 1-5"
+timezone: "America/Los_Angeles"
+runner: agent-prompt
+prompt: |
+  Look at today's completed calendar events, closed tasks/tickets, and
+  commits (whatever of {{activity_sources}} is available) for
+  {{lookback_hours}} hours.
+  1. Summarize in 2-3 bullets what got meaningfully done today.
+  2. List anything left open that was expected to close today, as
+     "carrying over to tomorrow."
+  3. End with one line acknowledging the day plainly — no forced
+     positivity, just an honest close.
+  Keep the whole thing short enough to read in 15 seconds.
+variables:
+  activity_sources:
+    default: "your calendar, task tracker, and git commits"
+    description: Comma-separated list of sources to check for today's activity.
+  lookback_hours:
+    default: 10
+    description: Rough length of the workday to look back over.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Schedule this against your actual calendar end time, not a fixed hour, if your agent can read "last event ends at" dynamically.

package/jobs/personal/new-restaurant-roundup.yaml

@@ -0,0 +1,35 @@
+id: new-restaurant-roundup
+version: 1
+name: New Restaurant Roundup
+description: >
+  Checks for restaurants that newly opened near you in the last week and
+  gives you a short list to consider. Use this if you like trying new
+  places but never remember to actually go looking for what just opened.
+category: personal
+tags: [restaurants, local, discovery, weekly]
+schedule: "0 17 * * 5"
+timezone: "America/Los_Angeles"
+runner: agent-prompt
+prompt: |
+  Check for restaurants that newly opened within {{radius_miles}} miles of
+  {{location}} in the last {{lookback_days}} days (via Yelp, Google Maps,
+  local news, or whatever local-discovery source is available).
+  1. List each new place: name, cuisine, and distance.
+  2. Note anything getting early buzz (a write-up, strong early reviews).
+  3. Keep it to the top {{max_results}} most promising — this is a quick
+     Friday-evening list, not a research report.
+variables:
+  location:
+    default: "your city/neighborhood"
+    description: Location to search around.
+  radius_miles:
+    default: 5
+    description: Search radius in miles.
+  lookback_days:
+    default: 14
+    description: How recently a restaurant must have opened to count as "new."
+  max_results:
+    default: 5
+    description: Max number of places to list.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Quality depends on local coverage in whatever source the agent can reach — sparser in small towns than big cities.

package/jobs/productivity/morning-briefing-digest.yaml

@@ -0,0 +1,42 @@
+id: morning-briefing-digest
+version: 1
+name: Morning Briefing Digest
+description: >
+  Pulls together overnight email, today's calendar, and any connected
+  analytics/monitoring dashboards into one short digest waiting for you at
+  the start of the day. Use this if you start your morning tab-hopping
+  across five dashboards before you've even had coffee.
+category: productivity
+tags: [briefing, digest, morning, calendar, email]
+schedule: "0 7 * * 1-5"
+timezone: "America/Los_Angeles"
+runner: agent-prompt
+prompt: |
+  Build a short morning briefing covering:
+  1. Calendar: today's meetings from {{calendar_source}}, flagging any
+     back-to-back blocks with no prep time.
+  2. Email: unread messages from {{email_source}} in the last
+     {{lookback_hours}} hours that look like they need a same-day reply —
+     skip newsletters/notifications.
+  3. Metrics: anything notable from {{dashboard_sources}} (traffic spike or
+     drop, error rate change, ranking movement) — only report real changes,
+     not routine noise.
+  4. End with a single "top 3 things to do today" list synthesized from the
+     above.
+  Keep the whole digest to one screen — this replaces tab-hopping, it
+  shouldn't become its own chore to read.
+variables:
+  calendar_source:
+    default: "your calendar (e.g. Google Calendar)"
+    description: Calendar to pull today's meetings from.
+  email_source:
+    default: "your inbox (e.g. Gmail)"
+    description: Inbox to scan for messages needing a same-day reply.
+  dashboard_sources:
+    default: "analytics/search console/uptime monitoring, whatever you have connected"
+    description: Comma-separated list of dashboards/metrics sources to check.
+  lookback_hours:
+    default: 16
+    description: How far back to scan email (covers overnight since last workday).
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Value scales with how many sources you connect — start with just calendar+email and add dashboards as they're available.

package/jobs/productivity/recurring-task-queue-reset.yaml

@@ -0,0 +1,37 @@
+id: recurring-task-queue-reset
+version: 2
+name: Recurring Task Queue Reset
+description: >
+  Clears out last week's completed recurring-task checklist and creates a
+  fresh one from your template, so every cycle starts with the same
+  predefined owners and checklist instead of a copy-pasted mess. Use this
+  if your recurring weekly checklist has ever quietly drifted because
+  someone edited last week's copy instead of starting clean.
+category: productivity
+tags: [productivity, checklist, recurring, template]
+schedule: "0 6 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  if [ ! -f "{{template_path}}" ]; then
+    echo "template not found at {{template_path}} — nothing to reset from.";
+    exit 1;
+  fi;
+  week_label=$(date +%G-W%V);
+  dest="{{output_dir}}/${week_label}.md";
+  mkdir -p "{{output_dir}}";
+  if [ -f "$dest" ]; then
+    echo "$dest already exists — not overwriting this week's checklist.";
+  else
+    cp "{{template_path}}" "$dest";
+    echo "created fresh checklist: $dest";
+  fi
+variables:
+  template_path:
+    default: "./templates/weekly-checklist.md"
+    description: Path to the checklist template with predefined owners/items.
+  output_dir:
+    default: "./weekly-checklists"
+    description: Directory where each week's fresh checklist file is written.
+compatible_agents: [generic, claude, codex]
+notes: File-based by default for portability — swap `cp` for your task tool's API call (Notion, Asana, ClickUp) if you want it created there instead of as a local file.

package/jobs/restaurant/health-inspection-prep-reminder.yaml

@@ -0,0 +1,29 @@
+id: health-inspection-prep-reminder
+version: 1
+name: Health Inspection Prep Reminder
+description: >
+  Reminds the team of the standard health-inspection checklist on a
+  recurring basis, not just when an inspection is imminent. Use this if
+  you've ever scrambled the morning an inspector showed up unannounced.
+category: restaurant
+tags: [compliance, health-inspection, checklist, kitchen]
+schedule: "0 7 * * 1"
+timezone: "America/New_York"
+runner: shell
+command: >
+  echo "Weekly health-inspection self-check ({{checklist_path}}):";
+  if [ -f "{{checklist_path}}" ]; then cat "{{checklist_path}}"; else
+  echo "- Fridge/freezer temps logged and in range";
+  echo "- Handwashing stations stocked (soap, towels, signage)";
+  echo "- Food storage labeled with dates, FIFO followed";
+  echo "- No bare-hand contact with ready-to-eat food";
+  echo "- Pest control log up to date";
+  echo "- Cleaning/sanitizing log current";
+  echo "- Employee health/illness policy posted";
+  fi
+variables:
+  checklist_path:
+    default: "./health-inspection-checklist.txt"
+    description: Optional path to your own custom checklist file; falls back to a standard baseline if not found.
+compatible_agents: [generic, claude, codex]
+notes: This is a recurring self-audit reminder, not a substitute for your local health department's actual requirements — adapt the checklist to your jurisdiction.

package/jobs/restaurant/inventory-waste-log-review.yaml

@@ -0,0 +1,32 @@
+id: inventory-waste-log-review
+version: 1
+name: Inventory Waste Log Review
+description: >
+  Reviews the kitchen's waste log for the week and flags which items are
+  being tossed most, in case it's an over-ordering or portioning problem.
+  Use this if food cost keeps creeping up and nobody's sure why.
+category: restaurant
+tags: [inventory, waste, food-cost, kitchen]
+schedule: "0 10 * * 1"
+timezone: "America/New_York"
+runner: agent-prompt
+prompt: |
+  Read the waste log for the past {{lookback_days}} days from
+  {{waste_log_source}}.
+  1. Total waste by item (quantity and estimated cost if given).
+  2. Rank the top 5 items by wasted cost.
+  3. For each top item, note the most common waste reason logged (spoilage,
+     over-prep, returned order, etc.) if that field exists.
+  4. Flag any item where waste looks like it's trending up week over week,
+     not just a one-off bad night.
+  5. Suggest one concrete action per top item (reduce par level, tighten
+     portioning, adjust prep timing).
+variables:
+  waste_log_source:
+    default: "your POS/inventory system's waste log"
+    description: Where the waste log lives (e.g. "Toast waste tracking", "a shared spreadsheet").
+  lookback_days:
+    default: 7
+    description: How many days of waste log to review.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Quality of the report depends entirely on how consistently staff logs waste — garbage in, garbage out.

package/jobs/restaurant/reservation-noshow-deposit-check.yaml

@@ -0,0 +1,32 @@
+id: reservation-noshow-deposit-check
+version: 1
+name: Reservation No-Show Pattern Check
+description: >
+  Reviews recent reservation no-shows and flags parties/times where
+  no-shows cluster, so you know whether a deposit or confirmation-call
+  policy would help. Use this if a certain night or party size keeps
+  costing you empty tables.
+category: restaurant
+tags: [reservations, no-show, hospitality]
+schedule: "0 11 * * 1"
+timezone: "America/New_York"
+runner: agent-prompt
+prompt: |
+  Pull reservation data from {{reservation_system}} for the past
+  {{lookback_days}} days.
+  1. Calculate the overall no-show rate.
+  2. Break it down by day of week, time slot, and party size — flag any
+     segment with a no-show rate meaningfully above the overall average.
+  3. List repeat no-show guests (2+ in the window) by name/phone if
+     available.
+  4. Recommend whether a deposit or confirmation-text policy is warranted
+     for the flagged segments specifically, rather than restaurant-wide.
+variables:
+  reservation_system:
+    default: "your reservation platform"
+    description: Name of the reservation system (e.g. "OpenTable", "Resy", "Tock").
+  lookback_days:
+    default: 30
+    description: Window of reservation history to analyze.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Read-only analysis — any policy change (deposits, blocklisting repeat no-shows) is a business decision for a human to make.

package/jobs/sales/newly-funded-leads-scout.yaml

@@ -0,0 +1,44 @@
+id: newly-funded-leads-scout
+version: 1
+name: Newly Funded Companies Lead Scout
+description: >
+  Checks funding-announcement sources for companies that just raised in
+  your target market and drafts a first-outreach message for each. Use
+  this if you sell to companies that spend differently right after a
+  funding round and you want to reach them before every other vendor does.
+category: sales
+tags: [sales, leads, funding, outreach, prospecting]
+schedule: "0 8 * * 1-5"
+timezone: "UTC"
+runner: agent-prompt
+prompt: |
+  Check {{funding_sources}} for companies that announced a funding round in
+  the last {{lookback_days}} days matching: industry "{{target_industry}}",
+  stage "{{target_stage}}".
+  1. List each company: name, round size/stage, and a one-line note on why
+     they fit the target profile.
+  2. For each, note the most relevant contact if discoverable (founder,
+     head of the department your product serves).
+  3. Draft a short, non-generic first-touch outreach message per company
+     that references the funding news and ties it to a concrete reason
+     they'd need {{your_product}} now.
+  4. Skip companies already in {{existing_crm_note}} to avoid duplicate
+     outreach.
+variables:
+  funding_sources:
+    default: "Crunchbase, TechCrunch funding news, or your preferred funding-news feed"
+    description: Sources to check for funding announcements.
+  target_industry:
+    default: "SaaS"
+    description: Industry/vertical to filter for.
+  target_stage:
+    default: "Seed or Series A"
+    description: Funding stage(s) worth prospecting.
+  your_product:
+    default: "your product"
+    description: One-line description of what you sell, for the outreach draft to reference.
+  existing_crm_note:
+    default: "no CRM connected — skip duplicate check"
+    description: Where to check for companies already in your pipeline, to avoid re-outreaching.
+compatible_agents: [claude, codex, hermes, openclaw, generic]
+notes: Draft-only — review before sending, and check the funding source's terms of use before scraping instead of using an official API/RSS feed.

package/jobs/security/open-port-check.yaml

@@ -1,5 +1,5 @@
 id: open-port-check
-version: 1
+version: 2
 name: Expected Open Ports Check
 description: >
   Checks that the ports you expect to be open on a host actually are, and
@@ -16,7 +16,7 @@ command: >
     if command -v nc >/dev/null 2>&1; then
       nc -z -w2 "$host" "$p" 2>/dev/null && echo "OK: $host:$p open" || { echo "MISSING: $host:$p expected open but isn't"; fail=1; };
     else
-      (echo > /dev/tcp/$host/$p) 2>/dev/null && echo "OK: $host:$p open" || { echo "MISSING: $host:$p expected open but isn't"; fail=1; };
+      (echo > "/dev/tcp/$host/$p") 2>/dev/null && echo "OK: $host:$p open" || { echo "MISSING: $host:$p expected open but isn't"; fail=1; };
     fi
   done;
   exit $fail

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wonsukchoi/crondex",
-  "version": "0.8.0",
+  "version": "0.9.1",
   "description": "A public directory of pre-made, agent-editable cron jobs.",
   "type": "module",
   "license": "MIT",
@@ -32,7 +32,8 @@
   },
   "scripts": {
     "build-catalog": "node scripts/build-catalog.js",
-    "validate": "node scripts/validate-jobs.js"
+    "validate": "node scripts/validate-jobs.js",
+    "lint-shell": "node scripts/lint-shell.js"
   },
   "devDependencies": {
     "ajv": "^8.17.1",