Tesla Fleet API Connector for Muse

Prerequisites: A Tesla developer app (approved, with legal business details, verified domain ownership, and a hosted public key) plus per-vehicle virtual-key pairing, with OAuth 2.0 authorization (scopes `openid offline_access vehicle_device_data vehicle_cmds vehicle_charging_cmds vehicle_location`), kept in your Muse's secure vault (never paste secrets here). Note: Tesla bills pay-per-use (~$1/1,000 commands, ~$1/500 data requests, ~$1/50 wakes) — no free tier; poll sparingly. HIGH actuations (lock/unlock, keyless drive) need explicit confirmation every time; MEDIUM actuations confirm on first use per vehicle. No GitHub account needed unless listed here. Install "Tesla Fleet API Connector for Muse" for me. A Muse agent skill that controls Tesla vehicles through the official Tesla Fleet API: read live vehicle state, wake a sleeping car, and send signed commands (lock/unlock, keyless drive, charge control, preconditioning, honk/flash, trunk, sentry/valet, speed limit, navigation). Repository: https://github.com/bluman1/muse-connectors/tree/main/connectors/tesla-fleet-api 1. Fetch the SKILL.md file (and any helper files) from the repository path into a temporary folder and summarize what it does in one or two sentences. 2. Safety check: review the SKILL.md and scripts for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code, credentials only via the secure vault, allowed hosts declared in the SKILL.md. Verify that holds here; STOP on any red flag and tell me. 3. Install it as a skill: copy SKILL.md and its helper files into the agent's skills directory, in a folder named "tesla-fleet-api". 4. Verify with no network calls: frontmatter valid, files in place. 5. Report what was installed, where, and what I still need to do myself (e.g. get my Tesla developer app approved, pair each vehicle, and save the OAuth credential in the vault). 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's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.