agentsclimarketplace

Telemetry

Skill dacrypt/tesla-claude-plugin/skills/telemetry

Tesla plugin for Claude Code — control your Tesla with natural language. 9 skills: status, charging, vehicle control, order tracking, analytics, and a self-hosted web dashboard.

Install
npx -y skills add dacrypt/tesla-claude-plugin --skill telemetry

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

  • 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

What its author says it does

Copied from the file, not written here

Fleet Telemetry management — self-hosted real-time vehicle streaming. Install, configure, and monitor the fleet-telemetry Docker stack.

SKILL.md

2.5 KB, 516 tokens by cl100k_base, as published. Nobody here has run it

Tesla Fleet Telemetry

Self-hosted real-time telemetry streaming using the official fleet-telemetry server. Streams live vehicle data (location, speed, battery, climate, etc.) to your own infrastructure via WebSocket/MQTT.

Install

tesla telemetry install          # pull and configure the fleet-telemetry Docker stack

This sets up the fleet-telemetry container with TLS certificates, configures your vehicle to stream to the server, and registers the server endpoint with the Fleet API.

Configure Streaming Fields

tesla telemetry configure        # interactive field selector (what data to stream)

Common fields: Location, Speed, BatteryLevel, ChargeState, ClimateState, InsideTemp, OutsideTemp, Odometer, SentryMode.

Start / Stop

tesla telemetry start            # start the fleet-telemetry container
tesla telemetry stop             # stop the container
tesla telemetry restart          # restart after config changes

Monitor

tesla telemetry status           # container health, uptime, connected vehicles, message rate
tesla telemetry logs             # tail live logs from the telemetry server
tesla telemetry logs --tail 100  # last 100 lines

Stream Live Vehicle Data

tesla vehicle stream-live        # stream real-time telemetry to the terminal (Ctrl-C to stop)
tesla vehicle stream-live --fields BatteryLevel,Speed,Location

Response Guidelines

  • If the CLI is not configured (no VIN, no auth), stop and tell the user to run /tesla:setup — never auto-configure
  • Fleet Telemetry requires Fleet API backend — if the user is on Owner API or Tessie, explain the prerequisite
  • Install must be run before start/configure
  • tesla vehicle stream-live uses the telemetry server once it is running
  • For $ARGUMENTS:
    • "install" / "setup" → tesla telemetry install
    • "configure" / "fields" → tesla telemetry configure
    • "start" → tesla telemetry start
    • "stop" → tesla telemetry stop
    • "status" / no args → tesla telemetry status
    • "logs" / "monitor" → tesla telemetry logs
    • "stream" / "live" → tesla vehicle stream-live

Gives 0 of the 12 instructions most monitoring observability skills give in 516 tokens

Counted across 481 of the 483 authors here whose files we hold, read 2026-08-06

  • link every alert to a runbookin 43 of 481, across 35 files
  • use structured json loggingin 36 of 481, across 31 files
  • alert on user-facing symptomsin 20 of 481, across 15 files
  • emit structured JSON logs with stable event namesin 18 of 481, across 13 files
  • propagate trace context across boundariesin 16 of 481
  • use histograms for latency trackingin 14 of 481, across 9 files
  • use OpenTelemetry for distributed tracingin 13 of 481, across 8 files
  • include a correlation ID on every log linein 13 of 481, across 8 files
  • Define service level objectivesin 10 of 481, across 7 files
  • Call useAzureMonitor before importing other modulesin 9 of 481, across 2 files
  • stop and ask for clarification if inputs are missingin 9 of 481, across 2 files
  • define on-call questions before adding telemetryin 9 of 481, across 4 files

Said here and by no other author read

  • run install before start or configure
  • stop and tell the user to run setup if cli is unconfigured
  • never auto-configure the cli
  • explain the fleet api backend prerequisite if missing
  • restart the container after config changes
  • run tesla telemetry install for setup arguments

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 328,083. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.