agentleFS
Sign inStart free
dacryptdacrypt/tesla-claude-plugin/skills/telemetry/SKILL.md

telemetry

Skill0 starsChanged 7 months agoMITView on GitHub

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

11 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dashboard and create-skill.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • GoogleSkill

    dashboard

    Configures and launches the GKE Capacity & Triage Dashboard scoped to a GCP project ID, GKE cluster name, or target ML workload ID. Uses the configure-and-launch-dashboard action and launch-workload-dashboard workflow to verify local dashboard health, discover cluster capacity, trigger live scans, and generate deep-linked URLs. Use when the user types "/dashboard", says "launch dashboard", "open dashboard", "show capacity", or "view triage dashboard" with a project, cluster, or workload. Don't use for general workload log querying or automated failure attribution (use the troubleshoot skill).

    Also in 3 projects that use this

  • ElasticSkill

    create-skill

    Interactively create a new Claude Code skill and add it to the elastic-docs-skills catalog. Use when the user wants to generate a new skill, scaffold a slash command, or build automation for docs tasks.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 9 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If the CLI is not configured (no VIN, no auth), stop and tell the user to run /tesla:setup — never auto-configure

    line 57

“Common” is measured: kept by at least 6 in 10 of the 9 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free