Tesla

Prerequisites: a real Tesla plus a self-hosted TeslaMate stack you own on your home network (typically a Raspberry Pi or home server, TeslaMate with Fleet API access), or acceptance that answers will be limited to the layers that exist, plus a Muse setup that can reach the stack through Home Link. Setup layers the owner builds: a Tesla developer account and Fleet API app with a virtual key enrolled on the car, TeslaMate in its sleep-friendly configuration, and optionally Tesla's Fleet Telemetry server. Tesla includes a monthly free credit (currently $10); typical reads cost fractions of a cent beyond it. Read-only credentials for the local databases and MQTT broker are stored by the host and must never be pasted into chat. Install "Tesla" for me. A gadget skill that reads Tesla status, drive and charge history, and efficiency analytics from an existing self-hosted TeslaMate and Fleet Telemetry stack, read-only by default. Repository: https://github.com/amanthakkar/musecases/tree/main/skills/gadget-tesla 1. Fetch the SKILL.md file from the repository into a temporary folder and summarize what it does in one or two sentences. Do not paste the full SKILL.md text into this chat. 2. Safety check: review the SKILL.md for anything suspicious (unexpected network calls, credential harvesting). Credentials must never be pasted into chat. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md into the agent's skills directory, in a folder named "gadget-tesla". 4. Verify with no network calls: frontmatter valid, file in place. 5. Report what was installed, where, and what I still need to do myself (for example identifying the vehicle from the local stack, labeling geofences, or confirming which layers exist). If your setup has the Home Link networking and safety rules document (~/docs/devices/home_link.md), follow it; if not, apply the stay-local rules in this prompt. GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it is in the prerequisites above. Rules: do not touch anything outside the temp folder and the install target. Read-only by default: no vehicle commands unless I explicitly request one and an owner-controlled command proxy is already deployed, never send Fleet API commands directly from a skill session, never wake the vehicle to satisfy curiosity, and never change TeslaMate polling, telemetry subscriptions, or Fleet API scopes as a side effect of answering. If anything looks off, stop and ask me.