agentleFS
dacryptdacrypt/tesla-claude-plugin/skills/status/SKILL.md

status

Skill0 starsChanged 7 months agoMITView on GitHub

Quick Tesla vehicle status — battery level, charging state, location, climate, readiness. Use when someone asks "how's my Tesla?", "battery level?", "where's my car?", "is my car ready?", or similar status queries.

177 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use off, list and 10 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • StakeholderSenseiSkill

    off

    Disable polygraph for this repo (user-only escape hatch; all hooks no-op)

    Also in 4 projects that use this

  • SuShuhengSkill

    list

    Use when checking obshare-cli upload history, finding document tokens, or reviewing previous upload URLs and permission snapshots.

    Also in 8 projects that use this

  • kennethleungtySkill

    pause

    Pause — stop the music (alias for /stop)

    Also in 6 projects that use this

  • codebycoreySkill

    new

    Start a new change with a proposal. Use when starting a feature, creating a proposal, or beginning planned work.

    Also in 7 projects that use this

  • michaelenglandSkill

    import

    This skill should be used when the user wants to import an existing .pptx file into deckwright, bring in a PowerPoint that was created outside this tool, reverse-engineer a presentation for editing, or invoke /deckwright:import. Converts a .pptx into a PptxGenJS generation script so it can be edited and regenerated through the deckwright pipeline.

    Also in 5 projects that use this

  • genomewalkerSkill

    resume

    Resume a thread by loading its ~800-token context capsule

    Also in 15 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 146 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 2

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    If vehicle commands fail with HTTP 412, ConfigurationError, or AuthenticationError, the car may not be delivered yet.

    line 69
  2. Distinctive:

    Do NOT attempt to fix the 412 error by changing config or backends.

    line 85
  3. 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 89
  4. Distinctive:

    If vehicle commands fail, fall back to order status instead of retrying with different backends

    line 90

“Common” is measured: kept by at least 6 in 10 of the 146 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 Vehicle Status

Get a quick overview of the vehicle's current state.

Quick Status

For a fast at-a-glance view:

tesla vehicle summary --oneline

For more detail:

tesla vehicle summary

Specific Queries

Battery & Charging

tesla charge status              # SoC %, range, charge rate, time remaining
tesla charge status --oneline    # compact: 🔋 72% | ⚡ 11kW | 1h30m to 80%

Location

tesla vehicle location           # GPS coordinates + Google Maps link

Readiness (morning check)

tesla vehicle ready              # 7-point system check
tesla vehicle ready --oneline    # ✅ Ready | 🔋 82% | 🌡 22°C

Climate

tesla climate status             # interior/exterior temperatures

Full Vehicle Data

tesla vehicle info               # complete vehicle state (JSON with -j)
tesla vehicle bio                # comprehensive 5-panel profile
tesla vehicle dashboard          # multi-panel Rich dashboard

Health Check

tesla vehicle health-check       # 7-point diagnostic
tesla vehicle software           # firmware version + pending updates
tesla vehicle tires              # TPMS pressure readings
tesla vehicle alerts             # recent fault codes

Pre-delivery Fallback

If vehicle commands fail with HTTP 412, ConfigurationError, or AuthenticationError, the car may not be delivered yet. You MUST run ALL of these commands in order:

Step 1 — Order status:

tesla order status --oneline
tesla order delivery

Step 2 — RUNT registry (MANDATORY — do not skip):

tesla data runt

This shows plate assignment, registration state, liens/prendas, and SOAT. Uses openquery with automatic CAPTCHA solving. This is critical pre-delivery info.

Step 3 — Present results from BOTH order and RUNT together.

Do NOT attempt to fix the 412 error by changing config or backends. Do NOT skip the RUNT query.

Response Guidelines

  • If the CLI is not configured (no VIN, no auth), stop and tell the user to run /tesla:setup — never auto-configure
  • If vehicle commands fail, fall back to order status instead of retrying with different backends
  • Lead with the most relevant info (usually battery %)
  • Include location only if asked or if the car is away from home
  • Mention charging state if plugged in
  • Flag any issues (low battery, open doors, sentry events)
  • For $ARGUMENTS:
    • "battery" → tesla charge status
    • "location" / "where" → tesla vehicle location
    • "climate" / "temp" → tesla climate status
    • "full" / "everything" → tesla vehicle info
    • no args → tesla vehicle summary

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.

Reviews can't be read right now.

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.