OpenClaw

tfl-journey-disruption

Plan TfL journeys from start/end/time, resolve locations (prefer postcodes), and warn about disruptions; suggest alternatives when disrupted.

diegopetrucci0 来源安装数☆ 0 仓库 Stars

查看来源 ↗安装与使用 SKILL.md ↗

安装与使用

请根据来源仓库和你的 AI 工具说明安装此技能。先阅读技能文件和依赖要求，再添加到工作流。

SkillHub CLI

skillhub install diegopetrucci/transport-for-london-journey-disruption

打开来源仓库，查看说明和兼容环境后，按来源提供的命令或步骤安装。

将来源链接提供给你的 Agent，让它先读取说明、核对依赖，并向你说明将执行的安装步骤。

查看来源 ↗使用指南

技能说明

TfL Journey Planner + Disruption Checks

Use this skill when the user wants a TfL journey plan and needs disruption awareness.

Reference: https://tfl.gov.uk/info-for/open-data-users/api-documentation

Script helper

Use scripts/tfl_journey_disruptions.py for a quick journey + disruption check.

Examples:

python3 scripts/tfl_journey_disruptions.py \"940GZZLUSTD\" \"W1F 9LD\" --depart-at 0900
python3 scripts/tfl_journey_disruptions.py --from \"Stratford\" --to \"W1F 9LD\" --arrive-by 1800

Notes:

If the API returns disambiguation options, pick one and retry with its parameterValue.
If you have TfL API keys, set TFL_APP_ID and TFL_APP_KEY in the environment.

Inputs to collect

From: postcode, stop/station name, place name, or lat,lon
To: postcode, stop/station name, place name, or lat,lon
Time + intent: depart at or arrive by (and date if not explicit)
Optional: mode or accessibility constraints if the user mentions them

If any of these are missing or ambiguous, ask the user for clarification.

Resolve locations

Prefer postcodes when available. Otherwise, resolve place names and stations:

If input looks like a UK postcode, use it directly as {from} or {to}.
If input is lat,lon, use as-is.
If input is a stop or station name, try StopPoint/Search/{query} and choose a hub or the relevant NaPTAN ID.
If the search or journey result returns disambiguation, show the top options (common name + parameterValue) and ask the user to pick.
When unsure, ask a clarifying question rather than guessing.

Plan journeys

Call:

/Journey/JourneyResults/{from}/to/{to}?date=YYYYMMDD&time=HHMM&timeIs=Depart|Arrive

Guidelines:

If the user says "arrive by" use timeIs=Arrive; otherwise default to Depart.
If the date is not provided, ask. If the user implies "now", you can omit date/time.

Extract candidate routes

From the response, take the first 1-3 journeys. For each, capture:

Duration and arrival time
Publ...

来源信息

Source: github
Repository: openclaw/skills
Path: skills/diegopetrucci/transport-for-london-journey-disruption
Version: —
Commit: 39787898face1fb6bc422498d6d77dfd93085640
分类来源: rules
状态: active
可见性: public

这些信息来自收录时的来源分析，可能滞后；使用前请核对最新来源文件。

来源内容

SKILL.md

# TfL Journey Planner + Disruption Checks

Use this skill when the user wants a TfL journey plan and needs disruption awareness.

Reference: https://tfl.gov.uk/info-for/open-data-users/api-documentation

## Script helper

Use `scripts/tfl_journey_disruptions.py` for a quick journey + disruption check.

Examples:

```bash
python3 scripts/tfl_journey_disruptions.py \"940GZZLUSTD\" \"W1F 9LD\" --depart-at 0900
python3 scripts/tfl_journey_disruptions.py --from \"Stratford\" --to \"W1F 9LD\" --arrive-by 1800
```

Notes:
- If the API returns disambiguation options, pick one and retry with its `parameterValue`.
- If you have TfL API keys, set `TFL_APP_ID` and `TFL_APP_KEY` in the environment.

## Inputs to collect

- From: postcode, stop/station name, place name, or lat,lon
- To: postcode, stop/station name, place name, or lat,lon
- Time + intent: depart at or arrive by (and date if not explicit)
- Optional: mode or accessibility constraints if the user mentions them

If any of these are missing or ambiguous, ask the user for clarification.

## Resolve locations

Prefer postcodes when available. Otherwise, resolve place names and stations:

- If input looks like a UK postcode, use it directly as `{from}` or `{to}`.
- If input is lat,lon, use as-is.
- If input is a stop or station name, try `StopPoint/Search/{query}` and choose a hub or the relevant NaPTAN ID.
- If the search or journey result returns disambiguation, show the top options (common name + parameterValue) and ask the user to pick.
- When unsure, ask a clarifying question rather than guessing.

## Plan journeys

Call:

`/Journey/JourneyResults/{from}/to/{to}?date=YYYYMMDD&time=HHMM&timeIs=Depart|Arrive`

Guidelines:
- If the user says "arrive by" use `timeIs=Arrive`; otherwise default to `Depart`.
- If the date is not provided, ask. If the user implies "now", you can omit date/time.

## Extract candidate routes

From the response, take the first 1-3 journeys. For each, capture:
- Duration and arrival time
- Publ...

搜索