agentleFS
Sign inStart free
dacryptdacrypt/tesla-claude-plugin/CLAUDE.md

tesla-claude-plugin

CLAUDE.md0 starsChanged 7 months agoMITView on GitHub

A Claude Code plugin that wraps tesla-cli for natural language Tesla vehicle management. The plugin is the AI interface layer; the CLI is the execution engine.

The file

We split this CLAUDE.md into the rules it gives an agent

3 rules. About 0 are common, 0 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Create skills/<name>/SKILL.md with YAML frontmatter

    line 26
  2. Very specific:

    Use allowed-tools: Bash(tesla *) to scope tool access

    line 27
  3. Very specific:

    Keep SKILL.md under 500 lines — move reference material to separate files

    line 30

≈ “Common” is an estimate: at least 1 in 5 of the 26,980 CLAUDE.md files we read have a rule of the same kind, not the same words. “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
CLAUDE.md

Tesla Claude Plugin — Contributor Context

What is this?

A Claude Code plugin that wraps tesla-cli for natural language Tesla vehicle management. The plugin is the AI interface layer; the CLI is the execution engine.

Structure

.claude-plugin/plugin.json    # Plugin manifest (name, version, author)
skills/*/SKILL.md             # 9 skills — each a focused capability
bin/tesla-check               # Pre-flight validation script
docs/design.md                # Architecture design document

Key Rules

  1. Zero PII — never hardcode VINs, order numbers, names, or emails in any skill file
  2. Dynamic context — use !tesla config show --json`` shell injection for runtime data
  3. CLI is the engine — skills invoke tesla commands, never duplicate business logic
  4. Confirm destructive actions — unlock, trunk, sentry off, remote-start require user OK
  5. Descriptions under 250 chars — Claude Code truncates longer descriptions

Adding a Skill

  1. Create skills/<name>/SKILL.md with YAML frontmatter
  2. Use allowed-tools: Bash(tesla *) to scope tool access
  3. Set disable-model-invocation: true for commands with side effects
  4. Set user-invocable: false for background knowledge skills
  5. Keep SKILL.md under 500 lines — move reference material to separate files

Testing

claude --plugin-dir .                  # load plugin locally
/tesla:status                          # test a skill
bin/tesla-check                        # run pre-flight validation

Naming Conventions

  • Skill names: lowercase + hyphens only (e.g., battery-health)
  • Directories match skill names
  • Plugin namespace: tesla: (e.g., /tesla: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