← Back to Skills Marketplace
192
Downloads
1
Stars
0
Active Installs
3
Versions
Install in OpenClaw
/install tfl-cli
Description
London transport CLI — tube status, journey planning, live arrivals, disruptions, bike docks, and agent-friendly projection via `--output <path>` for route,...
Usage Guidance
This skill appears to be a straightforward wrapper around an npm-distributed TfL CLI and is coherent with its description. Before installing: (1) verify the npm package and author (npmjs.com/package/@shan8851/tfl-cli and the package's repository/homepage) so you trust the maintainers; (2) prefer installing in a sandbox/container or review the package contents if you require higher assurance (npm packages can execute arbitrary code during postinstall); (3) be aware the SKILL.md mentions an optional TFL_APP_KEY—only set that env var if you trust the package and the key itself; (4) because this is instruction-only, the static scanner had no package code to analyze—inspect the published npm package or its repo if you need stronger guarantees.
Capability Analysis
Type: OpenClaw Skill
Name: tfl-cli
Version: 0.3.1
The skill bundle provides a CLI interface for London transport data (TfL) via the npm package `@shan8851/tfl-cli`. The instructions in SKILL.md are purely functional, detailing how to query tube status, plan routes, and check live arrivals. There are no indicators of data exfiltration, malicious execution, or harmful prompt injection.
Capability Assessment
Purpose & Capability
The name/description (London transport CLI) match the declared binary requirement ('tfl') and the install spec (npm package @shan8851/tfl-cli that creates the 'tfl' binary). There are no unrelated environment variables, credentials, or config paths required.
Instruction Scope
SKILL.md only describes how to use the tfl CLI (status, route, arrivals, bikes, search, output projection). It does not instruct the agent to read unrelated files, system config, or to transmit data to arbitrary endpoints. It does mention an optional TFL_APP_KEY environment variable for higher rate limits, which is expected for a TfL client.
Install Mechanism
Installation is via an npm package (@shan8851/tfl-cli) that provides the 'tfl' binary — this is a typical and expected mechanism. npm packages can contain arbitrary code, so installing from the public registry carries the usual moderate risk compared with instruction-only skills; however, no suspicious download URLs or archive extraction from unknown hosts are present.
Credentials
The skill declares no required env vars (none listed), which fits basic usage. SKILL.md mentions an optional TFL_APP_KEY for higher rate limits; that optional variable is reasonable but is not listed in the metadata as an optional env var—minor documentation mismatch. The skill does not request unrelated secrets or multiple credentials.
Persistence & Privilege
Defaults are used (always: false, user-invocable true). The skill does not request persistent presence or modify other skills or system-wide settings. Autonomous invocation is allowed (platform default) but is not combined with other red flags.
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install tfl-cli - After installation, invoke the skill by name or use
/tfl-cli - Provide required inputs per the skill's parameter spec and get structured output
Version History
v0.3.1
Publish from ~/.openclaw/skills as source of truth; keep OpenClaw metadata and updated --output projection guidance.
v0.3.0
**tfl-cli 0.3.0 adds agent-friendly projection for core commands**
- New `--output <path>` option on `route`, `arrivals`, and `bikes` commands to extract specific values or subtrees from JSON output
- Documentation updated with projection usage examples and agent notes for integration scenarios
- Clarified descriptions and command summaries for greater clarity
- Improved explanation of output modes, error envelopes, and exit codes
v0.2.0
tfl-cli 0.2.0
- Adds live tube status, disruption alerts, journey planning, and arrivals for London transport via the CLI.
- Supports querying bike dock availability and searching for stops/stations.
- Flexible input: accepts station names, postcodes, coordinates, or TfL stop IDs.
- Commands return text by default (JSON when piped), with options to force output format or disable color.
- No API key required for basic use; supports higher rate limits with TFL_APP_KEY.
- Includes clear error handling and exit codes, with ambiguity suggestions for station names.
Metadata
Frequently Asked Questions
What is tfl-cli?
London transport CLI — tube status, journey planning, live arrivals, disruptions, bike docks, and agent-friendly projection via `--output <path>` for route,... It is an AI Agent Skill for Claude Code / OpenClaw, with 192 downloads so far.
How do I install tfl-cli?
Run "/install tfl-cli" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is tfl-cli free?
Yes, tfl-cli is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does tfl-cli support?
tfl-cli is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created tfl-cli?
It is built and maintained by shan8851 (@shan8851); the current version is v0.3.1.
More Skills