← RailJournal IndiaCONTENT HISTORY
WHAT CHANGED
Update to RailJournal India
Snapshot Oct 25, 2026 · 12:05 UTC · version 1.0.1
Collection source: downloaded plugin package.
First saved snapshot
No earlier snapshot is available to establish a change.
Save RailJournal India and check future changes in Following.
Up to 10 plugins free · no card required.
Compare saved observations
Download comparison JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Check the reported running status of an Indian train for a given origin departure date, such as delay and last known location. Use when the user asks where a train is, whether it is late, or how it is running.",
"included_files": [],
"name": "train-status",
"skill_md_contents": "---\nname: train-status\ndescription: Check the reported running status of an Indian train for a given origin departure date, such as delay and last known location. Use when the user asks where a train is, whether it is late, or how it is running.\n---\n\n# Train running status\n\n1. Make sure you have a train number. If the user gave a name, resolve it first with `search_trains` and confirm the match.\n2. Ask for, or infer from context, the date the train departed from its origin (YYYY-MM-DD, Asia/Kolkata). Today's date is fine only if the user means a train that left its origin today.\n3. Call `get_train_running_status` with the train number and `origin_departure_date`.\n4. Summarise the current position, delay and next stops. Starred times are estimates; say so.\n\nImportant:\n- The tool reads RailJournal's existing website cache and does not start a live refresh. A cache miss returns an error. Tell the user the status is not available right now and suggest trying again shortly. Do not retry in a loop and do not invent a status.\n- Retrieval time is not observation time. Mention when the data was retrieved.\n- Include the source link from the result.\n"
}SHA-256 of public snapshot: 9c06c006df7a5d36a4268b857773590895ca1805c78029d01a1db80f402b196e