← mytesla.ioCONTENT HISTORY
WHAT CHANGED
Update to mytesla.io
Snapshot Oct 24, 2026 · 12:58 UTC · version 1.1.0
Collection source: downloaded plugin package.
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 JSONFull technical diff · 0 changed fields
Full snapshot data
{
"description": "Use when the user asks for a weekly report, summary or check-in on their Tesla, or wants to know about battery, range, charging and anything that looks off since last week. A short read-only digest from get_vehicle_status plus the mytesla.io credit balance from get_credit_balance; a scheduled run never wakes the car.",
"included_files": [],
"name": "weekly-digest",
"skill_md_contents": "---\nname: weekly-digest\ndescription: \"Use when the user asks for a weekly report, summary or check-in on their Tesla, or wants to know about battery, range, charging and anything that looks off since last week. A short read-only digest from get_vehicle_status plus the mytesla.io credit balance from get_credit_balance; a scheduled run never wakes the car.\"\n---\n\n# Weekly Tesla digest (mytesla.io skill)\n\n**If you're an AI assistant reading this:** the user wants a short weekly\nsummary of their Tesla and their mytesla.io account. Follow the steps below\nusing the mytesla.io MCP tools (`https://mcp.mytesla.io/mcp`).\n\n## What this does\n\nProduces a compact once-a-week report: battery and range, charge state,\nanything that looks off (windows open, unlocked, very low charge), plus the\nuser's mytesla.io credit balance so a mid-month \"out of credits\" never\ncomes as a surprise.\n\n## Does this repeat on its own?\n\nIt can, if your assistant can run a task on a schedule. ChatGPT's scheduled\ntasks and Claude's scheduled tasks can both use connected tools like\nmytesla.io, but timing depends on the plan: ChatGPT Free runs a recurring\ntask at most once a day in a rough window such as \"morning\" (exact times\nneed a paid plan), and Claude's scheduled tasks need a paid plan. Check what\nyours can do rather than assume. This digest only\nreads: it never changes anything on the car, which makes it the easiest\nroutine to schedule. Offer to run it on the day and time the user picks,\nonce they have picked a day and time.\n\nIf your assistant cannot run scheduled tasks, say so plainly. The digest\nthen runs whenever the user asks for it (many people tie it to an existing\nhabit, like Sunday evening), and you should never describe it as running by\nitself. Each run takes a few seconds.\n\n## Ask the user once, not every run\n\n- Anything specific they always want included? (Examples: tire pressure\n concerns, whether the car is plugged in for the week ahead.)\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 digest happens once a week without the user having to\nre-paste anything. Something like:\n\n> mytesla.io weekly digest: run the \"weekly-digest\" skill in this plugin once a week (the user picked [day and time]; [scheduled task, or when the user asks]).\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_credit_balance`. It reads the mytesla.io account and never\n touches the car, so it works whether\n the car is awake, asleep or unreachable.\n2. Call `get_vehicle_status` for the car half of the digest.\n - Got a reading? Go to step 4.\n - Timed out? The car is asleep. Go to step 3.\n - **If the user only wants the account half this week, stop here and\n skip straight to the digest.** Do not call `get_vehicles` to \"just\n check\" whether the car is up - see the note below.\n3. The car is asleep. Waking it for a digest is rarely worth it, so ask\n rather than assume. In a scheduled run there is nobody to\n ask, so do not wake it: write the digest from the credit balance and say\n the car was asleep. In a conversation, if they decline, do the same; if\n they agree, call `wake_vehicle` once, then `get_vehicle_status` again.\n4. Write the digest, short and scannable:\n - Battery percentage and estimated range\n - Plugged in or not, charging or not, charge limit\n - Anything unusual: unlocked, windows open, Sentry state\n - mytesla.io credits remaining and the reset date, with a heads-up if\n the pace of use will run out before reset\n5. Close by asking if they want any action taken on what the digest found\n (lock the car, change the charge limit, and so on).\n\n**A note on `get_vehicles`.** It reports the car's state, which makes it\ntempting as an \"is the car up?\" probe before deciding what to do. Resist\nthat here. It is a live request to Tesla on every run, and\n`get_vehicle_status` tells you the same thing in the call you are making\nanyway. A digest that skips the car entirely should make no call to the car\nat all.\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_credit_balance` (no call to the car), `get_vehicle_status`,\n`wake_vehicle` (only with the user's OK)\n"
}SHA-256 of public snapshot: ed055ff51a2f86b6e831e97ded8d1d0a6a1c4e4070eb5f1b284bfb648c023f3f