Add repo conventions and cron documentation
This commit is contained in:
31
cron/capmetro-monitor.md
Normal file
31
cron/capmetro-monitor.md
Normal file
@@ -0,0 +1,31 @@
|
||||
# CapMetro Monitor
|
||||
|
||||
## Purpose
|
||||
|
||||
Watch for CapMetro service changes relevant to Ben's commute, especially Route 5 and MetroRail-related monitoring assets.
|
||||
|
||||
## Entrypoints
|
||||
|
||||
- Skill: `skills/capmetro-monitor/`
|
||||
- Primary monitor: `skills/capmetro-monitor/scripts/monitor.sh`
|
||||
- Change check: `skills/capmetro-monitor/scripts/check-changes.sh`
|
||||
- Route status helper: `skills/capmetro-monitor/scripts/route5-status.sh`
|
||||
- Additional watch scripts:
|
||||
- `skills/capmetro-monitor/scripts/watch-departure.sh`
|
||||
- `skills/capmetro-monitor/scripts/watch-departure-v2.sh`
|
||||
- `skills/capmetro-monitor/scripts/monitor-route5.js`
|
||||
|
||||
## Schedule
|
||||
|
||||
- Recurring
|
||||
- Exact active runtime schedule should be recorded here when finalized
|
||||
|
||||
## Expected behavior
|
||||
|
||||
- Checks for service changes and commute-relevant updates
|
||||
- Translates transit-operator language into plain English summaries
|
||||
- Supports route/status-specific helper workflows
|
||||
|
||||
## Notes
|
||||
|
||||
Prefer GTFS-driven or documented skill behavior over ad hoc scraping where possible. If the operational entrypoint changes, update this doc.
|
||||
Reference in New Issue
Block a user