Tessie Tesla Control

**Judgment:** High-utility but high-sensitivity control skill for Tesla owners using Tessie, suitable for power users who understand the implications of remote vehicle control and are comfortable granting an API key. Not yet deployed, so it should be treated as in-review and tested cautiously before production use. **What it does well:** - Offers broad control and monitoring of Tesla vehicles: battery, range, climate, charging, location, and basic security-related states (lock/unlock, windows, trunks, sentry via Tessie commands). - Leverages Tessie’s mature API, avoiding direct low-level Tesla API handling and benefiting from Tessie’s richer data (drives, idles, analytics context). - Configuration is straightforward: a single Tessie API key via config or environment variable, with automatic vehicle/VIN detection. - Natural language command set is simple and discoverable (e.g., “tessie battery”, “tessie recent drives”, “tessie set charge limit to 90%”). **Key risks and concerns:** - **Security & privacy risk:** Any party with access to the assistant instance using this skill could obtain sensitive data (real-time location, recent drives) and issue control commands (unlock, open windows/trunks, adjust charging). Protecting the Tessie API key and access to the assistant is critical. - **Physical-world impact:** Unlocking the car, opening windows/trunks, or modifying charging behavior are real-world actions; misinterpretation of user intent or prompt injection could have safety, theft, or nuisance implications. - **Third-party dependency:** Reliability and latency depend on Tessie’s service availability and Tesla’s connectivity. Outages or vehicle sleep states may cause intermittent failures. - **Not yet deployed:** The metadata notes “NOT YET DEPLOYED – pending review,” indicating it may still need validation (error handling, safe defaults, confirmation flows for high-impact actions). **Recommended scenarios:** - Private or tightly access-controlled deployments where the assistant is used by the vehicle owner (or explicitly trusted users) only. - Users who already rely on Tessie and understand its security model, and who want a conversational interface for frequent tasks like preconditioning and charging management. - Non-critical convenience use: checking status, range, or drives, where errors are low-impact. **Caution / when to avoid or restrict:** - Multi-user or shared-chat environments where it is difficult to ensure that only authorized individuals can issue commands. - Any deployment lacking strong authentication, access control, and logging around high-impact commands (unlock, open trunks/windows, enable/disable sentry, etc.). - Automated or agentic workflows that might issue commands without explicit, recent, user confirmation; these should be restricted or require confirmations before executing sensitive actions.