Deterministic Tessie vehicle reads, confirmed controls and health checks through protected dynamic vehicle policy and the existing OneCLI gateway.
73
91%
Does it follow best practices?
Run evals on this skill
Adds up to 20 points to the overall score
Passed
No findings from the security scan
Process steps in order. Do not skip ahead.
The fire-time precheck (scripts/tessie-precheck.py) resolves the current host-admitted vehicle list and reads every addressable vehicle from Tessie's cache and wakes the agent only when something needs attention. Its thresholds, wake conditions and output shape are the script's contract (top-of-file docstring and constants). This skill is the foundation check; Tesla2-7 features compose the tessie-ops scripts and bring their own prechecks.
The wake data names a reason and, for attention_needed, an alerts list. If the data carries no alert and no failure, finish silently.
Report every item in alerts, including per-vehicle failures alongside battery alerts. State each fact as a declarative sentence in the chat's language: which vehicle (alias), what the precheck found, and what the owner can do. For low_battery_unplugged, add the battery level and say it is not plugged in. For a top-level failure or an alert with kind script_failed, script_timeout, bad_output or precheck_error, quote its error text and point to docs/setup.md Command and failure semantics. Never include coordinates or addresses. Never ask whether the owner already knows.
Send the message with mcp__nanoclaw__send_message and finish here. Do not run controls: a notice grants no authority to act on the vehicle.