Files

b3nw 3b7d6bb67c Initial commit: custom OpenClaw skills from docker-test

- workspace: capmetro-monitor, github-notifications, model-selector
- workspace-security: vt-monitor, monitor-unauthorized
- workspace-home: cron-manager, monitor-unauthorized
- extensions: vt-sentinel (VT-Sentinel plugin)

Includes sync.sh for pull/push, README, AGENTS.md, .gitignore.

2026-02-16 15:32:44 +00:00

1.6 KiB

Raw Permalink Blame History

name, description

name	description
capmetro-monitor	Monitor CapMetro (Austin, TX) service changes for specific routes. Checks tri-annual service change pages for Route 5 (Bus) and Route 500 (MetroRail), translates transit operator language into plain English summaries. Use for weekly monitoring of commute-relevant transit updates.

CapMetro Service Change Monitor

Weekly monitoring of Austin transit route changes with plain-English summaries.

What It Does

Checks CapMetro service change pages (tri-annual: Jan, Jun, Aug)
Filters for Route 5 (Bus) and Route 500 (MetroRail)
Detects new changes since last check
Returns structured JSON for processing

Monitored Routes

Route 5 - Woodrow/East 12th (Bus)
Route 500 - MetroRail (Red Line)

Usage

bash skills/capmetro-monitor/scripts/check-changes.sh

Output when nothing new:

{"hasNew":false}

Output with new changes:

{
  "hasNew": true,
  "newChanges": [
    {
      "url": "https://www.capmetro.org/servicechange/june-2026",
      "title": "June 2026 Proposed Service Changes",
      "id": "https://www.capmetro.org/servicechange/june-2026"
    }
  ]
}

Integration

Designed for weekly cron job that:

Runs check script
If hasNew: true, fetch full details and summarize in plain English
Translate transit terminology (timepoint, alignment, turnaround) for clarity

State Tracking

State stored in memory/capmetro-check-state.json:

{
  "lastCheck": "2026-02-04T17:30:00Z",
  "seenChanges": ["url1", "url2"]
}

Requirements

curl for web requests
jq for JSON processing

1.6 KiB Raw Permalink Blame History