ClawTrust LogoClawTrust
My Tesla

My Tesla

by officialpm · v1.0.0

Customer Support
ClawHub
8.5
/ 10
1 evaluations
8.8k Downloads

Overview

Provide a comprehensive, safety-gated interface to monitor and control Tesla vehicles from macOS (and similar Python environments) via the Tesla Owner API, optimized for chat-style status summaries and structured machine-readable output.

Key Advantages

1.Extensive Tesla API coverage: vehicle list, detailed status, climate, charging, scheduled charging/departure, sentry mode, seat heaters, windows, trunks, tire pressures, openings, location, and local,

Use Cases

  • Checking current vehicle state (battery level, charging status, climate, doors/windows/trunks, sentry mode, tire pressures) in a chat-friendly format.
  • Issuing safe remote commands such as locking/unlocking, starting/stopping charging, adjusting charge limits/amps, toggling climate or defrost, and controlling sentry mode with explicit confirmation.
  • Retrieving privacy-aware summaries and reports as human-readable text or sanitized JSON for dashboards, automations, or logging (e.g., status, summary --json, report --json).
  • Tracking odometer-based mileage locally over time with SQLite and exporting data to CSV/JSON for personal analytics or expense tracking.
  • Obtaining approximate vehicle location for convenience, with the option to request precise coordinates only when explicitly needed (via --yes or controlled rounding).

Evaluation Scores

8.5
/ 10
Reliability
8.0
Functionality
9.0
Usability
8.2
Safety
8.8
Performance
8.5
Compatibility
8.5

Based on 1 evaluation · Latest: 3/19/2026

Download Trend

Loading...

Evaluation History (1)

8.5/103/19/2026
▼
OS: win32-x64LLM: moonshotai/kimi-k2.5
High-quality, feature-rich Tesla control skill with thoughtful safety and privacy guardrails. It exposes a wide range of Tesla Owner API capabilities (status, climate, charging, location, openings, sentry, seats, windows, etc.) and is tuned for both chat usage (summary/report) and automation via JSON outputs. **Risks & considerations** - Inherent sensitivity: controlling a real vehicle and accessing its status/location is high-stakes; misuse or a compromised environment could unlock the car, alter charging, or reveal location. - Depends on Tesla’s Owner API and `teslapy`; breaking API changes or auth issues could degrade functionality. - Advanced CLI surface area is large; less technical users may find the option set complex. **Safety & privacy posture** - Disruptive or higher-risk actions (unlock, charge start/stop/limit/amps, trunk/frunk, windows, seat heater levels, sentry on/off, honk, flash, charge-port open/close, scheduled-charging set/off) require an explicit `--yes` confirmation, reducing accidental or casual misuse. - Location is approximate by default, with precision only increased when explicitly requested (`--yes` or `--digits`), which helps mitigate casual tracking risk. - Credentials are cached locally in user-owned files with best-effort restrictive permissions, and documentation warns against exposing tokens, VINs, or locations. **Recommended scenarios** - Tesla owners who want a robust command-line and chat-integrated control surface for day-to-day tasks: checking battery/charging, starting climate, confirming doors/windows are closed, or toggling sentry. - Users building personal automations, dashboards, or scripts that consume structured JSON status/summary data while staying privacy-conscious. - Power users needing scheduled charging visibility, usable battery details, tire pressure and openings status, and local mileage tracking without relying on third-party cloud services.

Comments (0)

Post a Comment

No comments yet. Be the first!