agentleFS
Sign inStart free
dacryptdacrypt/tesla-claude-plugin/skills/automations/SKILL.md

automations

Skill0 starsChanged 7 months agoMITView on GitHub

Tesla automation rules — create triggers that fire notifications or commands when vehicle state changes. Battery alerts, charge complete, sentry events.

4 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions4 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 4

    1. esphome/esphome★ 12ksame name
    2. BuilderIO/agent-native★ 7.6ksame name
    3. truffle-ai/dexto★ 659same name
    4. uplika/uplika-plugin★ 3same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • In this repository11 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

2 rules. 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use this to verify notification delivery before enabling the rule in the daemon.

    line 77
  2. Very specific:

    If the CLI is not configured (no VIN, no auth), stop and tell the user to run /tesla:setup — never auto-configure

    line 87

“Common” is measured: kept by at least 6 in 10 of the 4 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Tesla Automations

Rule-based automation engine that monitors vehicle state and fires notifications or shell commands when conditions are met.

List Rules

tesla automations list           # show all configured rules (name, trigger, action, enabled)
tesla automations list --json    # machine-readable output

Add Rules

tesla automations add            # interactive wizard (name, trigger, condition, action)

Rules have three parts: a trigger (what to watch), a condition (threshold/value), and an action (notify or run command).

Default Rules

The following rules are available out of the box:

Rule nameTriggerDefault conditionAction
battery_belowbattery SoC< 20%push notification
charging_completecharge statebecomes Completepush notification
sentry_eventsentry modenew event detectedpush notification
tesla automations add --preset battery_below    # add the 20% low-battery alert
tesla automations add --preset charging_complete
tesla automations add --preset sentry_event

Remove Rules

tesla automations remove <name>  # delete a rule by name
tesla automations enable <name>  # re-enable a disabled rule
tesla automations disable <name> # disable without deleting

Run Daemon

tesla automations run            # start the rules daemon (foreground)
tesla automations run --source auto  # auto-select best data source (TeslaMate → Fleet → Owner)
tesla automations run --interval 60  # poll every 60 seconds (default: 30)

The daemon polls vehicle state on the configured interval and evaluates all enabled rules.

Install as System Service

tesla automations install        # install as launchd (macOS) or systemd (Linux) service
tesla automations uninstall      # remove the service

Test a Rule

tesla automations test <name>    # fire the rule action once, regardless of conditions

Use this to verify notification delivery before enabling the rule in the daemon.

Status

tesla automations status         # daemon running? last evaluation? last fired rule?

Response Guidelines

  • If the CLI is not configured (no VIN, no auth), stop and tell the user to run /tesla:setup — never auto-configure
  • List rules first before suggesting add/remove operations
  • Suggest presets for the three most common use cases (battery_below, charging_complete, sentry_event)
  • Remind the user the daemon must be running (or installed as a service) for rules to fire
  • For $ARGUMENTS:
    • "list" / no args → tesla automations list
    • "add" / "create" / "new" → tesla automations add
    • "remove" / "delete" → tesla automations remove <name>
    • "run" / "start" / "daemon" → tesla automations run
    • "install" / "service" → tesla automations install
    • "test" → tesla automations test <name>
    • "status" → tesla automations status

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free