Requirements
- Target platform
- OpenClaw
- Install method
- Manual import
- Extraction
- Extract archive
- Prerequisites
- OpenClaw
- Primary doc
- SKILL.md
Tencent SkillHub · Communication & Collaboration
Commute Traffic
Check real-time traffic conditions for a route between two locations using TomTom. Use when the user asks about traffic, commute time, best time to leave, dr...
skill openclawclawhub Free
Check real-time traffic conditions for a route between two locations using TomTom. Use when the user asks about traffic, commute time, best time to leave, dr...
⬇ 0 downloads ★ 0 stars Unverified but indexed
Install for OpenClaw
Quick setup
- Download the package from Yavira.
- Extract the archive and review SKILL.md first.
- Import or place the package into your OpenClaw setup.
Package facts
- Download mode
- Yavira redirect
- Package format
- ZIP package
- Source platform
- Tencent SkillHub
- What's included
- INSTALL.md, SKILL.md, references/tomtom-api-response.md, scripts/check_traffic.py
Validation
- Use the Yavira download entry.
- Review SKILL.md after the package is downloaded.
- Confirm the extracted package contains the expected setup assets.
Install with your agent
Agent handoff
Hand the extracted package to your coding agent with a concrete install brief instead of figuring it out manually.
- Download the package from Yavira.
- Extract it into a folder your agent can access.
- Paste one of the prompts below and point your agent at the extracted folder.
New install
I downloaded a skill package from Yavira. Read SKILL.md from the extracted folder and install it by following the included instructions. Tell me what you changed and call out any manual steps you could not complete.
Upgrade existing
I downloaded an updated skill package from Yavira. Read SKILL.md from the extracted folder, compare it with my current installation, and upgrade it while preserving any custom configuration unless the package docs explicitly say otherwise. Summarize what changed and any follow-up checks I should run.
Trust & source
Release facts
- Source
- Tencent SkillHub
- Verification
- Indexed source record
- Version
- 0.1.0
Provenance
- Publisher
- Xavjer
- Source page
- View original listing
- Canonical URL
- Open canonical page
Documentation
Purpose
Query real-time traffic data from TomTom for any route and provide the user with actionable travel advice. The script handles geocoding (resolving place names to coordinates) and routing (calculating travel time with live traffic) — all via the same TomTom API key.
Determining Origin and Destination
The origin and destination are not static — you must determine them from what the user tells you. Examples: "How's traffic from the office to home?" → You must know (or ask) where their office and home are. "Check traffic Basel to Zurich" → origin=Basel, destination=Zurich. "Should I leave now?" → Use previously discussed or known origin/destination. If unknown, ask. "What's the commute like?" → If you know the user's regular commute, use that. Otherwise, ask. Rules: If both origin and destination are clear from context, proceed immediately. If only one is clear, ask for the missing one. If neither is clear and you have no prior context, ask the user for both. Accept any format: addresses, city names, landmarks, coordinates — the script geocodes automatically.
Running the Traffic Check
Execute the script with origin and destination as arguments: python3 {baseDir}/scripts/check_traffic.py --origin "<ORIGIN>" --destination "<DESTINATION>" Examples: python3 {baseDir}/scripts/check_traffic.py --origin "Basel, Switzerland" --destination "Zurich, Switzerland" python3 {baseDir}/scripts/check_traffic.py --origin "Basel SBB" --destination "Paradeplatz, Zürich" python3 {baseDir}/scripts/check_traffic.py --origin "Aeschenplatz, Basel" --destination "ETH Zürich"
Interpreting the Output
The script returns JSON with one or more route alternatives. For each route: FieldMeaningtravel_time_minTotal travel time with current live trafficno_traffic_time_minTravel time with zero traffic (free-flow)historic_traffic_time_minTypical travel time based on historical patternslive_traffic_time_minTime including live incident datatraffic_delay_minExtra delay caused by current traffictraffic_delay_pctDelay as percentage of free-flow timecongestionDerived level: light, moderate, or heavydistance_kmRoute distance in kilometersdeparture_time / arrival_timeDeparture and estimated arrival timestamps
Congestion classification:
Light: traffic delay adds less than 20% to free-flow time Moderate: 20–50% above free-flow Heavy: more than 50% above free-flow
Presenting Results to the User
When presenting traffic data, always include: The fastest route and its estimated travel time. Traffic delay in plain language (e.g., "Currently 8 minutes delay due to traffic on the A2, adding about 15% to the normal drive time"). Comparison of alternatives if multiple routes are returned. A recommendation: whether to leave now or wait, based on congestion level. Keep it concise and practical. The user wants to know: "How long will it take and should I go now?"
Error Handling
If the script returns {"status": "error"}, relay the error message to the user. If TOMTOM_API_KEY is not configured, tell the user to set it up in ~/.openclaw/openclaw.json. If geocoding fails (no coordinates found), the location may be too vague — ask the user to be more specific. If no routes are returned, suggest trying different location descriptions.
Category context
Messaging, meetings, inboxes, CRM, and teammate communication surfaces.
Source: Tencent SkillHub
Largest current source with strong distribution and engagement signals.
Package contents
Included in package
3 Docs1 Scripts
- SKILL.md
- INSTALL.md
- references/tomtom-api-response.md
- scripts/check_traffic.py