68 lines
1.6 KiB
Markdown
68 lines
1.6 KiB
Markdown
---
|
|
name: capmetro-monitor
|
|
description: 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
|
|
|
|
1. Checks CapMetro service change pages (tri-annual: Jan, Jun, Aug)
|
|
2. Filters for Route 5 (Bus) and Route 500 (MetroRail)
|
|
3. Detects new changes since last check
|
|
4. Returns structured JSON for processing
|
|
|
|
## Monitored Routes
|
|
|
|
- **Route 5** - Woodrow/East 12th (Bus)
|
|
- **Route 500** - MetroRail (Red Line)
|
|
|
|
## Usage
|
|
|
|
```bash
|
|
bash skills/capmetro-monitor/scripts/check-changes.sh
|
|
```
|
|
|
|
**Output when nothing new:**
|
|
```json
|
|
{"hasNew":false}
|
|
```
|
|
|
|
**Output with new changes:**
|
|
```json
|
|
{
|
|
"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:
|
|
1. Runs check script
|
|
2. If `hasNew: true`, fetch full details and summarize in plain English
|
|
3. Translate transit terminology (timepoint, alignment, turnaround) for clarity
|
|
|
|
## State Tracking
|
|
|
|
State stored in `memory/capmetro-check-state.json`:
|
|
```json
|
|
{
|
|
"lastCheck": "2026-02-04T17:30:00Z",
|
|
"seenChanges": ["url1", "url2"]
|
|
}
|
|
```
|
|
|
|
## Requirements
|
|
|
|
- `curl` for web requests
|
|
- `jq` for JSON processing
|