charge
Skill0 starsChanged 7 months agoMITView on GitHub
Tesla charging management — battery status, charge sessions, cost tracking, weekly summaries, schedule, forecast. Use when someone asks about charging, battery, range, kWh, cost per charge, charge history, or Supercharger usage.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- runxhq/runxtheir own version, first seen Oct 13, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- runxhq/runx★ 97same 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.
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
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
- Very specific: line 76
If the CLI is not configured (no VIN, no auth), stop and tell the user to run /tesla:setup — never auto-configure
- Distinctive: line 77
Always include SoC % and charge state (charging, stopped, disconnected)
- Distinctive: line 78
If charging: show power (kW), time remaining, and target limit
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.
Files
Tesla Charging
Manage and analyze charging state, history, and costs.
Current State
tesla charge status # full: SoC %, range, power, time remaining, limit
tesla charge status --oneline # compact: 🔋 72% | ⚡ 11kW | 1h30m to 80%
tesla charge last # most recent charge session with costCost & Usage Tracking
tesla charge weekly # weekly kWh, cost, sessions (default: last 4 weeks)
tesla charge weekly --weeks 8 # last 8 weeks
tesla charge cost-summary # aggregated cost report
tesla charge cost-summary --csv costs.csv # export to CSV
tesla teslaMate cost-report # monthly cost breakdown (requires TeslaMate)
tesla teslaMate cost-report --month 2026-03 # specific monthCharge History
tesla charge sessions # unified sessions (TeslaMate + Fleet API)
tesla charge sessions -n 50 # last 50 sessions
tesla charge sessions --csv charges.csv # export to CSV
tesla charge history # Fleet API raw charge historySchedule & Forecast
tesla charge forecast # ETA + kWh estimate to reach target SoC
tesla charge schedule-preview # scheduled charge + departure times
tesla charge schedule-preview --oneline # 🔌 Charge @ 23:30 | 🚗 Depart @ 07:00
tesla charge profile # view/set limit + amps + scheduleCharging Control
tesla charge start # begin charging
tesla charge stop # stop charging
tesla charge set-limit 80 # set target SoC (50-100%)
tesla charge set-amps 32 # set current (1-48A)
tesla charge limit # show current limit
tesla charge amps # show current amperageSupercharging Invoices
tesla charge invoices # show recent Supercharging invoices
tesla charge invoices -n 50 # last 50 invoices
tesla charge invoices --csv invoices.csv # export to CSVRequires Tessie backend. Shows date, location, kWh, cost, duration.
Response Guidelines
- If the CLI is not configured (no VIN, no auth), stop and tell the user to run
/tesla:setup— never auto-configure - Always include SoC % and charge state (charging, stopped, disconnected)
- If charging: show power (kW), time remaining, and target limit
- For cost queries: show kWh consumed and cost (using configured
cost_per_kwh) - For weekly/monthly: show trends and comparisons
- Mention if TeslaMate is needed for deeper analytics
- For
$ARGUMENTS:- "status" / no args →
tesla charge status - "last" →
tesla charge last - "weekly" / "week" →
tesla charge weekly - "sessions" / "history" →
tesla charge sessions - "forecast" / "eta" →
tesla charge forecast - "cost" / "money" / "spent" →
tesla charge cost-summary
- "status" / no args →
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
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.

