Analytics
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.
npx -y skills add dacrypt/tesla-claude-plugin --skill analyticsAssembled 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
Tesla analytics via TeslaMate — trip history, charging costs, battery degradation, vampire drain, efficiency, heatmaps. Requires TeslaMate.
SKILL.md
3.3 KB, 821 tokens by cl100k_base, as published. Nobody here has run it
Tesla Analytics (TeslaMate)
Deep analytics from your TeslaMate PostgreSQL database.
Prerequisite: TeslaMate must be connected. If not set up, guide the user:
uv tool install tesla-cli[teslaMate] tesla teslaMate connect postgresql://user:pass@host:5432/teslamateFor a managed Docker stack:
tesla teslaMate install
Connection Status
tesla teslaMate status # lifetime stats + connection health
Trip History
tesla teslaMate trips # last 20 trips
tesla teslaMate trips --limit 50 # last 50 trips
tesla teslaMate trip-stats # summary + top routes
tesla teslaMate trip-stats --days 30 # last 30 days
tesla teslaMate efficiency # per-trip energy efficiency (Wh/km)
Charging Analytics
tesla teslaMate charging # last 20 charging sessions
tesla teslaMate charging-locations # top charging locations
tesla teslaMate charging-locations --days 90 --limit 10
tesla teslaMate graph # ASCII bar chart of sessions
tesla teslaMate daily-chart # daily kWh chart
tesla teslaMate daily-chart --days 30
Cost Reports
tesla teslaMate cost-report # current month cost breakdown
tesla teslaMate cost-report --month 2026-03 # specific month
tesla teslaMate report # monthly summary (DC vs AC, Wh/km)
tesla charge weekly # weekly kWh + cost (last 4 weeks)
tesla charge cost-summary # aggregated cost totals
Battery Health
tesla teslaMate battery-degradation # monthly max range trend
tesla vehicle battery-health # degradation from snapshot history
Other Analytics
tesla teslaMate vampire # vampire drain analysis
tesla teslaMate heatmap # drive days calendar
tesla teslaMate heatmap --year 2026
tesla teslaMate geo # most-visited locations
tesla teslaMate timeline # unified events timeline
tesla teslaMate timeline --days 7
tesla teslaMate updates # OTA update history
tesla teslaMate stats # lifetime stats
tesla teslaMate sentry-events # sentry mode events
Grafana Dashboards
tesla teslaMate grafana # open Grafana in browser
Response Guidelines
- If the CLI is not configured (no VIN, no auth), stop and tell the user to run
/tesla:setup— never auto-configure - If TeslaMate is not connected, explain what it is and guide through setup
- For cost queries: break down by AC vs DC charging, show cost per kWh
- For battery health: show the trend and explain what's normal (1-3% loss/year)
- For trips: include distance, duration, and efficiency
- For
$ARGUMENTS:- "trips" / "drives" →
tesla teslaMate trips - "charging" / "sessions" →
tesla teslaMate charging - "costs" / "money" / "spent" →
tesla teslaMate cost-report - "battery" / "health" / "degradation" →
tesla teslaMate battery-degradation - "vampire" / "drain" →
tesla teslaMate vampire - "efficiency" →
tesla teslaMate efficiency - "heatmap" / "calendar" →
tesla teslaMate heatmap
- "trips" / "drives" →
Gives 0 of the 12 instructions most analytics metrics skills give in 821 tokens
Counted across 368 of the 369 authors here whose files we hold, read 2026-08-06
- read product marketing context before asking questionsin 18 of 368, across 12 files
- use lowercase with underscores for event namesin 16 of 368, across 6 files
- track events for decisions not vanity metricsin 15 of 368, across 5 files
- use object-action format for event namesin 15 of 368, across 8 files
- produce a tracking plan documentin 14 of 368, across 4 files
- Call RUBE_SEARCH_TOOLS first to get current schemasin 13 of 368, across 2 files
- establish consistent event naming conventions before implementingin 10 of 368, across 4 files
- Verify dimension and metric compatibility before reportingin 9 of 368, across 2 files
- Encrypt data at rest and in transitin 9 of 368, across 3 files
- use snake_case for event namesin 9 of 368, across 5 files
- monitor technical health during the testin 9 of 368, across 5 files
- use consistent property namesin 8 of 368, across 4 files
Said here and by no other author read
- guide teslamate setup if unconnected
- tell user to run setup if cli unconfigured
- never auto-configure
- break down charging costs by AC and DC
- show cost per kWh
- explain battery health trend
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.