Tesla Control via Tessie
v1.0.0Control and monitor Tesla vehicles via the Tessie API. Use when you need to check Tesla status (battery, location, charging), control climate (heat/cool), lock/unlock doors, start/stop charging, honk/flash lights, open charge port or trunks, or any other Tesla vehicle command. Requires TESSIE_API_KEY environment variable.
⭐ 1· 1.5k·0 current·0 all-time
MIT-0
Download zip
LicenseMIT-0 · Free to use, modify, and redistribute. No attribution required.
Security Scan
OpenClaw
Suspicious
high confidencePurpose & Capability
The skill name, SKILL.md, reference docs, and included Python scripts all match the stated purpose (controlling a Tesla via the Tessie API). The actions implemented (lock/unlock, climate, charge, software updates, location, etc.) are coherent with the description.
Instruction Scope
Runtime instructions and scripts are limited to calling the Tessie API and using the TESSIE_API_KEY environment variable. The SKILL.md does not instruct reading unrelated system files or exfiltrating data to unexpected endpoints; all network calls target api.tessie.com per the reference doc.
Install Mechanism
There is no install spec (instruction-only), which is low risk; scripts require Python 'requests' (SKILL.md tells user to pip install requests). One minor inconsistency: code files are bundled but no install/packaging step is provided — acceptable but worth noting.
Credentials
The skill requires a TESSIE_API_KEY (declared in SKILL.md and used directly by both scripts) but the registry metadata lists 'Required env vars: none' and 'Primary credential: none'. That mismatch is significant: the skill will need a bearer token with control permissions for vehicles, and the registry should declare this explicitly. No other unrelated credentials are requested.
Persistence & Privilege
The skill does not request permanent/always-on inclusion (always:false) and does not attempt to modify other skills or system-wide settings. It can be invoked autonomously by the agent (default platform behavior) — because this skill can issue remote vehicle commands, allow autonomous invocation only with explicit user consent.
What to consider before installing
This skill implements exactly what it claims (remote Tesla control via Tessie) but the registry metadata incorrectly omits the required TESSIE_API_KEY. Before installing: (1) confirm the registry entry is updated to declare TESSIE_API_KEY as the primary credential; (2) review the included scripts to ensure no modifications are needed for your environment (they call https://api.tessie.com and read TESSIE_API_KEY from the environment); (3) ensure the API key you provide has the minimum scope needed and be prepared to rotate/revoke it if needed; (4) consider limiting the agent's autonomous use of this skill (so it cannot issue remote lock/unlock/fart/honk commands without your explicit approval); and (5) if you don't trust the skill owner, run the scripts in an isolated environment (or inspect and run locally) rather than granting platform-level access. If the registry maintainer cannot explain/fix the missing env metadata, treat the omission as a red flag and do not install.Like a lobster shell, security has layers — review code before you run it.
automationvk97224vhhe3ww0051gmvkxb5ds802yf4evvk97224vhhe3ww0051gmvkxb5ds802yf4latestvk97224vhhe3ww0051gmvkxb5ds802yf4teslavk97224vhhe3ww0051gmvkxb5ds802yf4tessievk97224vhhe3ww0051gmvkxb5ds802yf4vehiclevk97224vhhe3ww0051gmvkxb5ds802yf4
License
MIT-0
Free to use, modify, and redistribute. No attribution required.