Srbijavoz

Check Current Notices

Run the bundled script first:

python3 scripts/srbvoz_scraper.py --limit 20

Filter notices when the user mentions a specific issue:

python3 scripts/srbvoz_scraper.py --query "kašnjenje" --limit 20
python3 scripts/srbvoz_scraper.py --query "Petrovaradin" --limit 20

The output JSON is the source of truth for current notices. Use notice title, content, date, and link in the final answer.

Resolve Station Names

When the user gives a partial station name, call the station endpoint through the same script:

python3 scripts/srbvoz_scraper.py --station "Beograd"

Return the best matching station names and codes. Do not guess station names without checking the API first.

Inspect Timetable Metadata

When the user asks whether something is a timetable artifact rather than a fresh notice, inspect the timetable page metadata:

python3 scripts/srbvoz_scraper.py --timetable-info
python3 scripts/srbvoz_scraper.py --station "Novi Sad" --timetable-info

Use this only to support interpretation. Prefer live notices over timetable-page hints.

Classify the Result

Scan notice titles and bodies for disruption cues. Read references/keyword-cues.md when you need the full cue list.

Classify each relevant result as one of:

• delay
• stopped
• canceled
• operational_change
• replacement_bus_service
• no_disruption_found

On the Novi Sad - Petrovaradin corridor, treat recurring bus-service notices as timetable information unless the notice explicitly says service changed, stopped, or was canceled.

Answer Format

Default to a short, rider-friendly summary.

Lead with the practical answer in plain language, for example:

• No current issue found for Novi Sad -> Beograd.
• There is an issue on Novi Sad -> Beograd this morning.
• Only a recurring bus-transfer notice is present, no fresh disruption found.

Then include only the useful operational details:

• whether there is a current issue or not
• affected route / train / departure times if known
• whether it looks current today, ongoing, or just a recurring timetable arrangement
• what the passenger should do, if obvious, for example use replacement bus, expect delay, or check the next departure

Do not include classifier jargon like disruption type unless the user asks for it. Do not quote trigger phrases or explain the internal classification unless the user asks. Mention live notice versus recurring timetable notice only when it helps disambiguate whether the issue is fresh.

If nothing relevant appears, say that no matching current notice was found.

Handle Failures

• If the API request fails, the script can fall back to the public timetable page unless --no-fallback is set.
• If both API and fallback fail, say that the official public endpoints were unavailable at lookup time.
• If the user asks for exact timetable calculations, explain that this skill only checks public notices, station lookup, and timetable metadata.

Tips

• Prefer route-specific queries like Petrovaradin, Beograd centar, or Novi Sad over generic searches.
• Quote the exact Serbian phrase that triggered the classification instead of paraphrasing the whole notice.
• A recurring bus notice on the Petrovaradin corridor is not enough by itself to claim a fresh disruption.
• Use --station before answering ambiguous station-name questions.
• Use --timetable-info only as supporting evidence, not as the primary source when live notices exist.
• Keep the final answer short and operational: what happened, where, and whether it appears current.