monta-charging-operations
Step-by-step workflows for EV charging operators using Monta. Use when the user wants to investigate a failed, stuck, or zero-kWh charge, check why a charger is offline or in error, pull site or charger utilisation, reconcile charges against wallet transactions or invoices, or onboard a new site or charge point. Builds on the monta-api skill.
Install
With your agent
Install OMGSkills skill "monta-app/claude-plugin-monta:skills/monta-charging-operations" into this agent's normal skills directory: call the OMGSkills MCP get_install_plan tool for your agent and run the script it returns (it installs only the pinned commit and verifies SKILL.md), and stop if MCP or the pin is unavailable. Do not overwrite or change existing skills without asking me.
Manual command
git clone https://github.com/monta-app/claude-plugin-monta /tmp/claude-plugin-monta && ln -s /tmp/claude-plugin-monta/skills/monta-charging-operations ~/.claude/skills/monta-charging-operationsFrom README
Monta charging operations Workflows for day-to-day operator questions. Tool names, filters, safety rules, and conventions are in the monta-api skill; read it first. Everything below starts with reads. Only the final step of some workflows changes anything, and those steps require confirmation with the concrete target restated. Investigate a failed or stuck charge Find the charge. If the user has an ID, call get-charge. Otherwise get-charges with chargePointId or siteId, state, and a narrow fromDate/toDate. Stuck usually means state is starting, charging, stopping, or releasing long after startedAt, or consumedKwh is 0 after several minutes. Read the charge. Report state and rawState, startSource, chargeAuth type, startedAt, stoppedAt, failedAt, failureReason, stopReason, consumedKwh, kwhLimit, socLimit, price, cost, and payingTeam. A failureReason or stopReason usually answers the question directly. Check the money if relevant.