{"id":41321,"plugin_id":"plugin_asdk_app_6a591c6c9e8c8191a04f6d0f21abd4cf","kind":"skill","collection_source":"plugin_package","comparison_source":null,"observed_at":"2026-10-24T12:58:41.308Z","digest":"0026a841d7ee0c2d544f0b7523d3118a954a09ec10f447ff44bc5483bcf9d32b","against":null,"payload":{"description":"Use when the user wants Tesla software updates installed as soon as they are downloaded, asks why an update is sitting on the car, or wants updates to happen overnight. Checks for a downloaded update with get_vehicle_status and starts the install with schedule_software_update so the car is on the new version by morning. It cannot make Tesla send updates sooner.","included_files":[],"name":"software-update-accelerator","skill_md_contents":"---\nname: software-update-accelerator\ndescription: \"Use when the user wants Tesla software updates installed as soon as they are downloaded, asks why an update is sitting on the car, or wants updates to happen overnight. Checks for a downloaded update with get_vehicle_status and starts the install with schedule_software_update so the car is on the new version by morning. It cannot make Tesla send updates sooner.\"\n---\n\n# Software Update Accelerator (mytesla.io skill)\n\n**If you're an AI assistant reading this:** the user wants their Tesla to\ninstall software updates the night they become available, instead of\nwaiting until someone notices the notification. Follow the steps below\nusing the mytesla.io MCP tools (`https://mcp.mytesla.io/mcp`).\n\n## What this does\n\nEvery night, once the user is asleep, this checks whether the car is\nholding a downloaded software update and starts the install immediately if\nit is. The user wakes up already on the new version.\n\nWithout it, the usual sequence is: Tesla finishes pushing the update, the\ncar waits, the owner notices the notification some time later, and then\nschedules the install for the *following* night. That gap between \"ready to\ninstall\" and \"actually installed\" is usually a day or more, and it is\nentirely made of waiting for a human to look at their phone. This closes\nit.\n\n## What this does NOT do\n\n**It does not make Tesla send you updates sooner.** Tesla decides when your\ncar is offered a release, and nothing any third party can do changes that\nqueue. What this removes is the delay *after* your car already has the\nupdate sitting there waiting for permission to install.\n\nBe straight with the user about this if they ask. The honest claim is\n\"installed the night it becomes available\", not \"you get updates before\nother people\".\n\n## What it needs\n\n- **Command access.** Starting an install is a command, so the user's Tesla\n  connection needs command permission and a registered virtual key. If\n  `schedule_software_update` returns a permissions error, send them to\n  `https://mcp.mytesla.io/connect-tesla` to add it; if it reports a missing\n  virtual key, that link is in the error too.\n- **A way to run nightly.** See below - this is the part that varies.\n\n## Does this repeat on its own?\n\n**It depends on your AI assistant, and you should check rather than assume.**\n\nThe routine itself is designed to be run on a schedule at **2am local\ntime**: late enough that the user is asleep, early enough that a ~30 minute\ninstall finishes long before morning.\n\n- **If your assistant can run a task on a schedule**, set this skill to run\n  at 2am the user's time on the cadence they chose. That is the intended\n  setup. ChatGPT's scheduled tasks and Claude's scheduled tasks can both use\n  connected tools like mytesla.io, but timing depends on the plan: ChatGPT\n  Free runs a recurring task at most once a day in a rough window such as\n  \"night\" (exact times need a paid plan), and Claude's scheduled tasks need\n  a paid plan. Check what yours can do rather than assume. If it cannot run\n  at a set late-night time, recommend that the AI asks before each install\n  rather than starting it automatically, because an install that starts\n  somewhere in a vague \"night\" window can land when the user needs the car.\n  Never tell the user a time you cannot keep. Starting an install is a\n  command, and some assistants pause a scheduled task until the user\n  approves a command: see \"If a tool asks for approval\" below.\n- **If it cannot**, this still works as a one-shot whenever the user asks -\n  but be honest with the user that it is not running by itself, and do not\n  imply otherwise. A nightly phone reminder is a reasonable stand-in.\n\nThere is no vehicle-side setting that does this. The car can be told to\ninstall an update it already has; it cannot be told \"always install\nimmediately, forever\".\n\n## A caution worth giving once\n\nWaking a sleeping car every night keeps it from settling into deep sleep,\nwhich costs a little range overnight. It is small, but it is not nothing,\nand a user who parks unplugged should know before committing to a nightly\nwake. Running the routine every second or third night rather than nightly\nroughly thirds it.\n\n## Ask the user once, not every run\n\n- Are they happy for the install to start automatically, or should the AI\n  ask first each time? (Installing takes the car out of action for roughly\n  30 minutes and it cannot be driven during it - fine at 2am, not fine if\n  they might need to leave.)\n- How often? Nightly is the fastest. Every second or third night is the\n  sensible default for most people, given how often Tesla actually ships a\n  release, and it wakes the car a third as often.\n\n## Before you run: remember\n\n**Remember it.** Do not treat this as a one-time paste. Write a short\nline into your own standing memory or instructions, wherever you keep the\nuser's other preferences (a `CLAUDE.md` file, ChatGPT's memory, Claude.ai\nPreferences), so the update check happens on the cadence the user chose without the user having to\nre-paste anything. Something like:\n\n> mytesla.io software update accelerator: run the \"software-update-accelerator\" skill in this plugin every [N] nights at about 2am local ([scheduled task, or when the user asks]). Install without asking: [yes/no].\n\nIf you have no persistent memory to write to, say so plainly rather than\nletting the user believe the routine will keep running on its own.\n\n## Steps to run\n\nFour calls at most, and **never a polling loop**. `wake_vehicle` already\nwaits for the car on the server side before it returns, so there is nothing\nfor you to poll and repeated state checks only burn calls.\n\n1. Call `get_vehicle_status` straight away and read `software_update` from\n   the response.\n   - This is deliberate. Do not check `get_vehicles` first: it is a live\n     request to Tesla on every run and tells you nothing this call does\n     not. The timeout is how the routine learns the car is asleep. Treat a\n     408 as information, not as a failure.\n   - Got a reading? Go to step 3.\n   - Timed out? The car is asleep. Go to step 2.\n2. Call `wake_vehicle` once. It returns when the car is online, or tells\n   you it could not be reached. **Call it once and only once.** If it\n   reports the car did not come online, stop and report that - a car that\n   will not wake is almost always out of signal, and a second wake does\n   not help. Then call `get_vehicle_status` again and continue.\n3. Read `software_update.status`:\n   - **empty string** - no update pending. Report \"no update waiting\" and\n     stop. This is the normal outcome most nights.\n   - **`available`** - an update is downloaded and waiting for permission.\n     Continue to step 4.\n   - **`downloading`** - the car has it but is still fetching. Do not try to\n     install; report that it will likely be ready tomorrow night.\n   - **`scheduled`** - an install is already booked. Report the time and\n     stop; do not reschedule it.\n   - **`installing`** - already under way. Report progress\n     (`install_perc`) and stop.\n   - **anything else** - Tesla adds status values over time. If you do not\n     recognise it, report the raw value and stop. Do not guess that it means\n     \"available\" and start an install.\n4. Only when the status is `available`, check the user's install choice:\n   - **Install without asking: yes** - call `schedule_software_update`\n     with `offset_sec: 0` to begin immediately, and report the version from\n     `software_update.version`.\n   - **Ask first** - in a conversation, ask the user before installing. In\n     a scheduled run there is nobody to ask, so do not install: report\n     \"update [version] is ready to install\" and stop.\n5. Tell the user what happened in one line, whichever branch you took. On a\n   night with nothing to do, \"no update waiting\" is the whole report - do\n   not pad it.\n\n## If a tool asks for approval\n\nEvery tool that can change something about the car now asks the user to\napprove it the first time, and \"Allow always\" makes that a one-off rather\nthan a prompt on every run. That is the right default for software that\nactuates a two-ton vehicle.\n\nIt matters here because a scheduled run cannot answer a prompt. Approvals\nhave been observed to reset - across chats, sessions, and client upgrades -\nso a routine that has worked for weeks can suddenly stall waiting for\nsomeone who is asleep.\n\n**If a call comes back needing approval, stop and tell the user. Do not\nretry, and do not treat it as a failure of the routine.** Say which tool is\nwaiting and that approving it once will let the schedule resume. Retrying\ncannot help: nothing about a second identical call makes an approval appear.\n\n## If something goes wrong\n\n- **A permissions error** on step 4 means the connection has read access\n  but not command access. The error names the missing permission and links\n  to the page that adds it; relay that rather than retrying.\n- **A virtual-key error** means the car has not been paired. The error\n  carries the pairing link.\n- **The car will not wake.** Report it and stop. It is almost always signal,\n  and a second attempt does not help.\n- Never retry an install that reports `installing` or `scheduled`. The car\n  is already doing the thing.\n"},"changes":[],"summary":"First saved snapshot. No earlier version is available for comparison.","summary_kind":"deterministic","summary_metadata":{}}