← Back to Skills Marketplace
Tesla Fleet API
by
Oliver Drobnik
· GitHub ↗
· v1.5.2
· MIT-0
3267
Downloads
1
Stars
10
Active Installs
16
Versions
Install in OpenClaw
/install tesla-fleet-api
Description
Use when integrating with Tesla's official Fleet API to read vehicle/energy device data or issue remote commands (e.g. start HVAC preconditioning, wake vehic...
Usage Guidance
This package appears to be a genuine Tesla Fleet API CLI. Before installing: (1) only provide TESLA_CLIENT_ID / TESLA_CLIENT_SECRET that you created for your own Tesla developer app; do not paste these into untrusted locations; (2) the tool asks you to generate and store an EC private key (private-key.pem) and will keep OAuth tokens in auth.json—store these files in a secure workspace and ensure file permissions are restrictive; (3) the signed-command proxy requires installing a Go binary from github.com/teslamotors — verify the exact version and source before running to reduce supply-chain risk; (4) confirm the Fleet/auth base URLs and domain names match official Tesla endpoints you expect (the repo uses fleet-auth.prd.vn.cloud.tesla.com / fleet-api.prd.* hosts); and (5) review SETUP.md and start_proxy.sh to ensure the workspace detection and file paths match where you want these secrets stored. If you are uncomfortable with storing keys/tokens in the detected workspace, run the scripts with an explicit --dir pointing to a secured directory.
Capability Analysis
Type: OpenClaw Skill
Name: tesla-fleet-api
Version: 1.5.2
The tesla-fleet-api skill bundle is a legitimate implementation for interacting with the official Tesla Fleet API. It includes scripts for OAuth authentication (auth.py, tesla_oauth_local.py), vehicle data retrieval (vehicle_data.py), and command execution (command.py) using Tesla's recommended signing proxy architecture. Sensitive data such as OAuth tokens and client secrets are stored locally with restricted file permissions (0o600) and are only transmitted to official Tesla endpoints (e.g., fleet-auth.prd.vn.cloud.tesla.com). The bundle follows Tesla's official security model for third-party integration, including virtual key enrollment and signed commands via the tesla-http-proxy.
Capability Assessment
Purpose & Capability
Name/description (Tesla Fleet API) match the requested binaries (python3, openssl) and required env vars (TESLA_CLIENT_ID, TESLA_CLIENT_SECRET). The included scripts implement OAuth flows, vehicle data reads, and signed command proxying as described.
Instruction Scope
SKILL.md and the scripts' logic stay on-topic: they read/write config.json/auth.json/vehicles.json/private-key.pem in a documented workspace, run a local callback server for OAuth, and call Tesla Fleet / auth endpoints. There are no instructions to read unrelated system secrets or to send data to unexpected external hosts.
Install Mechanism
This is instruction-only (no automated installer). The proxy requires installing a Go binary (github.com/teslamotors/vehicle-command/cmd/tesla-http-proxy) via 'go install' per SETUP.md — a normal step but a supply-chain consideration (you should pin/verify the proxy release before installing). No arbitrary remote archive downloads are performed by the skill itself.
Credentials
Only TESLA_CLIENT_ID and TESLA_CLIENT_SECRET are required; other env vars and files (access/refresh tokens, domain, private key) are optional or clearly documented. Requested credentials align with the described OAuth flows and proxy usage.
Persistence & Privilege
The skill does not request 'always: true' and does not modify other skills or global agent settings. It writes only its own state (config/auth/vehicles/places/proxy TLS) in the workspace; tokens and the private key are stored locally (scripts try to set private permissions).
How to Use
- Make sure OpenClaw is installed (local or Docker)
- Run the install command in chat:
/install tesla-fleet-api - After installation, invoke the skill by name or use
/tesla-fleet-api - Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.5.2
Direct Fleet API reads, automatic 401 refresh, clearer offline reporting, direct wake flow, and robust proxy path resolution.
v1.5.1
fix: use /Users/oliver/clawd for workspace root to preserve symlink paths
v1.5.0
- Dropped the Go runtime dependency; Go is no longer required to use the skill.
- Updated required environment variables and optional settings, removing obsolete entries related to signing proxy and public key.
- Improved documentation for setup, reflecting dependency changes.
- start_proxy.sh script and related requirements simplified due to proxy/signing changes.
- Version bumped to 1.5.0.
v1.4.2
**Changelog for tesla-fleet-api v1.4.2**
- Simplified environment requirements: no longer requires `bash` or `git` for basic operation.
- Removed `.env` file support; credentials are now loaded only from `config.json` or environment variables.
- Updated state directory layout and documentation in SETUP.md and SKILL.md.
- Refined scripts: removed `setup_proxy.sh`, added explicit `start_proxy.sh` and `stop_proxy.sh` for controlling the signing proxy.
v1.3.0
- Adds support for seat cooler (ventilated seat) commands.
- Implements `seat-climate` commands to control seat auto climate modes.
- Updates to precondition scheduling for more robust schedule parameters.
- Various code improvements and expanded option parsing across commands.
v1.2.0
Replace .env loading with config.json for provider creds (legacy .env fallback kept)
v1.1.9
Remove local-only calendar automation (school-precondition.sh) from published package; keep local copy outside skill.
v1.1.8
Mitigate supply-chain risk: setup_proxy uses pinned vehicle-command version via go install; document TESLA_VEHICLE_COMMAND_VERSION override.
v1.1.7
Default state dir is ~/.openclaw; update remaining docs/help strings (legacy ~/.moltbot noted).
v1.1.6
Prefer ~/.openclaw state dir (fallback to legacy ~/.moltbot). Update scripts + docs.
v1.1.5
Declare TESLA_PRIVATE_KEY + document proxy build (vehicle-command clone) and calendar access.
v1.1.4
Declare required env/bins + state dir; make proxy setup script non-installing (no automatic brew install)
v1.1.3
Docs: remove legacy migration note from SETUP.md.
v1.1.2
Docs: remove tesla_fleet.py from scripts overview table.
v1.1.1
Docs: move setup/config into SETUP.md; SKILL.md now references it.
v1.1.0
Split state: config.json/auth.json/vehicles.json/places.json; provider creds via .env; added places + vehicles commands.
Metadata
Frequently Asked Questions
What is Tesla Fleet API?
Use when integrating with Tesla's official Fleet API to read vehicle/energy device data or issue remote commands (e.g. start HVAC preconditioning, wake vehic... It is an AI Agent Skill for Claude Code / OpenClaw, with 3267 downloads so far.
How do I install Tesla Fleet API?
Run "/install tesla-fleet-api" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.
Is Tesla Fleet API free?
Yes, Tesla Fleet API is completely free, licensed under MIT-0. You can download, install and use it at no cost.
Which platforms does Tesla Fleet API support?
Tesla Fleet API is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).
Who created Tesla Fleet API?
It is built and maintained by Oliver Drobnik (@odrobnik); the current version is v1.5.2.
More Skills