# Telegram Traffic Reports

> Fetches and reports traffic conditions via Telegram bot format. Use for: telegram traffic, traffic report Telegram, commute alert, `waze-live-reports`.

- Skill: `stijnman/telegram-traffic-reports` (Agent Skill)
- Install (CLI): `npx skillmds@latest add stijnman/telegram-traffic-reports`
- Raw SKILL.md: https://api.skillmd.com/api/skills/stijnman/telegram-traffic-reports/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: Docs & Writing
- License: MIT
- Author: Stijnman (https://skillmd.com/u/stijnman)
- Updated: 2026-09-17
- Page: https://skillmd.com/skills/stijnman/telegram-traffic-reports

---

# Telegram Traffic Reports
## When to Use

- User says **telegram traffic** or task matches this capability
- User says **traffic report Telegram** or task matches this capability
- User says **commute alert** or task matches this capability

## Workflow

1. Get the user-approved location or route and clarify whether the request is for a draft, a one-time send, or a recurring alert.
2. Fetch traffic via waze-live-reports or traffic-flight-controller.
3. Format a concise Telegram message with delays and incidents; keep it as a draft by default.
4. Obtain explicit approval before sending to a named chat or enabling any recurring alert. Route scheduling through cron-scheduler only after its separate approval gate is satisfied.

## Integrations

- `waze-live-reports`
- `traffic-flight-controller`
- `cron-scheduler`
- `multi-platform-messenger-bridge`

## Error Handling

| Failure | Response |
|---------|----------|
| Location missing | Ask for origin/destination. |

## Gotchas

- Rate limit approved Telegram sends to 1/min per chat.
- Do not infer a recipient, enable a bot, or create a recurring alert from route data alone.

## Example

**Input:** User request matching triggers above.
**Output:** Structured result per workflow with integrations invoked as needed.