SKILLEMALL.ai

BC TomTom Traffic Commute

Get real-time commute traffic using TomTom Routing API. Live travel times, delays, and ETAs.

ClawHub Agent Skills author: vijays365 v1.0.0 MIT-0 5 files · 2 scripts body ≈ 471 tokens Open the sourceclawhub.ai analyzed 36 h ago

Get real-time commute traffic using TomTom Routing API.

As a process C 57/100 · Has gaps — weak spots: when it triggers, inputs and preconditions, failures and branches

IntegrationAI and agentsWriting and documentstype and topics are labelled automatically from the skill text
JSON
Technical rating
B
87/100
safety, quality, tests
Safety 60%
99
Quality 40%
69
Run on models
none yet
Process rating
C
57/100
Has gaps
Inputs and preconditions w 11
0
Failures and branches w 10
0
Progress reporting w 2
0
the three weakest of ten parameters · all ten

How to improve

  1. Say in the description WHEN to use the skill ("use when…", example requests): that is the agent's main cue.
For the model run — optional
  • Your own cases (evals/evals.json, 4–6 real requests with expected answers): the full check would then run those instead of a model-drafted suite.
  • A spec.yaml with trigger phrases and assertions — a behaviour contract for CI; `skilltest init` writes a template.

Guard findings · 1

✓ No critical or high findings

Medium and low: 1
  • low Exfiltration exfil-secret-in-url scripts/tomtom-traffic.sh:39
    Credential passed in a URL query string (normal for some APIs — verify the host is the intended service) (placeholder value)
    URL="https://api.tomtom.com/routing/1/calculateRoute/${ORIGIN}:${DEST}/json?key=…&traffic=true&routeType=…"
    placeholder

Files scanned: 5. Evidence is masked. Grey chips explain why severity was lowered.

Against the Agent Skills spec

  • warning name-format name should be kebab-case (lowercase letters, digits, hyphens)
  • warning description-no-when description does not say WHEN to use the skill (no "use when")
  • note frontmatter-key unknown frontmatter key "slug"

Process rating: all ten parameters 57/100

  • 0Inputs and preconditions. Does not say what the process needs to start
  • 0Failures and branches. Linear process with no failure handling
  • 0Progress reporting. Says nothing while it works
  • 20When it triggers. No condition that starts the skill
  • 40Consistency. Frontmatter name (TomTom Traffic Commute) differs from the folder (tomtom-traffic-commute)
  • 60Result and completion. Output format stated, no completion criterion
  • 100Tools and files. No external tools needed
  • 100Steps. 8 steps
  • 100Execution cost. Instruction body is 471 tokens
  • 100Running it twice. No mutating operations

Everything here is measured from the skill text rather than judged by a model, so the numbers are checkable. A parameter weighs more when it is a more common reason for the process to stall.

Quality signals

  • +5Description has no quoted example phrases that should trigger the skill
  • +4Description does not say when NOT to use the skill (false activations)
  • +3Description length 92: 120–800 characters recommended
  • +1No license
  • +2Single-language instructions
  • +4Structure: 10 headings
  • +3Step-by-step instructions: 8 items
  • +3Output format is stated explicitly
  • +4Has examples (4 code blocks)
  • +3All 1 scripts are documented

Quality base 70; lint remarks subtract, signals add up to 100. Result: 69.

External checks

ClawHub: suspicious
The skill is mostly a legitimate TomTom commute helper, but it needs Review because its shell scripts can execute unintended local Python code if crafted input values are used.
LLM: suspicious (high) · VirusTotal: · 10 Jun 2026