@wonsukchoi/crondex 0.10.0 → 0.11.0

package/README.md

@@ -36,6 +36,10 @@ npx @wonsukchoi/crondex add ssl-cert-expiry-check --dest ./cron/ssl-cert-expiry-
 - `add <id> [--dest path]` — copy it into your project to edit
 - `init <id> [--category x]` — scaffold a brand-new job from the template
 
+Add `--json` to `list`/`categories`/`show`/`recommend` for machine-readable
+output — useful when an agent is parsing the result programmatically
+instead of a human reading it.
+
 No install needed — `npx` always runs against the latest catalog. Prefer
 installing once? `npm install -g @wonsukchoi/crondex`, then drop the `npx`
 prefix (run `npm update -g` later to pick up new jobs). Prefer no npm at
@@ -87,7 +91,7 @@ tags, variables) use `crondex list`, `crondex recommend`, or browse
 `jobs/<category>/` directly.
 
 <!-- BEGIN JOB SUMMARY -->
-187 jobs across 37 categories:
+189 jobs across 37 categories:
 
 | category | jobs |
 |---|---|
@@ -113,7 +117,7 @@ tags, variables) use `crondex list`, `crondex recommend`, or browse
 | `inventory` | 3 |
 | `investing` | 3 |
 | `learning` | 5 |
-| `legal` | 3 |
+| `legal` | 4 |
 | `logistics` | 3 |
 | `manufacturing` | 3 |
 | `marketing` | 4 |
@@ -121,7 +125,7 @@ tags, variables) use `crondex list`, `crondex recommend`, or browse
 | `personal` | 9 |
 | `podcast` | 3 |
 | `productivity` | 9 |
-| `realestate` | 3 |
+| `realestate` | 4 |
 | `restaurant` | 3 |
 | `sales` | 5 |
 | `security` | 14 |
@@ -136,6 +140,7 @@ tags, variables) use `crondex list`, `crondex recommend`, or browse
 
 ```
 crondex/
+├── llms.txt               agent-discovery manifest (llms.txt convention)
 ├── bin/crondex.js         CLI: list / categories / show / add / recommend / init
 ├── lib/recommend.js       recommend's scoring logic (unit tested in test/)
 ├── catalog.json           generated index of every job — read this first

package/bin/crondex.js

@@ -2,6 +2,7 @@
 // CLI over catalog.json — browse jobs, read one, or pull one into your project.
 import { readFileSync, writeFileSync, existsSync } from "node:fs";
 import { join } from "node:path";
+import yaml from "js-yaml";
 import { tokenize, rankJobs } from "../lib/recommend.js";
 
 const ROOT = new URL("..", import.meta.url).pathname;
@@ -15,6 +16,14 @@ function flag(name) {
   return i === -1 ? undefined : args[i + 1];
 }
 
+function hasFlag(name) {
+  return args.includes(`--${name}`);
+}
+
+function printJson(value) {
+  console.log(JSON.stringify(value, null, 2));
+}
+
 function findJob(id) {
   const meta = CATALOG.jobs.find((j) => j.id === id);
   if (!meta) {
@@ -28,11 +37,11 @@ function printHelp() {
   console.log(`crondex — browse and pull pre-made cron jobs
 
 Usage:
-  crondex list [--category <name>] [--tag <name>]
-  crondex categories
-  crondex show <id>
+  crondex list [--category <name>] [--tag <name>] [--json]
+  crondex categories [--json]
+  crondex show <id> [--json]
   crondex add <id> [--dest <path>]
-  crondex recommend "<what you want done>" [--limit <n>]
+  crondex recommend "<what you want done>" [--limit <n>] [--json]
   crondex init <id> [--category <name>] [--dest <path>]
 
 Examples:
@@ -42,20 +51,39 @@ Examples:
   crondex add backup-reminder --dest ./cron/backup-reminder.yaml
   crondex recommend "warn me before my SSL cert expires"
   crondex init ssl-cert-expiry-check --category security
+
+Add --json to list/categories/show/recommend for machine-readable output —
+useful when an agent is parsing crondex's output programmatically instead
+of a human reading it.
 `);
 }
 
 function recommend(queryText) {
   const limit = Number(flag("limit")) || 5;
+  const json = hasFlag("json");
   if (!tokenize(queryText).length) {
+    if (json) return printJson([]);
     console.log("query too vague to match on — describe what you want the job to check or remind you about.");
     return;
   }
   const ranked = rankJobs(CATALOG.jobs, queryText, limit);
   if (!ranked.length) {
+    if (json) return printJson([]);
     console.log(`no confident match for "${queryText}". Run "crondex list" to browse everything.`);
     return;
   }
+  if (json) {
+    return printJson(
+      ranked.map((r) => ({
+        id: r.job.id,
+        category: r.job.category,
+        score: r.score,
+        matched_terms: r.matchedTerms,
+        modes: r.job.modes,
+        description: r.job.description,
+      }))
+    );
+  }
   console.log(`top match${ranked.length > 1 ? "es" : ""} for "${queryText}":`);
   console.log();
   for (const r of ranked) {
@@ -77,9 +105,11 @@ function catalogInfoLine() {
 function list() {
   const category = flag("category");
   const tag = flag("tag");
+  const json = hasFlag("json");
   const jobs = CATALOG.jobs.filter(
     (j) => (!category || j.category === category) && (!tag || j.tags.includes(tag))
   );
+  if (json) return printJson(jobs);
   console.log(catalogInfoLine());
   console.log();
   if (!jobs.length) {
@@ -94,15 +124,20 @@ function list() {
 }
 
 function show(id) {
-  console.log(readFileSync(join(ROOT, findJob(id).path), "utf8"));
+  const meta = findJob(id);
+  const raw = readFileSync(join(ROOT, meta.path), "utf8");
+  if (hasFlag("json")) return printJson(yaml.load(raw));
+  console.log(raw);
 }
 
 function categories() {
   const counts = {};
   for (const j of CATALOG.jobs) counts[j.category] = (counts[j.category] ?? 0) + 1;
+  const sorted = Object.entries(counts).sort(([a], [b]) => a.localeCompare(b));
+  if (hasFlag("json")) return printJson(sorted.map(([category, count]) => ({ category, count })));
   console.log(catalogInfoLine());
   console.log();
-  for (const [cat, n] of Object.entries(counts).sort(([a], [b]) => a.localeCompare(b))) {
+  for (const [cat, n] of sorted) {
     console.log(`${cat}  (${n})`);
   }
 }

package/catalog.json

@@ -1,7 +1,7 @@
 {
   "generated_by": "scripts/build-catalog.js",
   "schema": "schema/job.schema.json",
-  "count": 187,
+  "count": 189,
   "jobs": [
     {
       "id": "1on1-prep-reminder",
@@ -809,6 +809,31 @@
       ],
       "path": "jobs/learning/course-progress-checkin.yaml"
     },
+    {
+      "id": "court-deadline-reminder",
+      "version": 1,
+      "name": "Court Deadline Reminder",
+      "description": "Checks a tracked list of court/filing deadlines and warns before any come due. Use this if a filing deadline has ever been missed because it lived only in one person's head or a sticky note instead of a shared, checked calendar.",
+      "category": "legal",
+      "tags": [
+        "legal",
+        "court",
+        "deadline",
+        "compliance"
+      ],
+      "schedule": "0 7 * * *",
+      "timezone": "UTC",
+      "runner": "shell",
+      "modes": [
+        "script"
+      ],
+      "compatible_agents": [
+        "generic",
+        "claude",
+        "codex"
+      ],
+      "path": "jobs/legal/court-deadline-reminder.yaml"
+    },
     {
       "id": "coverage-gap-audit",
       "version": 1,
@@ -2385,12 +2410,12 @@
       "id": "low-stock-alert",
       "version": 1,
       "name": "Low Stock Alert",
-      "description": "Checks inventory levels against a reorder point and flags SKUs running low. Use this if you've ever gone out of stock on a bestseller because nobody was watching the count.",
+      "description": "Checks a general-purpose inventory database (warehouse, retail backroom, restaurant supplies — anything with a quantity and a set reorder point) against that fixed threshold and flags what's running low. Use this for physical stock tracked in a database, not tied to online sales; if you specifically need SKU reorder timing driven by e-commerce sales velocity and supplier lead time, see `low-stock-reorder-alert` instead.",
       "category": "inventory",
       "tags": [
         "inventory",
         "stock",
-        "ecommerce"
+        "warehouse"
       ],
       "schedule": "0 7 * * *",
       "timezone": "UTC",
@@ -3032,6 +3057,31 @@
       ],
       "path": "jobs/manufacturing/production-line-downtime-watch.yaml"
     },
+    {
+      "id": "property-maintenance-inspection-reminder",
+      "version": 1,
+      "name": "Property Maintenance Inspection Reminder",
+      "description": "Tracks when each property was last inspected and flags any that are due for their next routine walkthrough. Use this if a property has ever gone a year or more without a proper inspection because nothing forced anyone to schedule one.",
+      "category": "realestate",
+      "tags": [
+        "realestate",
+        "maintenance",
+        "inspection",
+        "property"
+      ],
+      "schedule": "0 8 * * 1",
+      "timezone": "UTC",
+      "runner": "shell",
+      "modes": [
+        "script"
+      ],
+      "compatible_agents": [
+        "generic",
+        "claude",
+        "codex"
+      ],
+      "path": "jobs/realestate/property-maintenance-inspection-reminder.yaml"
+    },
     {
       "id": "pto-balance-check",
       "version": 1,

package/jobs/inventory/low-stock-alert.yaml

@@ -2,11 +2,14 @@ id: low-stock-alert
 version: 1
 name: Low Stock Alert
 description: >
-  Checks inventory levels against a reorder point and flags SKUs running
-  low. Use this if you've ever gone out of stock on a bestseller because
-  nobody was watching the count.
+  Checks a general-purpose inventory database (warehouse, retail backroom,
+  restaurant supplies — anything with a quantity and a set reorder point)
+  against that fixed threshold and flags what's running low. Use this for
+  physical stock tracked in a database, not tied to online sales; if you
+  specifically need SKU reorder timing driven by e-commerce sales velocity
+  and supplier lead time, see `low-stock-reorder-alert` instead.
 category: inventory
-tags: [inventory, stock, ecommerce]
+tags: [inventory, stock, warehouse]
 schedule: "0 7 * * *"
 timezone: "UTC"
 runner: shell

package/jobs/legal/court-deadline-reminder.yaml

@@ -0,0 +1,40 @@
+id: court-deadline-reminder
+version: 1
+name: Court Deadline Reminder
+description: >
+  Checks a tracked list of court/filing deadlines and warns before any come
+  due. Use this if a filing deadline has ever been missed because it lived
+  only in one person's head or a sticky note instead of a shared, checked
+  calendar.
+category: legal
+tags: [legal, court, deadline, compliance]
+schedule: "0 7 * * *"
+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 && diff_days >= 0) {
+        printf "DUE SOON: %s — %s due %s (%d days)\n", $1, $2, $3, diff_days;
+      }
+    }
+  ' "{{deadlines_csv_path}}"
+variables:
+  deadlines_csv_path:
+    default: "./court-deadlines.csv"
+    description: "Path to a CSV with columns: matter_name,deadline_type,due_date (YYYY-MM-DD) — e.g. one row per filing/response/statute-of-limitations deadline."
+  warn_days_before:
+    default: 14
+    description: How many days before a deadline to start warning.
+compatible_agents: [generic, claude, codex]
+notes: >
+  This is a plain date-threshold check, not a rules-based calendaring
+  engine — it won't calculate deadlines from court rules the way dedicated
+  legal calendaring software does. Export computed due dates from that
+  system into the CSV, or maintain them manually, and use this as the
+  "did anyone actually notice" backstop.

package/jobs/realestate/property-maintenance-inspection-reminder.yaml

@@ -0,0 +1,35 @@
+id: property-maintenance-inspection-reminder
+version: 1
+name: Property Maintenance Inspection Reminder
+description: >
+  Tracks when each property was last inspected and flags any that are due
+  for their next routine walkthrough. Use this if a property has ever gone
+  a year or more without a proper inspection because nothing forced anyone
+  to schedule one.
+category: realestate
+tags: [realestate, maintenance, inspection, property]
+schedule: "0 8 * * 1"
+timezone: "UTC"
+runner: shell
+command: >
+  awk -F',' -v days="{{inspection_interval_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 last_epoch; close(cmd);
+      "date +%s" | getline now_epoch; close("date +%s");
+      days_since = (now_epoch - last_epoch) / 86400;
+      if (days_since >= days) {
+        printf "DUE: %s — last inspected %s (%d days ago)\n", $1, $2, days_since;
+      }
+    }
+  ' "{{properties_csv_path}}"
+variables:
+  properties_csv_path:
+    default: "./property-inspections.csv"
+    description: "Path to a CSV with columns: property_name,last_inspection_date (YYYY-MM-DD)."
+  inspection_interval_days:
+    default: 180
+    description: How often each property should be inspected, in days.
+compatible_agents: [generic, claude, codex]
+notes: Assumes a maintained CSV of last-inspection dates per property — export it from whatever property management system you use, or update it manually after each walkthrough.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@wonsukchoi/crondex",
-  "version": "0.10.0",
+  "version": "0.11.0",
   "description": "A public directory of pre-made, agent-editable cron jobs.",
   "type": "module",
   "license": "MIT",
@@ -35,10 +35,13 @@
     "build-catalog": "node scripts/build-catalog.js",
     "validate": "node scripts/validate-jobs.js",
     "lint-shell": "node scripts/lint-shell.js",
+    "check-duplicates": "node scripts/check-duplicates.js",
     "test": "node --test"
   },
-  "devDependencies": {
-    "ajv": "^8.17.1",
+  "dependencies": {
     "js-yaml": "^4.1.0"
+  },
+  "devDependencies": {
+    "ajv": "^8.17.1"
   }
 }