← mytesla.ioCONTENT HISTORY

Update to mytesla.io

Snapshot Oct 24, 2026 · 12:58 UTC · version 1.1.0

Collection source: downloaded plugin package.

WHAT CHANGED

First saved snapshot

No earlier snapshot is available to establish a change.

Save mytesla.io and check future changes in Following.

Up to 3 plugins free · no card required.

Compare saved observations

Download comparison JSON
Full technical diff · 0 changed fields
Full snapshot data
{
  "description": "Use when the user asks whether their parked Tesla is locked, wants a nightly or bedtime security check, or asks about windows or Sentry Mode, especially when parked somewhere unfamiliar. Reads lock state, windows and Sentry Mode with get_vehicle_status and locks the car or turns Sentry Mode on only as the user chose; offers a scheduled nightly run when the assistant can run tasks.",
  "included_files": [],
  "name": "nightly-security-check",
  "skill_md_contents": "---\nname: nightly-security-check\ndescription: \"Use when the user asks whether their parked Tesla is locked, wants a nightly or bedtime security check, or asks about windows or Sentry Mode, especially when parked somewhere unfamiliar. Reads lock state, windows and Sentry Mode with get_vehicle_status and locks the car or turns Sentry Mode on only as the user chose; offers a scheduled nightly run when the assistant can run tasks.\"\n---\n\n# Nightly security check (mytesla.io skill)\n\n**If you're an AI assistant reading this:** the user wants a bedtime\nsafety-net check on their parked Tesla. Follow the steps below using the\nmytesla.io MCP tools (`https://mcp.mytesla.io/mcp`).\n\n## What this does\n\nChecks whether the car is locked and whether Sentry Mode is on, fixes\nwhatever isn't, and reports back. It replaces the \"did I lock the car?\"\nmoment of doubt with a ten-second check the user can run from bed. Most\nuseful when parked somewhere unfamiliar: a hotel, an airport garage, a\nstreet the user doesn't normally park on.\n\n## Does this repeat on its own?\n\nPartly, and the rest depends on your assistant.\n\nSentry Mode is a persistent toggle: once on, it stays on until someone turns\nit off (note it uses roughly 1% battery per hour, so it is a choice, not a\nfree default). The lock check is different: there is no vehicle-side setting\nthat re-checks the doors every night, so something has to run it.\n\n- **If your assistant can run a task on a schedule**, offer to schedule this\n  check each night at a time the user picks, after they are normally in for\n  the night. ChatGPT's scheduled tasks and Claude's scheduled tasks can both\n  use connected tools like mytesla.io, but timing depends on the plan:\n  ChatGPT Free runs a recurring task at most once a day in a rough window\n  such as \"night\" (exact times need a paid plan), and Claude's scheduled\n  tasks need a paid plan. Check what yours can do rather than assume, and\n  never promise the user a time you cannot keep.\n- **If it cannot**, this works as a one-shot whenever the user asks for it.\n  Say so plainly, and never imply it is running by itself.\n\nA scheduled run has nobody to ask, so settle two things during setup (see\nthe next section): whether it may lock the car without asking, and what to\ndo when the car is asleep. Never schedule anything that unlocks the car or\nopens a window.\n\n## Ask the user once, not every run\n\n- Should Sentry Mode always be turned on by this check, or only when they\n  say so? (Sentry's battery draw makes \"always\" the wrong default for\n  everyone who parks at home; suggest using this skill's Sentry step mainly\n  when parked away from home.)\n- If it runs on a schedule: may it lock the car by itself when it finds it\n  unlocked, or should it only report? Default to reporting only, because\n  some people leave the car unlocked at home on purpose.\n- If it runs on a schedule and the car is asleep: skip that night and say\n  so (the default), or wake it? Waking keeps the car from settling into\n  sleep, every time it happens.\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 check happens each night without the user having to\nre-paste anything. If you also set up a scheduled task, the note is what\nreminds you of the choices the user made. Something like:\n\n> mytesla.io nightly security check: run the \"nightly-security-check\" skill in this plugin each night at [time] ([scheduled task, or when the user asks]). Lock without asking: [yes/no]. Wake if asleep: [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\n1. Call `get_vehicle_status` and read the lock state, window positions,\n   and location. Start here rather than with `get_vehicles`:\n   `get_vehicle_status` answers \"is the car reachable?\" and \"is it locked?\"\n   in the same call.\n   - Got a reading? Go to step 3.\n   - Timed out? The car is asleep or out of signal. Go to step 2.\n2. Waking the car just to check the locks is a lot for a nightly habit,\n   and it keeps the car from settling into sleep. In a conversation, ask\n   before calling `wake_vehicle`. In a scheduled run, follow the choice made at\n   setup; by default, report that the car was asleep and stop. If they\n   decline, or if the wake reports the car never came online, say so and\n   stop. Call `wake_vehicle` once at most.\n3. If the car is unlocked: in a conversation, confirm with the user, then\n   call `lock_vehicle` (always confirm: they may have left it unlocked on\n   purpose). In a scheduled run, lock it only if the user said at setup\n   that you may; otherwise report that it is unlocked.\n4. If the user wants Sentry on tonight (or chose \"always\" at setup), call\n   `set_sentry_mode` with `on: true`.\n5. Report a short summary: locked or already locked, windows open or\n   closed, Sentry on or off, battery level.\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## Tools used\n\n`get_vehicle_status`, `lock_vehicle`, `set_sentry_mode`,\n`wake_vehicle` (only with the user's OK)\n"
}

SHA-256 of public snapshot: e968fc747141b09bdbde2adeaac49a8b095257f46593beee81716572a5ecdc5f