Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Create and manage scheduled bus arrival alerts using Korea TAGO (국토교통부) OpenAPI and Clawdbot cron. Use when a user wants to register weekday/weekend schedules like "평일 오전 7시, <정류소명>, <노선들>" and receive automatic arrival summaries via their configured Gateway messaging (DM only).
Create and manage scheduled bus arrival alerts using Korea TAGO (국토교통부) OpenAPI and Clawdbot cron. Use when a user wants to register weekday/weekend schedules like "평일 오전 7시, <정류소명>, <노선들>" and receive automatic arrival summaries via their configured Gateway messaging (DM only).
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Scheduled bus arrival alerts powered by 국토교통부 TAGO OpenAPI. This skill is designed for users running Clawdbot Gateway + Clawdbot cron. Users register rules like: "평일 오전 7시, 인천 한빛초등학교, 535" "평일 오후 5시30분, 고양 향동초등학교, 730, 503" Then the system sends arrival summaries to the registering user (DM) on schedule. Note (MVP): stop resolution is done via stop name search (cityCode + keyword). GPS-based nearby lookup exists but may return 0 results depending on key/region.
A running Clawdbot Gateway (Telegram/Slack/etc. already configured) Clawdbot cron enabled/usable A data.go.kr API key for TAGO (setup 자동화 사용 시) systemctl --user 가 동작하는 환경 (systemd user service) (rule_wizard에서 cron 등록까지 하려면) clawdbot CLI
You must set a TAGO service key in your environment (never commit or paste it into markdown). Recommended env var: TAGO_SERVICE_KEY
Good for quick manual tests; cron jobs will NOT inherit this unless the Gateway service has it. export TAGO_SERVICE_KEY='...'
This is the most “set it once and forget it” flow. Run: python3 korea-metropolitan-bus-alerts/scripts/setup.py If your network blocks the endpoint or TAGO returns 403 during the smoke test, you can still complete setup: python3 korea-metropolitan-bus-alerts/scripts/setup.py --skip-smoke It will: Auto-detect your Gateway systemd user service (supports custom unit names) Prompt for TAGO_SERVICE_KEY (hidden input) Save it to ~/.clawdbot/secrets/tago.env (chmod 600) Write a systemd override to load that env file Restart the Gateway Run a small TAGO smoke test (Advanced/manual) If you prefer shell scripts, korea-metropolitan-bus-alerts/scripts/set_tago_key.sh is still available, but setup.py is the recommended UX.
Never commit .env / tago.env. Avoid sharing outputs of docker compose config or similar commands that may print env values.
export TAGO_SERVICE_KEY='...' python3 korea-metropolitan-bus-alerts/scripts/tago_bus_alert.py nearby-stops --lat 37.5665 --long 126.9780
Tell the agent something like: "평일 07:00, 인천 한빛초등학교, 535 알림 등록해줘" If the stop name is ambiguous (e.g., opposite side of road), the agent MUST ask a follow-up question to pick the correct direction/stop candidate before creating the rule.
"버스 알림 목록 보여줘"
"버스 알림 3번 삭제해줘" (confirm before delete)
"방금 등록한 규칙 테스트해줘" (one-time message)
매일 HH:MM 평일 HH:MM 주말 HH:MM (Phase 2: arbitrary cron expressions)
Use isolated cron jobs (sessionTarget: isolated) + deliver: true. Delivery is DM-only to the registering user. See references/cron_recipe.md and scripts/cron_builder.py.
For integration testing (and for power users), use: scripts/rule_wizard.py register It will: Ask for schedule/time/routes Resolve stop candidates via GPS nearby lookup (direction disambiguation) Generate the job JSON Optionally call clawdbot cron add to register it
Single provider only (MVP): 정류장 조회: BusSttnInfoInqireService (15098534) 도착 조회: ArvlInfoInqireService (15098530)
Never write API keys/tokens/passwords into markdown files. For browser automation on logged-in pages: require explicit user confirmation. For destructive operations (cron delete): confirm before acting. DM-only delivery (MVP): do not broadcast to groups/channels.
Prefer scripts under scripts/ for deterministic behavior. Put detailed API field mappings in references/api_reference.md.
Use scripts/tago_bus_alert.py for deterministic TAGO lookups: nearby-stops (GPS → stop candidates) arrivals (cityCode+nodeId → arrivals; optional route filtering)
Code helpers, APIs, CLIs, browser automation, testing, and developer operations.
Largest current source with strong distribution and engagement signals.