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

serve

Skill0 starsChanged 7 months agoMITView on GitHub

Start the Tesla web dashboard and REST API server. Self-hosted on localhost with a React UI for vehicle control, charging analytics, and order tracking. Use when someone says "start the dashboard", "open the web UI", or "run the server".

5 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 5 edited versions we read keep these.

  • 1

    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. Distinctive:

    Start the self-hosted web dashboard and REST API.

    line 14
  2. Very specific:

    Check if the serve extra is installed first

    line 55
  3. Very specific:

    If the user wants to expose to their network, remind them about security (no auth by default — set an API key with tesla config set …

    line 58

“Common” is measured: kept by at least 6 in 10 of the 5 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 Web Dashboard & API

Start the self-hosted web dashboard and REST API.

Quick Start

tesla serve                      # start on default port 8080
tesla serve --port 3000          # custom port
tesla serve --host 0.0.0.0      # expose to LAN

The dashboard opens at http://localhost:8080 (or your custom port).

Prerequisites

The serve extra must be installed:

uv tool install "tesla-cli[serve]"

What the Dashboard Includes

  • Dashboard page: Battery status, recent charges, quick action buttons
  • Vehicle page: Charge history, climate controls, door/trunk controls
  • Dossier page: VIN decode, specs, option codes, recalls, logistics
  • Analytics page: TeslaMate trip history, charging costs, heatmaps
  • Settings page: Configuration form

API Endpoints

The REST API is available at /api/:

  • GET /api/vehicle/state — full vehicle state
  • GET /api/charge/status — charging status
  • POST /api/vehicle/wake — wake vehicle
  • POST /api/security/lock — lock doors
  • GET /api/live — SSE stream for real-time updates
  • GET /api/metrics — Prometheus metrics (27 gauges)

Full API docs: http://localhost:8080/docs (Swagger UI)

Response Guidelines

  • Check if the serve extra is installed first
  • Provide the URL after starting
  • Mention the Swagger UI at /docs for API exploration
  • If the user wants to expose to their network, remind them about security (no auth by default — set an API key with tesla config set server.api_key <key>)

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